Linux: Out-of-bounds Read
CVE-2024-34777 is a high-severity out-of-bounds read vulnerability in Linux, with a CVSS 3.1 base score of 7.1 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists versions 35d31c8bd4722b107f5a2f5ddddce839de04b936, c57874265a3c5206d7aece3793bb2fc9abcd7570, 34a816d8735f3924b74be8e5bf766ade1f3bd10b as the first without the flaw, so updating Linux to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.22% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Linux to 35d31c8bd4722b107f5a2f5ddddce839de04b936 or c57874265a3c5206d7aece3793bb2fc9abcd7570 or 34a816d8735f3924b74be8e5bf766ade1f3bd10b or 63e7e05a48a35308aeddd7ecccb68363a5988e87, whichever matches your release line, or a later version.
- Update Linux Kernel to 5.15.161 or 6.1.93 or 6.6.33 or 6.9.4, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | 65789daa8087e125927230ccb7e1eab13999b0cf up to, but not including, 35d31c8bd4722b107f5a2f5ddddce839de04b936; 65789daa8087e125927230ccb7e1eab13999b0cf up to, but not including, c57874265a3c5206d7aece3793bb2fc9abcd7570; 65789daa8087e125927230ccb7e1eab13999b0cf up to, but not including, 34a816d8735f3924b74be8e5bf766ade1f3bd10b; 65789daa8087e125927230ccb7e1eab13999b0cf up to, but not including, 63e7e05a48a35308aeddd7ecccb68363a5988e87; 65789daa8087e125927230ccb7e1eab13999b0cf up to, but not including, 1ff05e723f7ca30644b8ec3fb093f16312e408ad; 5.11 | 35d31c8bd4722b107f5a2f5ddddce839de04b936, c57874265a3c5206d7aece3793bb2fc9abcd7570, 34a816d8735f3924b74be8e5bf766ade1f3bd10b, 63e7e05a48a35308aeddd7ecccb68363a5988e87, 1ff05e723f7ca30644b8ec3fb093f16312e408ad |
| Linux | Linux Kernel | 5.11 up to, but not including, 5.15.161; 5.16 up to, but not including, 6.1.93; 6.2 up to, but not including, 6.6.33; 6.7 up to, but not including, 6.9.4; 6.10 | 5.15.161, 6.1.93, 6.6.33, 6.9.4 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- NoneNothing can be modified.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H. Scored by NVD.
Official description
In the Linux kernel, the following vulnerability has been resolved: dma-mapping: benchmark: fix node id validation While validating node ids in map_benchmark_ioctl(), node_possible() may be provided with invalid argument outside of [0,MAX_NUMNODES-1] range leading to: BUG: KASAN: wild-memory-access in map_benchmark_ioctl (kernel/dma/map_benchmark.c:214) Read of size 8 at addr 1fffffff8ccb6398 by task dma_map_benchma/971 CPU: 7 PID: 971 Comm: dma_map_benchma Not tainted 6.9.0-rc6 #37 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996) Call Trace: <TASK> dump_stack_lvl (lib/dump_stack.c:117) kasan_report (mm/kasan/report.c:603) kasan_check_range (mm/kasan/generic.c:189) variable_test_bit (arch/x86/include/asm/bitops.h:227) [inline] arch_test_bit (arch/x86/include/asm/bitops.h:239) [inline] _test_bit at (include/asm-generic/bitops/instrumented-non-atomic.h:142) [inline] node_state (include/linux/nodemask.h:423) [inline] map_benchmark_ioctl (kernel/dma/map_benchmark.c:214) full_proxy_unlocked_ioctl (fs/debugfs/file.c:333) __x64_sys_ioctl (fs/ioctl.c:890) do_syscall_64 (arch/x86/entry/common.c:83) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130) Compare node ids with sane bounds first. NUMA_NO_NODE is considered a special valid case meaning that benchmarking kthreads won't be bound to a cpuset of a given node. Found by Linux Verification Center (linuxtesting.org).
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Out-of-bounds Read
The product reads data past the end, or before the beginning, of the intended buffer.
How developers prevent this class of flaw
- Use a language that provides appropriate memory abstractions.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
- git.kernel.org/stable/c/1ff05e723f7ca30644b8ec3fb093f16312e408ad
- git.kernel.org/stable/c/34a816d8735f3924b74be8e5bf766ade1f3bd10b
- git.kernel.org/stable/c/35d31c8bd4722b107f5a2f5ddddce839de04b936
- git.kernel.org/stable/c/63e7e05a48a35308aeddd7ecccb68363a5988e87
- git.kernel.org/stable/c/c57874265a3c5206d7aece3793bb2fc9abcd7570
Recent Out-of-bounds Read vulnerabilities
- 7.8 High severity
- 7.8 High severity
- 7.1 High severity
- 7.1 High severity
- 7.1 High severity
- 7.1 High severity
Spotted an error? Tell us.