Security readout for executives and security teams
Plain-English summary
A Linux RAM-disk driver initialization failure can leave references pointing to released driver code or structures. A local attacker reaching this condition may trigger a use-after-free with potentially severe confidentiality, integrity, and availability impact. The supplied sources do not show active exploitation.
Executive priority
Treat this as a high-priority kernel update, especially where low-privileged local code can run or brd RAM disks are available. It is not supported as an emergency remote-exploitation event: potential host impact is severe, but the attack vector is local and exploitation remains unconfirmed.
Technical view
CWE-416 occurs in brd_init because RAM disks become visible before registration and module initialization fully succeed. If later initialization fails, cleanup can free disks or module code while deferred file release or another thread closes a RAM-disk device and dereferences freed operations. The fix defers disk creation and restores mutex serialization.
Likely exposure
Exposure concerns Linux systems containing the vulnerable brd implementation where the RAM-disk driver can be initialized. The bundle provides version values spanning 5.14 through 6.13, but its flattened list does not reliably establish every fixed boundary. Distribution backports may change status, so validate the exact running build against vendor advisories and referenced commits.
Exploitation context
The bundle marks KEV false and provides no evidence of active exploitation or public weaponization. The supplied CVSS vector indicates local access with low privileges. Triggering also involves failed brd initialization and an outstanding or concurrent RAM-disk reference; these sources do not support an unauthenticated remote attack scenario.
Researcher notes
The issue was reproduced under fault injection with KASAN. Documented cases involve deferred file release after failed module initialization and concurrent open or close activity on a RAM-disk device. Sources establish a plausible kernel use-after-free and stable fixes, but not reliable privilege escalation, complete distribution package mappings, or exploitation in the wild.
Mitigation direction
- Obtain a corrected kernel from your Linux distributor or use a build containing the applicable referenced stable fix.
- Test, deploy, and reboot into the corrected kernel according to established change-management procedures.
- If rollout is delayed, consult distributor guidance for supported temporary mitigations; none are specified in this bundle.
Validation and detection
- Inventory the exact running kernel and vendor package release across Linux assets.
- Compare each build with distributor advisories and referenced stable commits, accounting for backports.
- Determine whether brd is built in, loadable, loaded, or required by workloads.
- After remediation, confirm the corrected kernel is running and review logs for related Oops or KASAN reports.
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-416: 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-56693 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:H/I:H/A:H1.85.9CISA-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
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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/41219c147df8bbd6591f59af5d695fb6c9a1cbffCVE reference, Linux
- https://git.kernel.org/stable/c/259bf925583ec9e3781df778cadf00594095090dCVE reference, Linux
- https://git.kernel.org/stable/c/410896624db639500f24f46478b4bfa05c76bf56CVE reference, Linux
- https://git.kernel.org/stable/c/c0c2744cd2939ec5999c51dbaf2af16886548b7bCVE reference, Linux
- https://git.kernel.org/stable/c/63dfd728b30f79495dacc886127695a379805152CVE reference, Linux
- https://git.kernel.org/stable/c/826cc42adf44930a633d11a5993676d85ddb0842CVE reference, Linux
- https://lists.debian.org/debian-lts-announce/2025/03/msg00001.htmlCVE reference, CVE
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.
Use After Free
Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.