Linux: Out-of-bounds Read
CVE-2024-50115 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 76ce386feb14ec9a460784fcd495d8432acce7a5, 58cb697d80e669c56197f703e188867c8c54c494, 6876793907cbe19d42e9edc8c3315a21e06c32ae 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 76ce386feb14ec9a460784fcd495d8432acce7a5 or 58cb697d80e669c56197f703e188867c8c54c494 or 6876793907cbe19d42e9edc8c3315a21e06c32ae or 2c4adc9b192a0815fe58a62bc0709449416cc884, whichever matches your release line, or a later version.
- Update Linux Kernel to 5.10.229 or 5.15.170 or 6.1.115 or 6.6.59, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | e4e517b4be019787ada4cbbce2f04570c21b0cbd up to, but not including, 76ce386feb14ec9a460784fcd495d8432acce7a5; e4e517b4be019787ada4cbbce2f04570c21b0cbd up to, but not including, 58cb697d80e669c56197f703e188867c8c54c494; e4e517b4be019787ada4cbbce2f04570c21b0cbd up to, but not including, 6876793907cbe19d42e9edc8c3315a21e06c32ae; e4e517b4be019787ada4cbbce2f04570c21b0cbd up to, but not including, 2c4adc9b192a0815fe58a62bc0709449416cc884; e4e517b4be019787ada4cbbce2f04570c21b0cbd up to, but not including, 426682afec71ea3f889b972d038238807b9443e4; e4e517b4be019787ada4cbbce2f04570c21b0cbd up to, but not including, f559b2e9c5c5308850544ab59396b7d53cfc67bd; 3.2 | 76ce386feb14ec9a460784fcd495d8432acce7a5, 58cb697d80e669c56197f703e188867c8c54c494, 6876793907cbe19d42e9edc8c3315a21e06c32ae, 2c4adc9b192a0815fe58a62bc0709449416cc884, 426682afec71ea3f889b972d038238807b9443e4, f559b2e9c5c5308850544ab59396b7d53cfc67bd |
| Linux | Linux Kernel | 3.2 up to, but not including, 5.10.229; 5.11 up to, but not including, 5.15.170; 5.16 up to, but not including, 6.1.115; 6.2 up to, but not including, 6.6.59; 6.7 up to, but not including, 6.11.6; 6.12 | 5.10.229, 5.15.170, 6.1.115, 6.6.59, 6.11.6 |
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 | 8.4 | High | CNA |
| 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: KVM: nSVM: Ignore nCR3[4:0] when loading PDPTEs from memory Ignore nCR3[4:0] when loading PDPTEs from memory for nested SVM, as bits 4:0 of CR3 are ignored when PAE paging is used, and thus VMRUN doesn't enforce 32-byte alignment of nCR3. In the absolute worst case scenario, failure to ignore bits 4:0 can result in an out-of-bounds read, e.g. if the target page is at the end of a memslot, and the VMM isn't using guard pages. Per the APM: The CR3 register points to the base address of the page-directory-pointer table. The page-directory-pointer table is aligned on a 32-byte boundary, with the low 5 address bits 4:0 assumed to be 0. And the SDM's much more explicit: 4:0 Ignored Note, KVM gets this right when loading PDPTRs, it's only the nSVM flow that is broken.
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/2c4adc9b192a0815fe58a62bc0709449416cc884
- git.kernel.org/stable/c/426682afec71ea3f889b972d038238807b9443e4
- git.kernel.org/stable/c/58cb697d80e669c56197f703e188867c8c54c494
- git.kernel.org/stable/c/6876793907cbe19d42e9edc8c3315a21e06c32ae
- git.kernel.org/stable/c/76ce386feb14ec9a460784fcd495d8432acce7a5
- git.kernel.org/stable/c/f559b2e9c5c5308850544ab59396b7d53cfc67bd
Other references
Recent Out-of-bounds Read vulnerabilities
- 7.1 High severity
- 7.1 High severity
- 8.2 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
Spotted an error? Tell us.