CVE-2023-54297: btrfs: zoned: fix memory leak after finding block group with super blocks
In the Linux kernel, the following vulnerability has been resolved:
btrfs: zoned: fix memory leak after finding block group with super blocks
At exclude_super_stripes(), if we happen to find a block group that has
super blocks mapped to it and we are on a zoned filesystem, we error out
as this is not supposed to happen, indicating either a bug or maybe some
memory corruption for example. However we are exiting the function without
freeing the memory allocated for the logical address of the super blocks.
Fix this by freeing the logical address.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel memory leak in Btrfs zoned filesystem handling. The available sources describe a narrow error path where memory is not freed after detecting an unexpected super-block mapping. Business risk is hard to rate because no CVSS, exploitation evidence, or practical impact details are provided.
Executive priority
Track and patch during normal kernel maintenance unless your environment uses Btrfs zoned filesystems at scale. Escalate priority if storage nodes match the affected configuration or show unexplained memory pressure.
Technical view
The flaw is in Btrfs zoned exclude_super_stripes(). If a block group unexpectedly has super blocks mapped to it, the function errors out but fails to free allocated logical-address memory. Kernel stable commits fix the leak by freeing that memory before exit. Sources do not provide CWE, CVSS, exploit prerequisites, or impact beyond the leak.
Likely exposure
Exposure appears limited to Linux systems running affected kernels with Btrfs zoned filesystems. General Linux systems not using Btrfs zoned mode are less likely exposed based on the description. The bundle lists affected Linux kernel version entries including 5.11, 5.15.123, 6.1.42, 6.4.7, and 6.5; confirm distro package status.
Exploitation context
The source bundle does not indicate active exploitation, public exploit availability, or CISA KEV listing. The described condition appears tied to an unexpected Btrfs zoned filesystem state, but the sources do not explain whether an attacker can intentionally trigger it.
Researcher notes
The public record is sparse. It identifies a missing free on an error path, but not a trigger model, attacker control, privilege requirement, or denial-of-service severity. Treat exploitability as unproven from these sources.
Mitigation direction
Update to a kernel or distro package containing the referenced stable fixes.
Check Linux distribution advisories for CVE-2023-54297 package status.
Prioritize systems using Btrfs zoned filesystems over unrelated Linux hosts.
Monitor affected systems for abnormal kernel memory pressure until patched.
Validation and detection
Inventory Linux kernel versions across systems using Btrfs.
Identify hosts using Btrfs zoned filesystem configurations.
Confirm installed kernels include one of the referenced stable fixes.
Review vendor advisories for backported fixes under distro-specific versions.
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-2023-54297 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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
0ADP providers
5Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Dec 30, 2025, 12:23 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.