s390/monwriter: Reject buffer reuse with different data length
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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
- CVE published
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
2.6.19
References 8
git.kernel.org
- stable/c/096dff1247037d329c04b3a5be0ecdfb1c5c7ac6
- stable/c/d39cf4a6d721b1ae21eb53bbf3e8cd984253d7ab
- stable/c/759d91378203ea35fa9bca6726dcf0010de081fb
- stable/c/036bc5661060702e798d215e81bb46da530965b3
- stable/c/01f3ce411711c2c919598ea25320a5a48f71edbc
- stable/c/f0745496f7c171271cafd9457df3b914a483ddeb
- stable/c/ae5347f3db1782c6118f6cc0d9fd8b1d43397db3
- stable/c/2995ccec260caa9e85b3301a4aba1e66ed80ad74