Skip to content
Noroxi
CVE-2026-72025· NVD / CVE Program· CNA Linux

s390/monwriter: Reject buffer reuse with different data length

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.

—No exploit Fix available
Published
Aug 15, 2026
Updated
Aug 18, 2026
EPSS
0.2% · 11th percentile
CWE
—
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Affected systems

—

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

    • 2.6.19affected
    • 31b58088292c7f00f0b81088bfb557285b0b6247 and later · before 096dff1247037d329c04b3a5be0ecdfb1c5c7ac6affected · git
    • 31b58088292c7f00f0b81088bfb557285b0b6247 and later · before d39cf4a6d721b1ae21eb53bbf3e8cd984253d7abaffected · git
    • 31b58088292c7f00f0b81088bfb557285b0b6247 and later · before 759d91378203ea35fa9bca6726dcf0010de081fbaffected · git
    • 31b58088292c7f00f0b81088bfb557285b0b6247 and later · before 036bc5661060702e798d215e81bb46da530965b3affected · git
    • 31b58088292c7f00f0b81088bfb557285b0b6247 and later · before 01f3ce411711c2c919598ea25320a5a48f71edbcaffected · git
    • 31b58088292c7f00f0b81088bfb557285b0b6247 and later · before f0745496f7c171271cafd9457df3b914a483ddebaffected · git
    • 31b58088292c7f00f0b81088bfb557285b0b6247 and later · before ae5347f3db1782c6118f6cc0d9fd8b1d43397db3affected · git
    • 31b58088292c7f00f0b81088bfb557285b0b6247 and later · before 2995ccec260caa9e85b3301a4aba1e66ed80ad74affected · git
    • before 2.6.19not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.180-16.1.180-1
Debian:13linuxbefore 6.12.100-16.12.100-1
Debian:14linuxbefore 7.1.5-17.1.5-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan
  • CVE-2026-74309vdpa/octeon_ep: fix IRQ-to-ring mapping in interrupt handler
    40Plan
  • CVE-2026-74280crypto: marvell/octeontx - fix DMA cleanup using wrong loop index
    40Plan
  • CVE-2026-74279crypto: cavium/cpt - fix DMA cleanup using wrong loop index
    40Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux01f3ce411711c2c919598ea25320a5a48f71edbcVendor (CNA)
Linux Linux036bc5661060702e798d215e81bb46da530965b3Vendor (CNA)
Linux Linux096dff1247037d329c04b3a5be0ecdfb1c5c7ac6Vendor (CNA)
Linux Linux2995ccec260caa9e85b3301a4aba1e66ed80ad74Vendor (CNA)
Linux Linux759d91378203ea35fa9bca6726dcf0010de081fbVendor (CNA)
Linux Linuxae5347f3db1782c6118f6cc0d9fd8b1d43397db3Vendor (CNA)
Linux Linuxd39cf4a6d721b1ae21eb53bbf3e8cd984253d7abVendor (CNA)
Linux Linuxf0745496f7c171271cafd9457df3b914a483ddebVendor (CNA)
debian:linux6.1.180-1 · Debian:12Package 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.

No dated events beyond publication.

EPSS, last 120 days

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 researchers

Finders, 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).

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.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records