Linux: Out-of-bounds Read
CVE-2024-50278 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 e492f71854ce03474d49e87fd98b8df1f7cd1d2d, 2222b0929d00e2d13732b799b63be391b5de4492, 483b7261b35a9d369082ab298a6670912243f0be 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.26% 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 e492f71854ce03474d49e87fd98b8df1f7cd1d2d or 2222b0929d00e2d13732b799b63be391b5de4492 or 483b7261b35a9d369082ab298a6670912243f0be or fdef3b94dfebd57e3077a578b6e309a2bb6fa688, whichever matches your release line, or a later version.
- Update Linux Kernel to 4.19.324 or 5.4.286 or 5.10.230 or 5.15.172, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | f494a9c6b1b6dd9a9f21bbb75d9210d478eeb498 up to, but not including, e492f71854ce03474d49e87fd98b8df1f7cd1d2d; f494a9c6b1b6dd9a9f21bbb75d9210d478eeb498 up to, but not including, 2222b0929d00e2d13732b799b63be391b5de4492; f494a9c6b1b6dd9a9f21bbb75d9210d478eeb498 up to, but not including, 483b7261b35a9d369082ab298a6670912243f0be; f494a9c6b1b6dd9a9f21bbb75d9210d478eeb498 up to, but not including, fdef3b94dfebd57e3077a578b6e309a2bb6fa688; f494a9c6b1b6dd9a9f21bbb75d9210d478eeb498 up to, but not including, c52ec00cb2f9bebfada22edcc0db385b910a1cdb; f494a9c6b1b6dd9a9f21bbb75d9210d478eeb498 up to, but not including, 036dd6e3d2638103e0092864577ea1d091466b86; f494a9c6b1b6dd9a9f21bbb75d9210d478eeb498 up to, but not including, 13ed3624c6ef283acefa4cc42cc8ae54fd4391a4; f494a9c6b1b6dd9a9f21bbb75d9210d478eeb498 up to, but not including, c0ade5d98979585d4f5a93e4514c2e9a65afa08d; and 1 more ranges | e492f71854ce03474d49e87fd98b8df1f7cd1d2d, 2222b0929d00e2d13732b799b63be391b5de4492, 483b7261b35a9d369082ab298a6670912243f0be, fdef3b94dfebd57e3077a578b6e309a2bb6fa688, c52ec00cb2f9bebfada22edcc0db385b910a1cdb, 036dd6e3d2638103e0092864577ea1d091466b86 |
| Linux | Linux Kernel | 3.13 up to, but not including, 4.19.324; 4.20 up to, but not including, 5.4.286; 5.5 up to, but not including, 5.10.230; 5.11 up to, but not including, 5.15.172; 5.16 up to, but not including, 6.1.117; 6.2 up to, but not including, 6.6.61; 6.7 up to, but not including, 6.11.8; 6.12 | 4.19.324, 5.4.286, 5.10.230, 5.15.172, 6.1.117, 6.6.61 |
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.1 | High | NVD |
| CVSS 3.1 | 7.1 | High | CISA (ADP) |
Official description
In the Linux kernel, the following vulnerability has been resolved: dm cache: fix potential out-of-bounds access on the first resume Out-of-bounds access occurs if the fast device is expanded unexpectedly before the first-time resume of the cache table. This happens because expanding the fast device requires reloading the cache table for cache_create to allocate new in-core data structures that fit the new size, and the check in cache_preresume is not performed during the first resume, leading to the issue. Reproduce steps: 1. prepare component devices: dmsetup create cmeta --table "0 8192 linear /dev/sdc 0" dmsetup create cdata --table "0 65536 linear /dev/sdc 8192" dmsetup create corig --table "0 524288 linear /dev/sdc 262144" dd if=/dev/zero of=/dev/mapper/cmeta bs=4k count=1 oflag=direct 2. load a cache table of 512 cache blocks, and deliberately expand the fast device before resuming the cache, making the in-core data structures inadequate. dmsetup create cache --notable dmsetup reload cache --table "0 524288 cache /dev/mapper/cmeta \ /dev/mapper/cdata /dev/mapper/corig 128 2 metadata2 writethrough smq 0" dmsetup reload cdata --table "0 131072 linear /dev/sdc 8192" dmsetup resume cdata dmsetup resume cache 3. suspend the cache to write out the in-core dirty bitset and hint array, leading to out-of-bounds access to the dirty bitset at offset 0x40: dmsetup suspend cache KASAN reports: BUG: KASAN: vmalloc-out-of-bounds in is_dirty_callback+0x2b/0x80 Read of size 8 at addr ffffc90000085040 by task dmsetup/90 (...snip...) The buggy address belongs to the virtual mapping at [ffffc90000085000, ffffc90000087000) created by: cache_ctr+0x176a/0x35f0 (...snip...) Memory state around the buggy address: ffffc90000084f00: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 ffffc90000084f80: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 >ffffc90000085000: 00 00 00 00 00 00 00 00 f8 f8 f8 f8 f8 f8 f8 f8 ^ ffffc90000085080: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 ffffc90000085100: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 Fix by checking the size change on the first resume.
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/036dd6e3d2638103e0092864577ea1d091466b86
- git.kernel.org/stable/c/13ed3624c6ef283acefa4cc42cc8ae54fd4391a4
- git.kernel.org/stable/c/2222b0929d00e2d13732b799b63be391b5de4492
- git.kernel.org/stable/c/483b7261b35a9d369082ab298a6670912243f0be
- git.kernel.org/stable/c/c0ade5d98979585d4f5a93e4514c2e9a65afa08d
- git.kernel.org/stable/c/c52ec00cb2f9bebfada22edcc0db385b910a1cdb
- git.kernel.org/stable/c/e492f71854ce03474d49e87fd98b8df1f7cd1d2d
- git.kernel.org/stable/c/fdef3b94dfebd57e3077a578b6e309a2bb6fa688
Other references
Recent Out-of-bounds Read vulnerabilities
- 7.1 High severity
- 7.1 High severity
- 7.1 High severity
- 7.1 High severity
- 7.8 High severity
- 7.8 High severity
Spotted an error? Tell us.