Input: ims-pcu - fix use-after-free and double-free in disconnect
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 628329d52474323938a03826941e166bc7c8eff4 · < 6aacc18004b1a915ccb8a829d30279a37988066e| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
Input: ims-pcu - fix use-after-free and double-free in disconnect
ims_pcu_disconnect() only intended to perform cleanup when the primary (control) interface is unbound. However, it currently relies on the interface class to distinguish between control and data interfaces. A malicious device could present a data interface with the same class as the control interface, leading to premature cleanup and potential use-after-free or double-free.
Switch to verifying that the interface being disconnected is indeed the control interface.
From the CVE record · Linux
The Linux kernel’s ims-pcu disconnect handler can mistake a data interface for the control interface and clean up too early. An attacker who can connect a malicious device presenting a data interface with the control interface’s class could trigger a use-after-free or double-free when that interface disconnects.
Teams running Linux kernels with the ims-pcu driver should check their kernel vendor’s advisory; affected versions were not specified.