Security readout for executives and security teams
Plain-English summary
A Linux kernel flaw on RISC-V systems can mishandle memory-page metadata, allowing valid address conversions to exceed expected vmemmap boundaries. The supplied CVSS score is 7.8 because a local, low-privileged attacker could potentially compromise confidentiality, integrity, and availability. Exposure depends on the system architecture, memory configuration, kernel version, and vendor backports.
Executive priority
Treat as high priority for RISC-V systems permitting local untrusted users or workloads because successful exploitation could affect all three security properties. Prioritize asset identification and vendor-supported kernel updates. Systems that are not RISC-V are not indicated as exposed by the supplied sources.
Technical view
The RISC-V sparse-memory vmemmap layout was not offset to align its first page with the first physical-memory page. Consequently, pfn_to_page() and page_to_pfn() could produce out-of-bounds results for some valid DRAM_BASE values under SV39, SV48, or SV57. Stable-kernel commits correct the mapping offset so conversions remain within bounds.
Likely exposure
Likely exposure is limited to RISC-V Linux systems using the relevant sparse-memory/vmemmap code. The record lists affected kernel versions including 5.4, 5.15.151, 6.1.81, 6.6.21, 6.7.9, and 6.8, but its version data is ambiguous. Distribution backports must be checked before declaring a host vulnerable.
Exploitation context
The CVSS vector describes local access, low privileges, low complexity, and no user interaction, with potentially high confidentiality, integrity, and availability impact. The supplied record is not in KEV and provides no evidence of active exploitation or a public exploit. Practical trigger conditions are not fully documented in the bundle.
Researcher notes
The source bundle identifies an out-of-bounds condition but assigns no CWE and gives no reproducer, crash trace, or confirmed attack path. Its affected-version entries appear flattened or duplicated, so upstream version comparison alone is insufficient. Researchers should correlate the running configuration and distributor backports with the cited stable commits without interpreting absent exploit evidence as proof of non-exploitability.
Mitigation direction
- Install a vendor-supported kernel containing the applicable stable-kernel correction.
- Check distribution advisories because patched package versions may differ from upstream versions.
- Prioritize exposed multi-user or untrusted-workload RISC-V systems.
- Restrict local access and untrusted workloads until affected systems are updated.
Validation and detection
- Confirm whether each system uses the RISC-V architecture.
- Identify the running kernel version and relevant sparse-memory configuration.
- Compare vendor package status against the applicable stable-kernel fix.
- Verify the patched kernel is running after installation and reboot.
- Review vendor advisories for backports that retain an older version number.
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-26795 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/5941a90c55d3bfba732b32208d58d997600b44efCVE reference, Linux
- https://git.kernel.org/stable/c/8310080799b40fd9f2a8b808c657269678c149afCVE reference, Linux
- https://git.kernel.org/stable/c/a278d5c60f21aa15d540abb2f2da6e6d795c3e6eCVE reference, Linux
- https://git.kernel.org/stable/c/2a1728c15ec4f45ed9248ae22f626541c179bfbeCVE reference, Linux
- https://git.kernel.org/stable/c/a11dd49dcb9376776193e15641f84fcc1e5980c9CVE reference, Linux
- https://git.kernel.org/stable/c/8af1c121b0102041809bc137ec600d1865eaeeddCVE reference, CVE · x_transferred
- https://lists.debian.org/debian-lts-announce/2024/06/msg00017.htmlCVE reference, CVE · x_transferred
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.