CVE-2024-26795 json
riscv: Sparse-Memory/vmemmap out-of-bounds fix
published 2024-04-04 2 y ago modified 2026-08-05 3 mo ago also EUVD-2024-24057
- cvss
- 7.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 15%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
riscv: Sparse-Memory/vmemmap out-of-bounds fix
Offset vmemmap so that the first page of vmemmap will be mapped to the first page of physical memory in order to ensure that vmemmap’s bounds will be respected during pfn_to_page()/page_to_pfn() operations. The conversion macros will produce correct SV39/48/57 addresses for every possible/valid DRAM_BASE inside the physical memory limits.
v2:Address Alex's comments
Patch / fix
- Linux Linux 5.15.151, 6.1.81, 6.6.21, 6.7.9, 6.8
- linux Debian 12 6.1.82-1
- linux Debian 14, Debian 13 6.7.9-1
debian advisories DEBIAN-CVE-2024-26795
- linux Ubuntu 22.04 LTS 5.15.0-112.122
- linux-aws Ubuntu 22.04 LTS 5.15.0-1063.69
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1062.70
- linux-gke Ubuntu 22.04 LTS 5.15.0-1060.66
- linux-ibm Ubuntu 22.04 LTS 5.15.0-1056.59
- linux-kvm Ubuntu 22.04 LTS 5.15.0-1060.65
- linux-azure Ubuntu 22.04 LTS 5.15.0-1066.75
- linux-gkeop Ubuntu 22.04 LTS 5.15.0-1046.53
ubuntu advisories UBUNTU-CVE-2024-26795
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/5941a90c55d3bfba732b32208d58d997600b44ef commit
- git.kernel.org/stable/c/8310080799b40fd9f2a8b808c657269678c149af commit
- git.kernel.org/stable/c/a278d5c60f21aa15d540abb2f2da6e6d795c3e6e commit
- git.kernel.org/stable/c/2a1728c15ec4f45ed9248ae22f626541c179bfbe commit
- git.kernel.org/stable/c/a11dd49dcb9376776193e15641f84fcc1e5980c9 commit
- git.kernel.org/stable/c/8af1c121b0102041809bc137ec600d1865eaeedd commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2024-26795 updated cvss 5.5
kernel: riscv: Sparse-Memory/vmemmap out-of-bounds fix
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
0.24% chance of exploitation in the next 30 days, higher than 15% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
-
git.kernel.org
/stable/c/5941a90c55d3bfba732b32208d58d997600b44ef
patch
-
git.kernel.org
/stable/c/8310080799b40fd9f2a8b808c657269678c149af
patch
-
git.kernel.org
/stable/c/a278d5c60f21aa15d540abb2f2da6e6d795c3e6e
patch
-
git.kernel.org
/stable/c/2a1728c15ec4f45ed9248ae22f626541c179bfbe
patch
-
git.kernel.org
/stable/c/a11dd49dcb9376776193e15641f84fcc1e5980c9
patch
-
git.kernel.org
/stable/c/8af1c121b0102041809bc137ec600d1865eaeedd
patch
-
lists.debian.org
/debian-lts-announce/2024/06/msg00017.html
mailing-list
Sources
- CVE List CVE-2024-26795
- NVD CVE-2024-26795
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.