Security readout for executives and security teams
Plain-English summary
A Linux kernel boot-time memory-management error can trigger a use-after-free when boot configuration memory is released through the wrong allocator. The supplied CVSS score is 7.8, reflecting potentially serious confidentiality, integrity, and availability impact from a local, low-privileged attack path.
Executive priority
Treat this as a high-priority kernel maintenance issue, especially on shared or multi-user Linux systems. It is not evidence of an ongoing emergency because active exploitation is unsupported. Schedule prompt vendor-approved kernel updates, with normal reboot coordination and verification of the running version.
Technical view
During xbc_exit(), memblock may already have transferred memory management to the buddy allocator. Calling memblock_free() can then access freed memblock data, particularly where CONFIG_ARCH_KEEP_MEMBLOCK is disabled, including x86. The kernel fix retains memblock_free() for early initialization rollback but uses memblock_free_late() during exit.
Likely exposure
Exposure is limited to Linux kernels containing the vulnerable bootconfig cleanup logic. The bundle identifies Linux 5.15, 6.1.88, 6.6.29, 6.8.8, and 6.9 as affected entries, but does not provide sufficiently clear range semantics. Confirm exact status against distribution advisories and kernel build provenance.
Exploitation context
The supplied CVSS vector describes local access, low privileges, low complexity, and no user interaction. The bundle includes a KASAN-detected kernel use-after-free, but provides no evidence of reliable exploitation in production. This CVE is not listed as KEV in the supplied data, so active exploitation should not be assumed.
Researcher notes
The demonstrated fault is a read-after-free in memblock_isolate_range reached through xbc_exit() during kernel initialization. The source bundle does not establish exploitability, affected configuration breadth, or downstream version boundaries. Researchers should distinguish a sanitizer-confirmed memory-safety defect from demonstrated privilege escalation or code execution.
Mitigation direction
- Update to a vendor-supported kernel containing the referenced upstream or stable fix.
- Check distribution advisories for the precise corrected package version.
- Prioritize multi-user systems where untrusted users can obtain local access.
- Restrict unnecessary local accounts until affected systems are updated.
Validation and detection
- Inventory running kernel versions and distribution package revisions.
- Compare kernel packages with vendor advisories and the referenced stable commits.
- Confirm whether kernel builds disable CONFIG_ARCH_KEEP_MEMBLOCK.
- Verify the updated kernel is active after reboot, not merely installed.
- Review boot and kernel logs for KASAN reports or unexpected startup failures.
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.
CVE-2024-26983 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
1 official scoreWe 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.9LinuxVulnerability 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
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/1e7feb31a18c197d63a5e606025ed63c762f8918CVE reference, Linux
- https://git.kernel.org/stable/c/e46d3be714ad9652480c6db129ab8125e2d20ab7CVE reference, Linux
- https://git.kernel.org/stable/c/5a7dfb8fcd3f29fc93161100179b27f24f3d5f35CVE reference, Linux
- https://git.kernel.org/stable/c/89f9a1e876b5a7ad884918c03a46831af202c8a0CVE reference, Linux
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/DAMSOZXJEPUOXW33WZYWCVAY7Z5S7OOY/CVE reference, CVE
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4EZ6PJW7VOZ224TD7N4JZNU6KV32ZJ53/CVE reference, CVE
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/GCBZZEC7L7KTWWAS2NLJK6SO3IZIL4WW/CVE 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.