VulnerabilityPublished 28 Oct 2026

CVE-2026-99124: Linux kernel · s390/pci: Fix leak of uninitialized kernel data in SCLP report

Affects Linux kernelSource CVE Database V5

Not known to be exploited · fixed in ba5001db9bb23ff7d2ea328c405c287ffb07786f : update Linux kernel when convenient.

Data as of 28 Oct 2026, 10:58 UTC

Severity

Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

Patch: Available – fixed in ba5001db9bb23ff7d2ea328c405c287ffb07786f, 126a7c227d8543e13903dd5622640c1f0fcc5a16, 8ac60ae2a307a50b599bf5d300b448d638f3ba29

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Linux kernel to ba5001db9bb23ff7d2ea328c405c287ffb07786f, 126a7c227d8543e13903dd5622640c1f0fcc5a16 or 8ac60ae2a307a50b599bf5d300b448d638f3ba29.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 368704a65be8620df795ccbeb44e025dafbc3e1f, < ba5001db9bb23ff7d2ea328c405c287ffb07786f	Fixed in ba5001db9bb23ff7d2ea328c405c287ffb07786f
LinuxLinux	Affected ≥ 368704a65be8620df795ccbeb44e025dafbc3e1f, < 126a7c227d8543e13903dd5622640c1f0fcc5a16	Fixed in 126a7c227d8543e13903dd5622640c1f0fcc5a16
LinuxLinux	Affected ≥ 368704a65be8620df795ccbeb44e025dafbc3e1f, < 8ac60ae2a307a50b599bf5d300b448d638f3ba29	Fixed in 8ac60ae2a307a50b599bf5d300b448d638f3ba29
LinuxLinux	Affected =4.7	Fixed in–

Description

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.

References

Community reviews

Loading reviews…