Input: ims-pcu - fix out-of-bounds read in ims_pcu_irq() debug logging
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 628329d52474323938a03826941e166bc7c8eff4 · < 9c964fc9507aeab74376ba9f892cf84ad6950dfe| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
Input: ims-pcu - fix out-of-bounds read in ims_pcu_irq() debug logging
The debug logging in ims_pcu_irq() unconditionally prints data from pcu->urb_in_buf. However, if the interrupt fired for pcu->urb_ctrl, the actual data resides in pcu->urb_ctrl_buf. If urb->actual_length for the control URB exceeds pcu->max_in_size, this leads to an out-of-bounds read.
Fix this by printing from the correct buffer associated with the URB.
From the CVE record · Linux
The Linux kernel’s ims_pcu_irq() debug logging can read beyond a buffer when an interrupt is for the control URB and its actual length exceeds pcu->max_in_size. The input does not establish whether an attacker can trigger this condition or whether it requires authentication or user interaction.
Engineers running Linux kernels with the ims-pcu driver should check whether their kernel is affected; affected versions are not specified.