LiveActive security incident?Get immediate response
CVE Record

CVE-2024-26710: powerpc/kasan: Limit KASAN thread size increase to 32KB

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This is a narrow Linux kernel PowerPC issue involving KASAN debug builds. The reported problem is excessive thread stack growth that can cause build errors, not a documented remote compromise. Business urgency is low unless the organization builds or supports custom PowerPC kernels with KASAN enabled.

Executive priority

Treat as a low-priority kernel maintenance item unless PowerPC KASAN builds are operationally important. The main risk described by sources is build disruption, not confirmed production exploitation.

Technical view

The fix limits KASAN-driven PowerPC thread stack enlargement to cases where the existing stack is below 32KB. Earlier behavior doubled stack size, and 32KB stacks could become 64KB, triggering PowerPC assembly operand range build failures. Sources do not provide CVSS, CWE, exploit details, or runtime impact.

Likely exposure

Exposure appears limited to Linux kernel PowerPC builds using KASAN instrumentation, especially custom or development kernels. Typical production systems without PowerPC or without KASAN are unlikely to be affected based on the supplied sources.

Exploitation context

The source bundle does not show active exploitation, CISA KEV listing, public exploit availability, or attacker-controlled exploitation conditions. The described impact is build failure from stack sizing behavior in KASAN-enabled PowerPC kernels.

Researcher notes

Evidence is incomplete for security impact: no CVSS, CWE, exploit narrative, or affected runtime scenario is provided. The issue is best tracked as a Linux stable kernel correctness fix affecting PowerPC KASAN stack sizing.

Mitigation direction

  • Check Linux vendor or distribution guidance for CVE-2024-26710.
  • Update affected PowerPC kernel branches to include the referenced stable fixes.
  • Review custom kernel build settings for PowerPC KASAN usage.
  • Prioritize normal kernel lifecycle patching unless affected builds are blocked.

Validation and detection

  • Inventory systems or build pipelines producing PowerPC Linux kernels.
  • Confirm whether KASAN is enabled in relevant kernel configurations.
  • Check whether the applicable stable commit is present in the kernel tree.
  • Review build logs for the cited switch.S operand range failure.
Prepared
Confidence
medium
Sources
7

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-26710 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
2ADP providers
6Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux9ccf64e763aca088b0d25c1274af42b1a6a45135, b38014874530d3776de75679315e8c1fe04aa89b, 58f396513cb1fa4ef91838c78698d458100cc27c, 18f14afe281648e31ed35c9ad2fcb724c4838ad9unaffected
LinuxLinux6.1.75, 6.6.14, 6.7.2unaffected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.