CVE-2024-35949 remediation guide
Linux Linux, linux kernel, fedora
In the Linux kernel, the following vulnerability has been resolved: btrfs: make sure that WRITTEN is set on all metadata blocks We previously would call btrfs_check_leaf() if we had the check integrity code enabled, which meant that we could only run the extended leaf checks if we had WRITTEN set on the header flags. This leaves a gap in our checking, because we could end up with corruption on disk where WRITTEN isn't set on the leaf, and then the extended leaf checks don't get run which we rely on to validate all of the item pointers to make sure we don't access memory outside of the exten...
Identify the affected asset
Confirm whether Linux Linux, linux kernel, fedora is installed, record the deployed version and installation path, and identify exposed interfaces.
- Record the product name, package or appliance identifier, and installed version.
- Identify internet-facing, administrative, API, and internal access paths.
- Preserve the pre-change configuration and relevant service logs.
Validate the affected-version match
Compare the deployed version with the affected range: >= 85d8a826c7cde17f9cca9c4debecb4538bdb6573 < 9dff3e36ea89e8003516841c27c45af562b6ef44, >= 85d8a826c7cde17f9cca9c4debecb4538bdb6573 < ef3ba8ce8cf7075b716aa4afcefc3034215878ee, >= 85d8a826c7cde17f9cca9c4debecb4538bdb6573 < e03418abde871314e1a3a550f4c8afb7b89cb273, >= 6.5, < 6.6.85, >= 6.7 < 6.8.10, 6.9, 40. Treat incomplete inventory results as unresolved.
Prioritize with independent signals
The CVSS severity warrants an early asset and exposure review. Combine this signal with asset criticality, exposure, compensating controls, and business impact.
Apply supported remediation
Follow the vendor advisory or supported update path. Current fixed-version status: 6.6.85, 6.8.10. Preserve configuration and rollback material before change.
Verify the result
Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.
- Confirm the expected version and package state.
- Run a functional health check for critical service paths.
- Review authentication, error, application, and security monitoring logs.
- Reassess exposure if the supported fix cannot be applied.
Operational boundary
This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.