Linux: Out-of-bounds Read
CVE-2024-57945 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 04350304428063da6a55a8a4597d409dc69148b2, 92f08673d3f1893191323572f60e3c62f2e57c2f, a4a7ac3d266008018f05fae53060fcb331151a14 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.21% 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 04350304428063da6a55a8a4597d409dc69148b2 or 92f08673d3f1893191323572f60e3c62f2e57c2f or a4a7ac3d266008018f05fae53060fcb331151a14 or d2bd51954ac8377c2f1eb1813e694788998add66, whichever matches your release line, or a later version.
- Update Linux Kernel to 5.11 or 5.16 or 6.1.140 or 6.6.72, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | 8af1c121b0102041809bc137ec600d1865eaeedd up to, but not including, 04350304428063da6a55a8a4597d409dc69148b2; 8310080799b40fd9f2a8b808c657269678c149af up to, but not including, 92f08673d3f1893191323572f60e3c62f2e57c2f; a278d5c60f21aa15d540abb2f2da6e6d795c3e6e up to, but not including, a4a7ac3d266008018f05fae53060fcb331151a14; a11dd49dcb9376776193e15641f84fcc1e5980c9 up to, but not including, d2bd51954ac8377c2f1eb1813e694788998add66; a11dd49dcb9376776193e15641f84fcc1e5980c9 up to, but not including, f754f27e98f88428aaf6be6e00f5cbce97f62d4b; 5941a90c55d3bfba732b32208d58d997600b44ef; 2a1728c15ec4f45ed9248ae22f626541c179bfbe; 5.10.212 up to, but not including, 5.10.258; and 5 more ranges | 04350304428063da6a55a8a4597d409dc69148b2, 92f08673d3f1893191323572f60e3c62f2e57c2f, a4a7ac3d266008018f05fae53060fcb331151a14, d2bd51954ac8377c2f1eb1813e694788998add66, f754f27e98f88428aaf6be6e00f5cbce97f62d4b, 5.10.258 |
| Linux | Linux Kernel | 5.10.212 up to, but not including, 5.11; 5.15.151 up to, but not including, 5.16; 6.1.81 up to, but not including, 6.1.140; 6.6.21 up to, but not including, 6.6.72; 6.7.9 up to, but not including, 6.8; 6.8.1 up to, but not including, 6.12.10; 6.8; 6.13 | 5.11, 5.16, 6.1.140, 6.6.72, 6.8, 6.12.10 |
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.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.8 | High | CNA |
| CVSS 3.1 | 7.1 | High | NVD |
Official description
In the Linux kernel, the following vulnerability has been resolved: riscv: mm: Fix the out of bound issue of vmemmap address In sparse vmemmap model, the virtual address of vmemmap is calculated as: ((struct page *)VMEMMAP_START - (phys_ram_base >> PAGE_SHIFT)). And the struct page's va can be calculated with an offset: (vmemmap + (pfn)). However, when initializing struct pages, kernel actually starts from the first page from the same section that phys_ram_base belongs to. If the first page's physical address is not (phys_ram_base >> PAGE_SHIFT), then we get an va below VMEMMAP_START when calculating va for it's struct page. For example, if phys_ram_base starts from 0x82000000 with pfn 0x82000, the first page in the same section is actually pfn 0x80000. During init_unavailable_range(), we will initialize struct page for pfn 0x80000 with virtual address ((struct page *)VMEMMAP_START - 0x2000), which is below VMEMMAP_START as well as PCI_IO_END. This commit fixes this bug by introducing a new variable 'vmemmap_start_pfn' which is aligned with memory section size and using it to calculate vmemmap address instead of phys_ram_base.
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.
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
Other references
Recent Out-of-bounds Read vulnerabilities
- 7.5 High severity
- 7.1 High severity
- 7.1 High severity
- 8.8 High severity
- 7.5 High severity
- 7.8 High severity
Spotted an error? Tell us.