CVE-2026-99124 json
s390/pci: Fix leak of uninitialized kernel data in SCLP report
published 14d ago modified 12d ago also EUVD-2026-111876
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 7%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 7.3
- linux Debian 13 6.12.115-2
- linux Debian 14 7.2.13-1
debian advisories DEBIAN-CVE-2026-99124
- kernel Azure Linux 3.0 6.6.161.1-1
azure linux advisories AZL-111230
Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT
- git.kernel.org/stable/c/ad1be38823d4b6dbc88648da296ca0c0f8824a55 commit
- git.kernel.org/stable/c/61ce6f9a527932f4482ebe00847490f17d63a0d1 commit
- git.kernel.org/stable/c/332f2d867f64dd530517e9a58394e3eab454df12 commit
- git.kernel.org/stable/c/ff31c34e921d11c7da3d7664ce495106267ca408 commit
- git.kernel.org/stable/c/eb10f25e32576bb3dbbea4457648614537f04211 commit
- git.kernel.org/stable/c/ba5001db9bb23ff7d2ea328c405c287ffb07786f commit
- git.kernel.org/stable/c/126a7c227d8543e13903dd5622640c1f0fcc5a16 commit
- git.kernel.org/stable/c/8ac60ae2a307a50b599bf5d300b448d638f3ba29 commit
Is CVE-2026-99124 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-99124 updated cvss 5.1
kernel: kernel: Information disclosure via out-of-bounds read in s390 PCI error reporting
-
Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernel Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9 Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9affected: no fix available “Fix deferred”
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.18% chance of exploitation in the next 30 days, higher than 7% of all scored CVEs (FIRST EPSS, 2026-11-11).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/ad1be38823d4b6dbc88648da296ca0c0f8824a55
- git.kernel.org /stable/c/61ce6f9a527932f4482ebe00847490f17d63a0d1
- git.kernel.org /stable/c/332f2d867f64dd530517e9a58394e3eab454df12
- git.kernel.org /stable/c/ff31c34e921d11c7da3d7664ce495106267ca408
- git.kernel.org /stable/c/eb10f25e32576bb3dbbea4457648614537f04211
- git.kernel.org /stable/c/ba5001db9bb23ff7d2ea328c405c287ffb07786f
- git.kernel.org /stable/c/126a7c227d8543e13903dd5622640c1f0fcc5a16
- git.kernel.org /stable/c/8ac60ae2a307a50b599bf5d300b448d638f3ba29
Sources
- CVE List CVE-2026-99124
- NVD CVE-2026-99124
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.