CVE-2024-26710

powerpc/kasan: Limit KASAN thread size increase to 32KB

MEDIUM
5.5
CVSS Score
Published: April 3, 2024 at 02:55 PM UTC
Updated: June 17, 2026 at 07:18 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

6.1.75 ≤ v < 6.1.766.1.75 ≤ v < 6.1.796.6.14 ≤ v < 6.6.186.7.2 ≤ v < 6.7.618f14afe281648e31ed35c9ad2fcb724c4838ad958f396513cb1fa4ef91838c78698d458100cc27c6.1.756.6.146.7.29ccf64e763aca088b0d25c1274af42b1a6a45135b38014874530d3776de75679315e8c1fe04aa89b
Vendor states this is fixed in 4cc31fa07445879a13750cb061bb8c2654975fcb (fixed)
Vendor states this is fixed in b29b16bd836a838b7690f80e37f8376414c74cbe (fixed)
Vendor states this is fixed in f1acb109505d983779bbb7e20a1ee6244d2b5736 (fixed)
Vendor states this is fixed in f9a4c401bf4c5af3437ad221c0a5880a518068d4 (fixed)
Affected range stops below 6.1.76, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.1.79, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.6.18, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.7.6, so it looks safe — our inference, not a vendor statement

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-770

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card