powerpc/pseries: Enforce hcall result buffer validity and size
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.30% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 19c166ee42cf16d8b156a6cb4544122d9a65d3ca, 262e942ff5a839b9e4f3302a8987928b0c8b8a2d, 3ad0034910a57aa88ed9976b1431b7b8c84e0048.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 19c166ee42cf16d8b156a6cb4544122d9a65d3ca, 262e942ff5a839b9e4f3302a8987928b0c8b8a2d, 3ad0034910a57aa88ed9976b1431b7b8c84e0048 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jul 12, 2024
- Updated
- Aug 5, 2026
- EPSS
- 0.3% · 21th percentile
- CWE
- CWE-787
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.8
- CNA · Linux
- 7.8
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernelbefore 4.19.317
- linux linux kernel4.20 and later · before 5.4.279
- linux linux kernel5.5 and later · before 5.10.221
- linux linux kernel5.11 and later · before 5.15.162
- linux linux kernel5.16 and later · before 6.1.96
- linux linux kernel6.2 and later · before 6.6.36
- linux linux kernel6.7 and later · before 6.9.7
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 2.6.19affected
- b9377ffc3a03cde558d76349a262a1adbb6d3112 and later · before acf2b80c31c37acab040baa3cf5f19fbd5140b18affected · git
- b9377ffc3a03cde558d76349a262a1adbb6d3112 and later · before 19c166ee42cf16d8b156a6cb4544122d9a65d3caaffected · git
- b9377ffc3a03cde558d76349a262a1adbb6d3112 and later · before a8c988d752b3d98d5cc1e3929c519a55ef55426caffected · git
- b9377ffc3a03cde558d76349a262a1adbb6d3112 and later · before 262e942ff5a839b9e4f3302a8987928b0c8b8a2daffected · git
- b9377ffc3a03cde558d76349a262a1adbb6d3112 and later · before 8aa11aa001576bf3b00dcb8559564ad7a3113588affected · git
- b9377ffc3a03cde558d76349a262a1adbb6d3112 and later · before 3ad0034910a57aa88ed9976b1431b7b8c84e0048affected · git
- b9377ffc3a03cde558d76349a262a1adbb6d3112 and later · before aa6107dcc4ce9a3451f2d729204713783b657257affected · git
- b9377ffc3a03cde558d76349a262a1adbb6d3112 and later · before ff2e185cf73df480ec69675936c4ee75a445c3e4affected · git
- before 2.6.19not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.99-1 | 6.1.99-1 |
| Debian:13 | linux | before 6.9.7-1 | 6.9.7-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
- CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV83Now
Published before and after this one in the same product
- ← EarlierCVE-2024-40972Jul 12, 2024 · ext4: do not create EA inode under buffer lock22Monitor
- ← EarlierCVE-2024-40973Jul 12, 2024 · media: mtk-vcodec: potential null pointer deference in SCP22Monitor
- Later →CVE-2024-40975Jul 12, 2024 · platform/x86: x86-android-tablets: Unregister devices in reverse order22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 19c166ee42cf16d8b156a6cb4544122d9a65d3ca | Vendor (CNA) |
| Linux Linux | 262e942ff5a839b9e4f3302a8987928b0c8b8a2d | Vendor (CNA) |
| Linux Linux | 3ad0034910a57aa88ed9976b1431b7b8c84e0048 | Vendor (CNA) |
| Linux Linux | 8aa11aa001576bf3b00dcb8559564ad7a3113588 | Vendor (CNA) |
| Linux Linux | a8c988d752b3d98d5cc1e3929c519a55ef55426c | Vendor (CNA) |
| Linux Linux | aa6107dcc4ce9a3451f2d729204713783b657257 | Vendor (CNA) |
| Linux Linux | acf2b80c31c37acab040baa3cf5f19fbd5140b18 | Vendor (CNA) |
| Linux Linux | ff2e185cf73df480ec69675936c4ee75a445c3e4 | Vendor (CNA) |
| debian:linux | 6.1.99-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-0942 · Jul 16, 2024(Linux Kernel Güncellemesi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-787 · Out-of-bounds WriteCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (8 more)Show less
- git.kernel.org/stable/c/262e942ff5a839b9e4f3302a8987928b0c8b8a2d
- git.kernel.org/stable/c/3ad0034910a57aa88ed9976b1431b7b8c84e0048
- git.kernel.org/stable/c/8aa11aa001576bf3b00dcb8559564ad7a3113588
- git.kernel.org/stable/c/a8c988d752b3d98d5cc1e3929c519a55ef55426c
- git.kernel.org/stable/c/aa6107dcc4ce9a3451f2d729204713783b657257
- git.kernel.org/stable/c/acf2b80c31c37acab040baa3cf5f19fbd5140b18
- git.kernel.org/stable/c/ff2e185cf73df480ec69675936c4ee75a445c3e4
- lists.debian.org/debian-lts-announce/2025/01/msg00001.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.