Linux: Out-of-bounds Write
CVE-2024-40901 is a high-severity out-of-bounds write vulnerability in Linux, with a CVSS 3.1 base score of 7.8 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 e9bce7c751f6d6c7be88c0bc081a66aaf61a23ee, 19649e49a6df07cd2e03e0a11396fd3a99485ec2, 0081d2b3ae0a17a86b8cc0fa3c8bdc54e233ba16 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.31% 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 e9bce7c751f6d6c7be88c0bc081a66aaf61a23ee or 19649e49a6df07cd2e03e0a11396fd3a99485ec2 or 0081d2b3ae0a17a86b8cc0fa3c8bdc54e233ba16 or 521f333e644c4246ca04a4fc4772edc53dd2a801, whichever matches your release line, or a later version.
- Update SIMATIC S7-1500 CPU 1518-4 PN/DP MFP to V3.1.5 or a later version.
- Update SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP to V3.1.5 or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | c696f7b83edeac804e898952058089143f49ca0a up to, but not including, e9bce7c751f6d6c7be88c0bc081a66aaf61a23ee; c696f7b83edeac804e898952058089143f49ca0a up to, but not including, 19649e49a6df07cd2e03e0a11396fd3a99485ec2; c696f7b83edeac804e898952058089143f49ca0a up to, but not including, 0081d2b3ae0a17a86b8cc0fa3c8bdc54e233ba16; c696f7b83edeac804e898952058089143f49ca0a up to, but not including, 521f333e644c4246ca04a4fc4772edc53dd2a801; c696f7b83edeac804e898952058089143f49ca0a up to, but not including, 46bab2bcd771e725ff5ca3a68ba68cfeac45676c; c696f7b83edeac804e898952058089143f49ca0a up to, but not including, 9079338c5a0d1f1fee34fb1c9e99b754efe414c5; c696f7b83edeac804e898952058089143f49ca0a up to, but not including, 18abb5db0aa9b2d48f7037a88b41af2eef821674; c696f7b83edeac804e898952058089143f49ca0a up to, but not including, 4254dfeda82f20844299dca6c38cbffcfd499f41; and 1 more ranges | e9bce7c751f6d6c7be88c0bc081a66aaf61a23ee, 19649e49a6df07cd2e03e0a11396fd3a99485ec2, 0081d2b3ae0a17a86b8cc0fa3c8bdc54e233ba16, 521f333e644c4246ca04a4fc4772edc53dd2a801, 46bab2bcd771e725ff5ca3a68ba68cfeac45676c, 9079338c5a0d1f1fee34fb1c9e99b754efe414c5 |
| Siemens | SIMATIC S7-1500 CPU 1518-4 PN/DP MFP | V3.1.0 up to, but not including, V3.1.5 | V3.1.5 |
| Siemens | SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP | V3.1.0 up to, but not including, V3.1.5 | V3.1.5 |
| Siemens | SIPLUS S7-1500 CPU 1518-4 PN/DP MFP | V3.1.0 up to, but not including, V3.1.5 | V3.1.5 |
| Linux | Linux Kernel | 4.10 up to, but not including, 4.19.317; 4.20 up to, but not including, 5.4.279; 5.5 up to, but not including, 5.10.221; 5.11 up to, but not including, 5.15.162; 5.16 up to, but not including, 6.1.95; 6.2 up to, but not including, 6.6.35; 6.7 up to, but not including, 6.9.6; 6.10 | 4.19.317, 5.4.279, 5.10.221, 5.15.162, 6.1.95, 6.6.35 |
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
- HighData or code can be modified at will.
- 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:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.3 | High | CNA |
| CVSS 3.1 | 7.8 | High | NVD |
Official description
In the Linux kernel, the following vulnerability has been resolved: scsi: mpt3sas: Avoid test/set_bit() operating in non-allocated memory There is a potential out-of-bounds access when using test_bit() on a single word. The test_bit() and set_bit() functions operate on long values, and when testing or setting a single word, they can exceed the word boundary. KASAN detects this issue and produces a dump: BUG: KASAN: slab-out-of-bounds in _scsih_add_device.constprop.0 (./arch/x86/include/asm/bitops.h:60 ./include/asm-generic/bitops/instrumented-atomic.h:29 drivers/scsi/mpt3sas/mpt3sas_scsih.c:7331) mpt3sas Write of size 8 at addr ffff8881d26e3c60 by task kworker/u1536:2/2965 For full log, please look at [1]. Make the allocation at least the size of sizeof(unsigned long) so that set_bit() and test_bit() have sufficient room for read/write operations without overwriting unallocated memory. [1] Link: https://lore.kernel.org/all/[email protected]/
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
- git.kernel.org/stable/c/0081d2b3ae0a17a86b8cc0fa3c8bdc54e233ba16Mailing List
- git.kernel.org/stable/c/18abb5db0aa9b2d48f7037a88b41af2eef821674Mailing List
- git.kernel.org/stable/c/19649e49a6df07cd2e03e0a11396fd3a99485ec2Mailing List
- git.kernel.org/stable/c/4254dfeda82f20844299dca6c38cbffcfd499f41Mailing List
- git.kernel.org/stable/c/46bab2bcd771e725ff5ca3a68ba68cfeac45676cMailing List
- git.kernel.org/stable/c/521f333e644c4246ca04a4fc4772edc53dd2a801Mailing List
- git.kernel.org/stable/c/9079338c5a0d1f1fee34fb1c9e99b754efe414c5Mailing List
- git.kernel.org/stable/c/e9bce7c751f6d6c7be88c0bc081a66aaf61a23eeMailing List
Other references
Recent Out-of-bounds Write vulnerabilities
- 7.8 High severity
- 7.8 High severity
- 7.1 High severity
- 7.0 High severity
- 7.5 High severity
- 8.2 High severity
Spotted an error? Tell us.