CVE-2024-26906: Linux kernel · x86/mm: Disallow vsyscall page read for copy_from_kernel_nofault()
Affects Linux kernelSource GCVE Database
Not known to be exploited · CVSS 5.5 Medium · fixed in 5.15.0-1063.69~20.04.1 : update Linux kernel when convenient.
Data as of 28 Oct 2026, 10:59 UTC
- Patch
- Available – fixed in 5.15.0-1063.69~20.04.1, 5.15.0-1065.74~20.04.1, 5.15.0-1062.70~20.04.1 +33
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 17 Apr 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Patches and advisories
- ubuntu.com/security/notices/USN-6820-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6821-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6821-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-6828-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6820-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-6821-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-6821-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-6871-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6892-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6919-1 (opens in a new tab)
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu Pro Realtime 24.04 LTSlinux-raspi-realtimepkg:deb/ubuntu/linux-raspi-realtime?arch=source&distro=realtime/nobleOther threats | Affected
| Fixed in
|
Ubuntu 22.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=jammyOther threats | Affected
| Fixed in
|
Ubuntu 22.04 LTSlinux-allwinner-5.19pkg:deb/ubuntu/linux-allwinner-5.19?arch=source&distro=jammyOther threats | Affected
| Fixed in– |
Ubuntu 22.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=jammyOther threats | Affected
| Fixed in
|
Ubuntu 22.04 LTSlinux-aws-5.19pkg:deb/ubuntu/linux-aws-5.19?arch=source&distro=jammyOther threats | Affected
| Fixed in– |
Ubuntu 22.04 LTSlinux-aws-6.2pkg:deb/ubuntu/linux-aws-6.2?arch=source&distro=jammyOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
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().
References
- ubuntu.com/security/CVE-2024-26906 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2024-26906 (opens in a new tab)
- git.kernel.org/linus/32019c659ecfe1d92e3bf9fcdfbb11a7c70acd58 (opens in a new tab)
- git.kernel.org/stable/c/6e4694e65b6db4c3de125115dd4f55848cc48381 (opens in a new tab)
- git.kernel.org/stable/c/e8a67fe34b76a49320b33032228a794f40b0316b (opens in a new tab)
- git.kernel.org/stable/c/f175de546a3eb77614d94d4c02550181c0a8493e (opens in a new tab)
- git.kernel.org/stable/c/57f78c46f08198e1be08ffe99c4c1ccc12855bf5 (opens in a new tab)
- git.kernel.org/stable/c/29bd6f86904682adafe9affbc7f79b14defcaff8 (opens in a new tab)
- git.kernel.org/stable/c/32019c659ecfe1d92e3bf9fcdfbb11a7c70acd58 (opens in a new tab)
- ubuntu.com/security/notices/USN-6820-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6821-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6821-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-6828-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6820-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-6821-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-6821-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-6871-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6892-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6919-1 (opens in a new tab)