Linux: Out-of-bounds Read
CVE-2024-41014 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 d1e3efe783365db59da88f08a2e0bfe1cc95b143, 7cd9f0a33e738cd58876f1bc8d6c1aa5bc4fc8c1, fb63435b7c7dc112b1ae1baea5486e0a6e27b196 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.24% 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 d1e3efe783365db59da88f08a2e0bfe1cc95b143 or 7cd9f0a33e738cd58876f1bc8d6c1aa5bc4fc8c1 or fb63435b7c7dc112b1ae1baea5486e0a6e27b196, whichever matches your release line, or a later version.
- Update Linux Kernel to 6.1.120 or 6.6.64 or 6.11, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to, but not including, d1e3efe783365db59da88f08a2e0bfe1cc95b143; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to, but not including, 7cd9f0a33e738cd58876f1bc8d6c1aa5bc4fc8c1; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 up to, but not including, fb63435b7c7dc112b1ae1baea5486e0a6e27b196; 2.6.12 | d1e3efe783365db59da88f08a2e0bfe1cc95b143, 7cd9f0a33e738cd58876f1bc8d6c1aa5bc4fc8c1, fb63435b7c7dc112b1ae1baea5486e0a6e27b196 |
| Linux | Linux Kernel | before 6.1.120; 6.2 up to, but not including, 6.6.64; 6.7 up to, but not including, 6.11 | 6.1.120, 6.6.64, 6.11 |
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 | CNA |
| CVSS 3.1 | 7.1 | High | NVD |
Official description
In the Linux kernel, the following vulnerability has been resolved: xfs: add bounds checking to xlog_recover_process_data There is a lack of verification of the space occupied by fixed members of xlog_op_header in the xlog_recover_process_data. We can create a crafted image to trigger an out of bounds read by following these steps: 1) Mount an image of xfs, and do some file operations to leave records 2) Before umounting, copy the image for subsequent steps to simulate abnormal exit. Because umount will ensure that tail_blk and head_blk are the same, which will result in the inability to enter xlog_recover_process_data 3) Write a tool to parse and modify the copied image in step 2 4) Make the end of the xlog_op_header entries only 1 byte away from xlog_rec_header->h_size 5) xlog_rec_header->h_num_logops++ 6) Modify xlog_rec_header->h_crc Fix: Add a check to make sure there is sufficient space to access fixed members of xlog_op_header.
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
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.1 High severity
Spotted an error? Tell us.