CVE-2026-99124: s390/pci: Fix leak of uninitialized kernel data in SCLP report
Noroxi assessment
Priority: Monitor (action score 0/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.17% (FIRST EPSS).
- Fixed version: Linux Linux 126a7c227d8543e13903dd5622640c1f0fcc5a16, 332f2d867f64dd530517e9a58394e3eab454df12, 61ce6f9a527932f4482ebe00847490f17d63a0d1; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 Release Notes.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 126a7c227d8543e13903dd5622640c1f0fcc5a16, 332f2d867f64dd530517e9a58394e3eab454df12, 61ce6f9a527932f4482ebe00847490f17d63a0d1; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 Release Notes 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: s390/pci: Fix leak of uninitialized kernel data in SCLP report While report_error_write() checks that the provided buffer is at least as large as the header struct, but not that it is large enough to contain the report with the length claimed by report->length. If user-space provides a short buffer, meaning a larger report->length than the actually written payload, up to around 4K of kernel data from past the kmalloc(len + 1) sized buffer allocated in kernfs_fop_write_iter() will leak into the SCLP report. However, as the entity processing the SCLP is privileged and able to access at least the page including the report, this does not leak data that entity could not access but it is still an out of bounds read and a malformed error report that should be rejected.
- Published
- Oct 28, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
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.
—
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
- 4.7affected
- 368704a65be8620df795ccbeb44e025dafbc3e1f and later · before ad1be38823d4b6dbc88648da296ca0c0f8824a55affected · git
- 368704a65be8620df795ccbeb44e025dafbc3e1f and later · before 61ce6f9a527932f4482ebe00847490f17d63a0d1affected · git
- 368704a65be8620df795ccbeb44e025dafbc3e1f and later · before 332f2d867f64dd530517e9a58394e3eab454df12affected · git
- 368704a65be8620df795ccbeb44e025dafbc3e1f and later · before ff31c34e921d11c7da3d7664ce495106267ca408affected · git
- 368704a65be8620df795ccbeb44e025dafbc3e1f and later · before eb10f25e32576bb3dbbea4457648614537f04211affected · git
- 368704a65be8620df795ccbeb44e025dafbc3e1f and later · before ba5001db9bb23ff7d2ea328c405c287ffb07786faffected · git
- 368704a65be8620df795ccbeb44e025dafbc3e1f and later · before 126a7c227d8543e13903dd5622640c1f0fcc5a16affected · git
- 368704a65be8620df795ccbeb44e025dafbc3e1f and later · before 8ac60ae2a307a50b599bf5d300b448d638f3ba29affected · git
- before 4.7not 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 | from 0 | — |
| Debian:13 | linux | before 6.12.115-2 | 6.12.115-2 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-99122Oct 28, 2026 · vsock/vmci: validate packet source for connected sockets29Monitor
- ← EarlierCVE-2026-99123Oct 28, 2026 · vsock/virtio: validate packet source for connected sockets28Monitor
- Later →CVE-2026-99125Oct 28, 2026 · s390/pai: Handle multiple PMU stop callback invocations0Monitor
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 | 126a7c227d8543e13903dd5622640c1f0fcc5a16 | Vendor (CNA) |
| Linux Linux | 332f2d867f64dd530517e9a58394e3eab454df12 | Vendor (CNA) |
| Linux Linux | 61ce6f9a527932f4482ebe00847490f17d63a0d1 | Vendor (CNA) |
| Linux Linux | 8ac60ae2a307a50b599bf5d300b448d638f3ba29 | Vendor (CNA) |
| Linux Linux | ad1be38823d4b6dbc88648da296ca0c0f8824a55 | Vendor (CNA) |
| Linux Linux | ba5001db9bb23ff7d2ea328c405c287ffb07786f | Vendor (CNA) |
| Linux Linux | eb10f25e32576bb3dbbea4457648614537f04211 | Vendor (CNA) |
| Linux Linux | ff31c34e921d11c7da3d7664ce495106267ca408 | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| debian:linux | 6.12.115-2 · Debian:13 | 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.
- Published
- Fix recordedsame day
- TodayNov 5, 2026+8 d
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-26-1423 · Oct 30, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
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
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/332f2d867f64dd530517e9a58394e3eab454df12
- git.kernel.org/stable/c/61ce6f9a527932f4482ebe00847490f17d63a0d1
- git.kernel.org/stable/c/8ac60ae2a307a50b599bf5d300b448d638f3ba29
- git.kernel.org/stable/c/ad1be38823d4b6dbc88648da296ca0c0f8824a55
- git.kernel.org/stable/c/ba5001db9bb23ff7d2ea328c405c287ffb07786f
- git.kernel.org/stable/c/eb10f25e32576bb3dbbea4457648614537f04211
- git.kernel.org/stable/c/ff31c34e921d11c7da3d7664ce495106267ca408
Vendor advisories and official records. Exploit/PoC links are deliberately left out.