Security readout for executives and security teams
Plain-English summary
A Linux Btrfs flaw can crash the kernel during certain storage write failures. Error information from a split write may arrive before its bookkeeping is ready, causing a null-pointer access. This can interrupt services and storage availability. The supplied sources support high severity, but not known active exploitation.
Executive priority
High for production systems using Btrfs, particularly storage nodes with mirrored or zoned configurations. Prioritize supported kernel updates and backport confirmation. Systems not using Btrfs are unlikely to exercise this code path, but inventory evidence should confirm that assumption.
Technical view
A timing and initialization-order defect in Btrfs split-bio error propagation can let a rapidly completed child bio access the original bio before its context is initialized. This causes a NULL pointer dereference in the kernel write-completion path. The supplied CVSS v3.1 score is 7.8 with local, low-privileged attack conditions.
Likely exposure
Exposure concerns systems running affected Linux kernels with Btrfs. The described failure involves split bios, mirrored writes, rapid error completion, and zoned-device RAID testing. The supplied version list names 6.3, 6.11.7, and 6.12 but does not clearly express every range boundary; verify distribution-specific package status.
Exploitation context
CISA KEV status is false, and the supplied sources provide no evidence of active exploitation. The CVSS vector describes local, low-privileged conditions without user interaction. The narrative demonstrates reproducibility through a Btrfs regression test, but does not establish a practical malicious exploitation method.
Researcher notes
The source identifies CWE-476. Fast completion of an earlier split bio may invoke error propagation before the remaining original bio context is initialized, producing a NULL dereference during Btrfs write completion. The linked stable commits are the authoritative fix references. Because the supplied description is truncated, additional cases and exact version-range semantics cannot be confirmed.
Mitigation direction
- Apply a vendor-supported kernel update containing the linked Btrfs fix.
- Confirm affected package versions and maintenance requirements through the Linux distribution or appliance vendor.
- Use the upstream commits to verify vendor backports into supported kernel packages.
Validation and detection
- Inventory running kernel versions and systems mounting Btrfs filesystems.
- Check vendor changelogs or kernel sources for either referenced stable commit.
- Review kernel logs for NULL dereferences involving btrfs_bio_end_io or btrfs_orig_write_end_io.
- After updating, verify the fixed kernel is running and Btrfs I/O completes without kernel faults.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.
CWE-476: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2024-50225 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9LinuxCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Base CVSS 3.1 score
5.5MediumVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
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.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/22833d89b780ba0f9f66e19c477e7decf638edceCVE reference, Linux
- https://git.kernel.org/stable/c/d48e1dea3931de64c26717adc2b89743c7ab6594CVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
NULL Pointer Dereference
NULL Pointer Dereference represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.