Linux: Out-of-bounds Write
CVE-2024-26730 is a high-severity out-of-bounds write vulnerability in Linux, with a CVSS 3.1 base score of 7.0 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 745aa03c513f1ba12cb98495467676f7acf3fffd, f006c45a3ea424f8f6c8e4b9283bc245ce2a4d0f, c196387820c9214c5ceaff56d77303c82514b8b1 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.25% 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 745aa03c513f1ba12cb98495467676f7acf3fffd or f006c45a3ea424f8f6c8e4b9283bc245ce2a4d0f or c196387820c9214c5ceaff56d77303c82514b8b1 or d56e460e19ea8382f813eb489730248ec8d7eb73, whichever matches your release line, or a later version.
- Update Linux Kernel to 6.6.19 or 6.7.7, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | 4283b0e29d58c6b11e2e45a5afcab401da4e7994 up to, but not including, 745aa03c513f1ba12cb98495467676f7acf3fffd; b7f1f7b2523a6a4382f12fe953380b847b80e09d up to, but not including, f006c45a3ea424f8f6c8e4b9283bc245ce2a4d0f; b7f1f7b2523a6a4382f12fe953380b847b80e09d up to, but not including, c196387820c9214c5ceaff56d77303c82514b8b1; b7f1f7b2523a6a4382f12fe953380b847b80e09d up to, but not including, d56e460e19ea8382f813eb489730248ec8d7eb73; 6.6 | 745aa03c513f1ba12cb98495467676f7acf3fffd, f006c45a3ea424f8f6c8e4b9283bc245ce2a4d0f, c196387820c9214c5ceaff56d77303c82514b8b1, d56e460e19ea8382f813eb489730248ec8d7eb73 |
| Linux | Linux Kernel | 6.6 up to, but not including, 6.6.19; 6.7 up to, but not including, 6.7.7; 6.6.19; 6.8 | 6.6.19, 6.7.7 |
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
- HighSuccess depends on conditions outside the attacker's control.
- 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
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.3 | High | CNA |
| CVSS 3.1 | 7.0 | High | NVD |
Official description
In the Linux kernel, the following vulnerability has been resolved: hwmon: (nct6775) Fix access to temperature configuration registers The number of temperature configuration registers does not always match the total number of temperature registers. This can result in access errors reported if KASAN is enabled. BUG: KASAN: global-out-of-bounds in nct6775_probe+0x5654/0x6fe9 nct6775_core
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Out-of-bounds Write
The product writes data past the end, or before the beginning, of the intended buffer.
How developers prevent this class of flaw
- Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer. Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Examples include the Safe C String Library (SafeStr) by Messier and Viega, and the Strsafe.h library from Microsoft. These libraries provide safer versions of overflow-prone string-handling functions.
- Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.
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 Write vulnerabilities
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
Spotted an error? Tell us.