CVE-2024-26710
What it is
In the Linux kernel, the following vulnerability has been resolved: powerpc/kasan: Limit KASAN thread size increase to 32KB KASAN is seen to increase stack usage, to the point that it was reported to lead to stack overflow on some 32-bit machines (see link). To avoid overflows the stack size was doubled for KASAN builds in commit 3e8635fb2e07 ("powerpc/kasan: Force thread size increase with KASAN"). However with a 32KB stack size to begin with, the doubling leads to a 64KB stack, which causes build errors: arch/powerpc/kernel/switch.S:249: Error: operand out of range (0x000000000000fe50 is not between 0xffffffffffff8000 and 0x0000000000007fff) Although the asm could be reworked, in practice a 32KB stack seems sufficient even for KASAN builds - the additional usage seems to be in the 2-3KB range for a 64-bit KASAN build. So only increase the stack for KASAN if the stack size is < 32KB.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of 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: 5.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.2% · EPSS, next 30 days
- Weakness
- CWE-770 · Allocation without limits
- Record status
- Modified
Affected
- Linux Kernel < 6.1.79
- Linux Kernel < 6.6.18
- Linux Kernel < 6.7.6
Attack profile CVSS 3.1 · 5.5
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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-26710.md and follow it. Check whether this project is affected by CVE-2024-26710. 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/4cc31fa07445879a13750cb061bb8c2654975fcb
- https://git.kernel.org/stable/c/b29b16bd836a838b7690f80e37f8376414c74cbe
- https://git.kernel.org/stable/c/f1acb109505d983779bbb7e20a1ee6244d2b5736
- https://git.kernel.org/stable/c/4297217bcf1f0948a19c2bacc6b68d92e7778ad9
- https://git.kernel.org/stable/c/4cc31fa07445879a13750cb061bb8c2654975fcb
- https://git.kernel.org/stable/c/b29b16bd836a838b7690f80e37f8376414c74cbe
- https://git.kernel.org/stable/c/f1acb109505d983779bbb7e20a1ee6244d2b5736
References
- https://git.kernel.org/stable/c/4cc31fa07445879a13750cb061bb8c2654975fcb
- https://git.kernel.org/stable/c/b29b16bd836a838b7690f80e37f8376414c74cbe
- https://git.kernel.org/stable/c/f1acb109505d983779bbb7e20a1ee6244d2b5736
- https://git.kernel.org/stable/c/f9a4c401bf4c5af3437ad221c0a5880a518068d4
- https://git.kernel.org/stable/c/4297217bcf1f0948a19c2bacc6b68d92e7778ad9
- https://git.kernel.org/stable/c/4cc31fa07445879a13750cb061bb8c2654975fcb
- https://git.kernel.org/stable/c/b29b16bd836a838b7690f80e37f8376414c74cbe
- https://git.kernel.org/stable/c/f1acb109505d983779bbb7e20a1ee6244d2b5736