LiveActive security incident?Get immediate response
CVE Record

CVE-2024-40974: powerpc/pseries: Enforce hcall result buffer validity and size

In the Linux kernel, the following vulnerability has been resolved: powerpc/pseries: Enforce hcall result buffer validity and size plpar_hcall(), plpar_hcall9(), and related functions expect callers to provide valid result buffers of certain minimum size. Currently this is communicated only through comments in the code and the compiler has no idea. For example, if I write a bug like this: long retbuf[PLPAR_HCALL_BUFSIZE]; // should be PLPAR_HCALL9_BUFSIZE plpar_hcall9(H_ALLOCATE_VAS_WINDOW, retbuf, ...); This compiles with no diagnostics emitted, but likely results in stack corruption at runtime when plpar_hcall9() stores results past the end of the array. (To be clear this is a contrived example and I have not found a real instance yet.) To make this class of error less likely, we can use explicitly-sized array parameters instead of pointers in the declarations for the hcall APIs. When compiled with -Warray-bounds[1], the code above now provokes a diagnostic like this: error: array argument is too small; is of size 32, callee requires at least 72 [-Werror,-Warray-bounds] 60 | plpar_hcall9(H_ALLOCATE_VAS_WINDOW, retbuf, | ^ ~~~~~~ [1] Enabled for LLVM builds but not GCC for now. See commit 0da6e5fd6c37 ("gcc: disable '-Warray-bounds' for gcc-13 too") and related changes.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Linux PowerPC pSeries hypercall interfaces did not let the compiler reliably detect undersized result buffers. A mistaken caller could therefore overwrite kernel stack memory, potentially causing crashes or broader compromise. The source describes only a contrived example and says no real vulnerable caller was found.

Executive priority

Treat this as targeted high-priority kernel maintenance for PowerPC pSeries fleets, not an enterprise-wide emergency. Prioritize internet-facing or multi-user relevant systems, but first confirm platform applicability because the disclosed example was theoretical and active exploitation is unsupported.

Technical view

The fix declares plpar_hcall(), plpar_hcall9(), and related result parameters as explicitly sized arrays. This lets supported array-bounds diagnostics reject buffers smaller than the API requires. The stated runtime consequence of such misuse is an out-of-bounds result write and possible stack corruption; LLVM builds had the relevant warning enabled, while GCC builds did not.

Likely exposure

Exposure is concentrated in Linux systems using the PowerPC pSeries subsystem and affected kernel code. It is not presented as a general vulnerability across every Linux architecture. Custom or out-of-tree kernel callers warrant additional review. Confirm exposure through architecture, kernel package, and downstream backport records rather than version strings alone.

Exploitation context

The supplied CVSS is 7.8 and describes a local, low-privilege path requiring no user interaction. However, KEV is false, no cited source reports active exploitation, and the disclosure says no real undersized caller was found. Practical exploitation therefore remains unsubstantiated by this bundle.

Researcher notes

The record supplies no CWE and identifies no concrete vulnerable call site. The change primarily strengthens compile-time API contracts, reducing the chance that future or external callers create a runtime overwrite. Severity reflects potential kernel stack corruption, while real-world reachability and trigger conditions remain insufficiently evidenced.

Mitigation direction

  • Inventory PowerPC pSeries systems and map their running kernels to vendor advisories.
  • Apply a supported kernel update incorporating the referenced stable fix or documented downstream backport.
  • Reboot affected systems into the updated kernel and retire superseded boot entries where operationally appropriate.
  • For custom kernels, adopt the corrected declarations and enable supported array-bounds diagnostics.
  • Consult the Linux distribution or kernel vendor if package remediation status is unclear.

Validation and detection

  • Confirm whether each candidate system uses PowerPC pSeries functionality.
  • Compare installed kernel packages and source provenance with vendor backport documentation.
  • After maintenance, verify the updated kernel is actually running.
  • Review custom and out-of-tree hypercall callers for correctly sized result buffers.
  • Confirm builds report undersized array arguments where the compiler supports that diagnostic.
Prepared
Confidence
medium
Sources
5

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-40974 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
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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.

1CVSS vectors
3Timeline events
2ADP providers
10Source links

SSVC decision data

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

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2024-40974Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxb9377ffc3a03cde558d76349a262a1adbb6d3112, b9377ffc3a03cde558d76349a262a1adbb6d3112, b9377ffc3a03cde558d76349a262a1adbb6d3112, b9377ffc3a03cde558d76349a262a1adbb6d3112, b9377ffc3a03cde558d76349a262a1adbb6d3112, b9377ffc3a03cde558d76349a262a1adbb6d3112, b9377ffc3a03cde558d76349a262a1adbb6d3112, b9377ffc3a03cde558d76349a262a1adbb6d3112unaffected
LinuxLinux2.6.19, 0, 4.19.317, 5.4.279, 5.10.221, 5.15.162, 6.1.96, 6.6.36, 6.9.7, 6.10affected
Weakness

CWE details

No CWE listed

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