Answer in brief
CVE-2026-72025 records a Unknown severity vulnerability in s390/monwriter: Reject buffer reuse with different data length. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-72025 records a Unknown severity vulnerability in s390/monwriter: Reject buffer reuse with different data length. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <096dff1247037d329c04b3a5be0ecdfb1c5c7ac6 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <d39cf4a6d721b1ae21eb53bbf3e8cd984253d7ab || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <759d91378203ea35fa9bca6726dcf0010de081fb || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <036bc5661060702e798d215e81bb46da530965b3 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <01f3ce411711c2c919598ea25320a5a48f71edbc || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f0745496f7c171271cafd9457df3b914a483ddeb || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ae5347f3db1782c6118f6cc0d9fd8b1d43397db3 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <2995ccec260caa9e85b3301a4aba1e66ed80ad74 || >=0 <5.10.261 || >=0 <5.15.212 || >=0 <6.1.178 || >=0 <6.6.145 || >=0 <6.12.97 || >=0 <6.18.40 || >=0 <7.1.5 | 096dff1247037d329c04b3a5be0ecdfb1c5c7ac6, d39cf4a6d721b1ae21eb53bbf3e8cd984253d7ab, 759d91378203ea35fa9bca6726dcf0010de081fb, 036bc5661060702e798d215e81bb46da530965b3, 01f3ce411711c2c919598ea25320a5a48f71edbc, f0745496f7c171271cafd9457df3b914a483ddeb, ae5347f3db1782c6118f6cc0d9fd8b1d43397db3, 2995ccec260caa9e85b3301a4aba1e66ed80ad74, 5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.97, 6.18.40, 7.1.5 |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <096dff1247037d329c04b3a5be0ecdfb1c5c7ac6 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <d39cf4a6d721b1ae21eb53bbf3e8cd984253d7ab || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <759d91378203ea35fa9bca6726dcf0010de081fb || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <036bc5661060702e798d215e81bb46da530965b3 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <01f3ce411711c2c919598ea25320a5a48f71edbc || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f0745496f7c171271cafd9457df3b914a483ddeb || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ae5347f3db1782c6118f6cc0d9fd8b1d43397db3 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <2995ccec260caa9e85b3301a4aba1e66ed80ad74 || >=0 <5.10.261 || >=0 <5.15.212 || >=0 <6.1.178 || >=0 <6.6.145 || >=0 <6.12.97 || >=0 <6.18.40 || >=0 <7.1.5 | 096dff1247037d329c04b3a5be0ecdfb1c5c7ac6, d39cf4a6d721b1ae21eb53bbf3e8cd984253d7ab, 759d91378203ea35fa9bca6726dcf0010de081fb, 036bc5661060702e798d215e81bb46da530965b3, 01f3ce411711c2c919598ea25320a5a48f71edbc, f0745496f7c171271cafd9457df3b914a483ddeb, ae5347f3db1782c6118f6cc0d9fd8b1d43397db3, 2995ccec260caa9e85b3301a4aba1e66ed80ad74, 5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.97, 6.18.40, 7.1.5 |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.