LiveActive security incident?Get immediate response
CVE Record

CVE-2024-42231: btrfs: zoned: fix calc_available_free_space() for zoned mode

In the Linux kernel, the following vulnerability has been resolved: btrfs: zoned: fix calc_available_free_space() for zoned mode calc_available_free_space() returns the total size of metadata (or system) block groups, which can be allocated from unallocated disk space. The logic is wrong on zoned mode in two places. First, the calculation of data_chunk_size is wrong. We always allocate one zone as one chunk, and no partial allocation of a zone. So, we should use zone_size (= data_sinfo->chunk_size) as it is. Second, the result "avail" may not be zone aligned. Since we always allocate one zone as one chunk on zoned mode, returning non-zone size aligned bytes will result in less pressure on the async metadata reclaim process. This is serious for the nearly full state with a large zone size device. Allowing over-commit too much will result in less async reclaim work and end up in ENOSPC. We can align down to the zone size to avoid that.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue affects Btrfs filesystems running in zoned mode. The kernel may overestimate usable metadata or system space when a zoned device is nearly full, reducing reclaim pressure and ending in unexpected ENOSPC failures. The evidence points to an availability and reliability risk, not a remote compromise.

Executive priority

Treat as a targeted reliability fix for storage platforms, not a broad emergency. Prioritize environments using Btrfs zoned mode near capacity, because failure could interrupt workloads through unexpected out-of-space conditions.

Technical view

The vulnerable Btrfs zoned-mode logic in calc_available_free_space() miscalculates data_chunk_size and may return non-zone-aligned availability. Because zoned mode allocates one full zone per chunk, this can overcommit metadata or system reservations and defer async metadata reclaim, causing ENOSPC on nearly full large-zone devices.

Likely exposure

Exposure is likely limited to Linux systems using Btrfs in zoned mode, especially large-zone devices near capacity. The source lists affected Linux kernel versions and stable kernel fix commits, but distro package exposure depends on vendor backports.

Exploitation context

No active exploitation is stated in the provided sources, and the CVE is not marked KEV. The described failure mode is operational exhaustion under specific storage conditions rather than an externally triggered exploit path.

Researcher notes

The public record lacks CVSS, CWE, exploit details, and clear distro-specific fixed versions. Analysis should stay tied to Btrfs zoned allocation semantics and the two stable commits. Avoid expanding impact beyond ENOSPC availability risk without vendor evidence.

Mitigation direction

  • Check Linux distribution advisories for CVE-2024-42231 kernel package status.
  • Update to a kernel package containing the referenced stable Btrfs fixes.
  • Prioritize nearly full Btrfs zoned-mode systems with large zone sizes.
  • Reduce capacity pressure on affected filesystems until patched.
  • Monitor for ENOSPC events and metadata reclaim anomalies.

Validation and detection

  • Inventory Linux systems using Btrfs zoned mode.
  • Identify kernel versions and compare against vendor fixed packages.
  • Review kernel changelogs for the referenced stable commits.
  • Check storage telemetry for near-full zoned Btrfs filesystems.
  • Validate patched kernels in staging before production rollout.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-42231 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
2ADP providers
3Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxcb6cbab79055ca207ad88bc54226b48ececdcef0, cb6cbab79055ca207ad88bc54226b48ececdcef0unaffected
LinuxLinux6.7, 0, 6.9.9, 6.10affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.