CVE-2024-26906: x86/mm: Disallow vsyscall page read for copy_from_kernel_nofault()
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.25% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 29bd6f86904682adafe9affbc7f79b14defcaff8, 32019c659ecfe1d92e3bf9fcdfbb11a7c70acd58, 57f78c46f08198e1be08ffe99c4c1ccc12855bf5.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 29bd6f86904682adafe9affbc7f79b14defcaff8, 32019c659ecfe1d92e3bf9fcdfbb11a7c70acd58, 57f78c46f08198e1be08ffe99c4c1ccc12855bf5 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: x86/mm: Disallow vsyscall page read for copy_from_kernel_nofault() When trying to use copy_from_kernel_nofault() to read vsyscall page through a bpf program, the following oops was reported: BUG: unable to handle page fault for address: ffffffffff600000 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 3231067 P4D 3231067 PUD 3233067 PMD 3235067 PTE 0 Oops: 0000 [#1] PREEMPT SMP PTI CPU: 1 PID: 20390 Comm: test_progs ...... 6.7.0+ #58 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996) ...... RIP: 0010:copy_from_kernel_nofault+0x6f/0x110 ...... Call Trace: <TASK> ? copy_from_kernel_nofault+0x6f/0x110 bpf_probe_read_kernel+0x1d/0x50 bpf_prog_2061065e56845f08_do_probe_read+0x51/0x8d trace_call_bpf+0xc5/0x1c0 perf_call_bpf_enter.isra.0+0x69/0xb0 perf_syscall_enter+0x13e/0x200 syscall_trace_enter+0x188/0x1c0 do_syscall_64+0xb5/0xe0 entry_SYSCALL_64_after_hwframe+0x6e/0x76 </TASK> ...... ---[ end trace 0000000000000000 ]--- The oops is triggered when: 1) A bpf program uses bpf_probe_read_kernel() to read from the vsyscall page and invokes copy_from_kernel_nofault() which in turn calls __get_user_asm(). 2) Because the vsyscall page address is not readable from kernel space, a page fault exception is triggered accordingly. 3) handle_page_fault() considers the vsyscall page address as a user space address instead of a kernel space address. This results in the fix-up setup by bpf not being applied and a page_fault_oops() is invoked due to SMAP. Considering handle_page_fault() has already considered the vsyscall page address as a userspace address, fix the problem by disallowing vsyscall page read for copy_from_kernel_nofault().
- Published
- Apr 17, 2024
- Updated
- Oct 15, 2026
- EPSS
- 0.2% · 16th percentile
- CWE
- —
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux10.0
- linux linux kernel5.11 and later · before 5.15.153
- linux linux kernel5.16 and later · before 6.1.83
- linux linux kernelbefore 5.10.214
- linux linux kernel6.7 and later · before 6.7.11
- linux linux kernel6.2 and later · before 6.6.23
- linux linux kernel6.8
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.5affected
- 75a1a607bb7e6d918be3aca11ec2214a275392f4 and later · before 6e4694e65b6db4c3de125115dd4f55848cc48381affected · git
- 75a1a607bb7e6d918be3aca11ec2214a275392f4 and later · before e8a67fe34b76a49320b33032228a794f40b0316baffected · git
- 75a1a607bb7e6d918be3aca11ec2214a275392f4 and later · before f175de546a3eb77614d94d4c02550181c0a8493eaffected · git
- 75a1a607bb7e6d918be3aca11ec2214a275392f4 and later · before 57f78c46f08198e1be08ffe99c4c1ccc12855bf5affected · git
- 75a1a607bb7e6d918be3aca11ec2214a275392f4 and later · before 29bd6f86904682adafe9affbc7f79b14defcaff8affected · git
- 75a1a607bb7e6d918be3aca11ec2214a275392f4 and later · before 32019c659ecfe1d92e3bf9fcdfbb11a7c70acd58affected · git
- before 5.5not affected · semver
- 5.10.214 and later · up to and including 5.10.*not affected · semver
- 5.15.153 and later · up to and including 5.15.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.85-1 | 6.1.85-1 |
| Debian:13 | linux | before 6.7.12-1 | 6.7.12-1 |
| openSUSE:Leap 15.5 | kernel-azure | before 5.14.21-150500.33.75.1 | 5.14.21-150500.33.75.1 |
| openSUSE:Leap 15.5 | kernel-rt_debug | before 5.14.21-150500.13.79.1 | 5.14.21-150500.13.79.1 |
| openSUSE:Leap 15.5 | kernel-source-azure | before 5.14.21-150500.33.75.1 | 5.14.21-150500.33.75.1 |
| openSUSE:Leap 15.5 | kernel-source-rt | before 5.14.21-150500.13.79.1 | 5.14.21-150500.13.79.1 |
| openSUSE:Leap 15.5 | kernel-syms-azure | before 5.14.21-150500.33.75.1 | 5.14.21-150500.33.75.1 |
| openSUSE:Leap 15.5 | kernel-syms-rt | before 5.14.21-150500.13.79.1 | 5.14.21-150500.13.79.1 |
| openSUSE:Leap Micro 5.5 | kernel-rt | before 5.14.21-150500.13.79.1 | 5.14.21-150500.13.79.1 |
| Red Hat:rhel_eus:9.2::appstream | bpftool-debuginfo | before 0:7.0.0-284.92.1.el9_2 | 0:7.0.0-284.92.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-64k-debug-debuginfo | before 0:5.14.0-284.92.1.el9_2 | 0:5.14.0-284.92.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-64k-debug-devel | before 0:5.14.0-284.92.1.el9_2 | 0:5.14.0-284.92.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-64k-debug-devel-matched | before 0:5.14.0-284.92.1.el9_2 | 0:5.14.0-284.92.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-64k-debuginfo | before 0:5.14.0-284.92.1.el9_2 | 0:5.14.0-284.92.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-64k-devel | before 0:5.14.0-284.92.1.el9_2 | 0:5.14.0-284.92.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-64k-devel-matched | before 0:5.14.0-284.92.1.el9_2 | 0:5.14.0-284.92.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-debug-debuginfo | before 0:5.14.0-284.92.1.el9_2 | 0:5.14.0-284.92.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-debug-devel | before 0:5.14.0-284.92.1.el9_2 | 0:5.14.0-284.92.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-debug-devel-matched | before 0:5.14.0-284.92.1.el9_2 | 0:5.14.0-284.92.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-debuginfo | before 0:5.14.0-284.92.1.el9_2 | 0:5.14.0-284.92.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-debuginfo-common-aarch64 | before 0:5.14.0-284.92.1.el9_2 | 0:5.14.0-284.92.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-debuginfo-common-ppc64le | before 0:5.14.0-284.92.1.el9_2 | 0:5.14.0-284.92.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-debuginfo-common-s390x | before 0:5.14.0-284.92.1.el9_2 | 0:5.14.0-284.92.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-debuginfo-common-x86_64 | before 0:5.14.0-284.92.1.el9_2 | 0:5.14.0-284.92.1.el9_2 |
+96
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2024-26902Apr 17, 2024 · perf: RISCV: Fix panic on pmu overflow handler22Monitor
- ← EarlierCVE-2024-26903Apr 17, 2024 · Bluetooth: rfcomm: Fix null-ptr-deref in rfcomm_check_security22Monitor
- Later →CVE-2024-26907Apr 17, 2024 · RDMA/mlx5: Fix fortify source warning while accessing Eth segment31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 29bd6f86904682adafe9affbc7f79b14defcaff8 | Vendor (CNA) |
| Linux Linux | 32019c659ecfe1d92e3bf9fcdfbb11a7c70acd58 | Vendor (CNA) |
| Linux Linux | 57f78c46f08198e1be08ffe99c4c1ccc12855bf5 | Vendor (CNA) |
| Linux Linux | 6e4694e65b6db4c3de125115dd4f55848cc48381 | Vendor (CNA) |
| Linux Linux | e8a67fe34b76a49320b33032228a794f40b0316b | Vendor (CNA) |
| Linux Linux | f175de546a3eb77614d94d4c02550181c0a8493e | Vendor (CNA) |
| almalinux:bpftool | 4.18.0-553.8.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel | 4.18.0-553.8.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-abi-stablelists | 4.18.0-553.8.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-core | 4.18.0-553.8.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-cross-headers | 4.18.0-553.8.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug | 4.18.0-553.8.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-core | 4.18.0-553.8.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-devel | 4.18.0-553.8.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-modules | 4.18.0-553.8.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-modules-extra | 4.18.0-553.8.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-devel | 4.18.0-553.8.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-doc | 4.18.0-553.8.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| debian:linux | 6.1.85-1 · Debian:12 | Package registry (OSV) |
| opensuse:kernel-azure | 5.14.21-150500.33.75.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:kernel-rt | 5.14.21-150500.13.79.1 · openSUSE:Leap Micro 5.5 | Package registry (OSV) |
| opensuse:kernel-rt_debug | 5.14.21-150500.13.79.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:kernel-source-azure | 5.14.21-150500.33.75.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:kernel-source-rt | 5.14.21-150500.13.79.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:kernel-syms-azure | 5.14.21-150500.33.75.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:kernel-syms-rt | 5.14.21-150500.13.79.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| red hat:bpftool-debuginfo | 0:7.0.0-284.92.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:5.14.0-284.92.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:5.14.0-284.92.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:5.14.0-284.92.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
+16
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-0494 · May 16, 2024(Linux Kernel Güncellemesi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/32019c659ecfe1d92e3bf9fcdfbb11a7c70acd58
- git.kernel.org/stable/c/57f78c46f08198e1be08ffe99c4c1ccc12855bf5
- git.kernel.org/stable/c/6e4694e65b6db4c3de125115dd4f55848cc48381
- git.kernel.org/stable/c/e8a67fe34b76a49320b33032228a794f40b0316b
- git.kernel.org/stable/c/f175de546a3eb77614d94d4c02550181c0a8493e
- lists.debian.org/debian-lts-announce/2024/06/msg00017.html
- cert-portal.siemens.com/productcert/html/ssa-265688.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.