s390/monwriter: Reject buffer reuse with different data length
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 31b58088292c7f00f0b81088bfb557285b0b6247 · < f0745496f7c171271cafd9457df3b914a483ddeb| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel's s390/monwriter component fails to reject reused buffers when a later record changes the data length. A local user with access to the monwriter device can trigger an out-of-bounds copy into a kernel buffer and corrupt memory. The device is root-only by default.
Administrators running the Linux kernel with the s390/monwriter device should check their systems; affected versions were not specified.