CVE-2024-26789
What it is
In the Linux kernel, the following vulnerability has been resolved: crypto: arm64/neonbs - fix out-of-bounds access on short input The bit-sliced implementation of AES-CTR operates on blocks of 128 bytes, and will fall back to the plain NEON version for tail blocks or inputs that are shorter than 128 bytes to begin with. It will call straight into the plain NEON asm helper, which performs all memory accesses in granules of 16 bytes (the size of a NEON register). For this reason, the associated plain NEON glue code will copy inputs shorter than 16 bytes into a temporary buffer, given that this is a rare occurrence and it is not worth the effort to work around this in the asm code. The fallback from the bit-sliced NEON version fails to take this into account, potentially resulting in out-of-bounds accesses. So clone the same workaround, and use a temp buffer for short in/outputs.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.2% in the next 30 days (EPSS).
- Severity: 7.8 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.2% · EPSS, next 30 days
- Weakness
- CWE-125 · Out-of-bounds read
- Record status
- Modified
Affected
- Linux Kernel ≤ 6.1.81
- Linux Kernel ≤ 6.6.21
- Linux Kernel ≤ 6.7.9
- Linux Kernel 6.8
Attack profile CVSS 3.1 · 7.8
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2024-26789.md and follow it. Check whether this project is affected by CVE-2024-26789. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/034e2d70b5c7f578200ad09955aeb2aa65d1164a
- https://git.kernel.org/stable/c/1291d278b5574819a7266568ce4c28bce9438705
- https://git.kernel.org/stable/c/1c0cf6d19690141002889d72622b90fc01562ce4
- https://git.kernel.org/stable/c/9e8ecd4908b53941ab6f0f51584ab80c6c6606c4
- https://git.kernel.org/stable/c/034e2d70b5c7f578200ad09955aeb2aa65d1164a
- https://git.kernel.org/stable/c/1291d278b5574819a7266568ce4c28bce9438705
- https://git.kernel.org/stable/c/1c0cf6d19690141002889d72622b90fc01562ce4
- https://git.kernel.org/stable/c/9e8ecd4908b53941ab6f0f51584ab80c6c6606c4
References
- https://git.kernel.org/stable/c/034e2d70b5c7f578200ad09955aeb2aa65d1164a
- https://git.kernel.org/stable/c/1291d278b5574819a7266568ce4c28bce9438705
- https://git.kernel.org/stable/c/1c0cf6d19690141002889d72622b90fc01562ce4
- https://git.kernel.org/stable/c/9e8ecd4908b53941ab6f0f51584ab80c6c6606c4
- https://git.kernel.org/stable/c/034e2d70b5c7f578200ad09955aeb2aa65d1164a
- https://git.kernel.org/stable/c/1291d278b5574819a7266568ce4c28bce9438705
- https://git.kernel.org/stable/c/1c0cf6d19690141002889d72622b90fc01562ce4
- https://git.kernel.org/stable/c/9e8ecd4908b53941ab6f0f51584ab80c6c6606c4