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

CVE-2026-72025

s390/monwriter: Reject buffer reuse with different data length

Description

In the Linux kernel, the following vulnerability has been resolved: s390/monwriter: Reject buffer reuse with different data length When data buffers are reused, e.g. for interval sample records, the first record determines the data length, and the size of the buffer for user copy. Current monwriter code does not check if the data length was changed for subsequent records, which also would never happen for valid user programs. However, a malicious user could change the data length, resulting in out of bounds user copy to the kernel buffer, and memory corruption. By default, the monwriter misc device is created with root-only permissions, so practical impact is typically low. Fix this by checking for changed data length and rejecting such records.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 3 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.22% · top 88% of all CVEs (10 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 31b58088292c7f00f0b81088bfb557285b0b6247 – < 096dff1247037d329c04b3a5be0ecdfb1c5c7ac6
    • affected 31b58088292c7f00f0b81088bfb557285b0b6247 – < d39cf4a6d721b1ae21eb53bbf3e8cd984253d7ab
    • affected 31b58088292c7f00f0b81088bfb557285b0b6247 – < 759d91378203ea35fa9bca6726dcf0010de081fb
    • affected 31b58088292c7f00f0b81088bfb557285b0b6247 – < 036bc5661060702e798d215e81bb46da530965b3
    • affected 31b58088292c7f00f0b81088bfb557285b0b6247 – < 01f3ce411711c2c919598ea25320a5a48f71edbc
    • affected 31b58088292c7f00f0b81088bfb557285b0b6247 – < f0745496f7c171271cafd9457df3b914a483ddeb
    • affected 31b58088292c7f00f0b81088bfb557285b0b6247 – < ae5347f3db1782c6118f6cc0d9fd8b1d43397db3
    • affected 31b58088292c7f00f0b81088bfb557285b0b6247 – < 2995ccec260caa9e85b3301a4aba1e66ed80ad74
  • Linux · Linux

    • affected 2.6.19
    • unaffected < 2.6.19
    • unaffected 5.10.261 – ≤ 5.10.*
    • unaffected 5.15.212 – ≤ 5.15.*
    • unaffected 6.1.178 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.97 – ≤ 6.12.*
    • unaffected 6.18.40 – ≤ 6.18.*
    • unaffected 7.1.5 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

8

Sources

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

Badge for a README or a ticket

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

Record last updated .