Описание
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.
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.
Ссылки
- https://nvd.nist.gov/vuln/detail/CVE-2026-72079
- https://git.kernel.org/stable/c/293388e42e5c0865204de6f36bfb8662156fce3b
- https://git.kernel.org/stable/c/315f269ea04bc1477ab9bf351e939623d12a1621
- https://git.kernel.org/stable/c/462a999917755a3bf77448dfd64307963cf0a9f0
- https://git.kernel.org/stable/c/6a6c373e6a82eddc522342c8a8db7072c65f2b56
- https://git.kernel.org/stable/c/6aacc18004b1a915ccb8a829d30279a37988066e
- https://git.kernel.org/stable/c/921abbb33887052e46b1b77299f87a3c741dc580
- https://git.kernel.org/stable/c/a4b3f4d42fbf58f06f0d49e37a9d0d9392eca338
- https://git.kernel.org/stable/c/bf0b58ba489d0bdaa18c7dd8beeaeb954dd7dbb7
EPSS
CVE ID
Связанные уязвимости
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.
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.
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.
In the Linux kernel, the following vulnerability has been resolved: I ...
EPSS