Input: ims-pcu - fix heap-buffer-overflow in ims_pcu_process_data()
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 5.10.265, Kernel 5.15.216, Kernel 6.1.183 and 11 more.
In the Linux kernel, the following vulnerability has been resolved: Input: ims-pcu - fix heap-buffer-overflow in ims_pcu_process_data() The `ims_pcu_process_data()` processes incoming URB data byte by byte. However, it fails to check if the `read_pos` index exceeds IMS_PCU_BUF_SIZE. If a malicious USB device sends a packet larger than IMS_PCU_BUF_SIZE, `read_pos` will increment indefinitely. Moreover, since `read_pos` is located immediately after `read_buf`, the attacker can overwrite `read_pos` itself to arbitrarily control the index. This manipulated `read_pos` is subsequently used in `ims_pcu_handle_response()` to copy data into `cmd_buf`, leading to a heap buffer overflow. Specifically, an attacker can overwrite the `cmd_done.wait.head` located at offset 136 relative to `cmd_buf` in the `ims_pcu_handle_response()`. Consequently, when the driver calls `complete(&pcu->cmd_done)`, it triggers a control flow hijack by using the manipulated pointer. Fix this by adding a bounds check for `read_pos` before writing to `read_buf`. If the packet is too long, discard it, log a warning, and reset the parser state. [dtor: factor out resetting packet state, reset checksum as well]
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=3.10 <5.10.265, >=5.11 <5.15.216, >=5.16 <6.1.183, >=6.13 <6.18.42, >=6.19 <7.1, >=6.2 <6.6.148, >=6.7 <6.12.101, >=628329d52474323938a03826941e166bc7c8eff4 <3a801bc75ba1d121d0ed60e7234f93ba5651d87d, >=628329d52474323938a03826941e166bc7c8eff4 <40bbbf2e91fd60715525bf0405c67876af817edf, >=628329d52474323938a03826941e166bc7c8eff4 <875115b82c295277b81b6dfee7debc725f44e854, >=628329d52474323938a03826941e166bc7c8eff4 <992a7173364dcf63e30012af43da3c2f279839f9, >=628329d52474323938a03826941e166bc7c8eff4 <ca9f8c09845fb8c51b6d447f6428eecd1b8b0a49, >=628329d52474323938a03826941e166bc7c8eff4 <d03a740e087de7dcb2a26dc1123377bd3d1d84ca, =3.10, >=628329d52474323938a03826941e166bc7c8eff4 <06cfff93fd40441292567b999091beab11c74504 | 5.10.265, 5.15.216, 6.1.183, 6.18.42, 7.1, 6.6.148, 6.12.101, 3a801bc75ba1d121d0ed60e7234f93ba5651d87d, 40bbbf2e91fd60715525bf0405c67876af817edf, 875115b82c295277b81b6dfee7debc725f44e854, 992a7173364dcf63e30012af43da3c2f279839f9, ca9f8c09845fb8c51b6d447f6428eecd1b8b0a49, d03a740e087de7dcb2a26dc1123377bd3d1d84ca, 06cfff93fd40441292567b999091beab11c74504 |
| linux-kernel: Kernel | >=3.10.0 <5.10.265, >=5.11.0 <5.15.216, >=5.16.0 <6.1.183, >=6.13.0 <6.18.42, >=6.2.0 <6.6.148, >=6.7.0 <6.12.101 | 5.10.265, 5.15.216, 6.1.183, 6.18.42, 6.6.148, 6.12.101 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket