Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-99124

s390/pci: Fix leak of uninitialized kernel data in SCLP report

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.

Timeline

  1. ID reserved

    By Linux

  2. · 33 days later

    Published

  3. · 2 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.18% · top 93% of all CVEs (12 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 368704a65be8620df795ccbeb44e025dafbc3e1f – < ad1be38823d4b6dbc88648da296ca0c0f8824a55
    • affected 368704a65be8620df795ccbeb44e025dafbc3e1f – < 61ce6f9a527932f4482ebe00847490f17d63a0d1
    • affected 368704a65be8620df795ccbeb44e025dafbc3e1f – < 332f2d867f64dd530517e9a58394e3eab454df12
    • affected 368704a65be8620df795ccbeb44e025dafbc3e1f – < ff31c34e921d11c7da3d7664ce495106267ca408
    • affected 368704a65be8620df795ccbeb44e025dafbc3e1f – < eb10f25e32576bb3dbbea4457648614537f04211
    • affected 368704a65be8620df795ccbeb44e025dafbc3e1f – < ba5001db9bb23ff7d2ea328c405c287ffb07786f
    • affected 368704a65be8620df795ccbeb44e025dafbc3e1f – < 126a7c227d8543e13903dd5622640c1f0fcc5a16
    • affected 368704a65be8620df795ccbeb44e025dafbc3e1f – < 8ac60ae2a307a50b599bf5d300b448d638f3ba29
  • Linux · Linux

    • affected 4.7
    • unaffected < 4.7
    • unaffected 5.10.273 – ≤ 5.10.*
    • unaffected 5.15.224 – ≤ 5.15.*
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.161 – ≤ 6.6.*
    • unaffected 6.12.115 – ≤ 6.12.*
    • unaffected 6.18.59 – ≤ 6.18.*
    • unaffected 7.2.13 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-99124 badge
[![CVE-2026-99124](https://cveledger.app/badge/CVE-2026-99124.svg)](https://cveledger.app/cve/CVE-2026-99124)

Record last updated .