24 matches found
CVE-2026-80596
A flaw was found in the Linux kernel's ims-pcu driver. This vulnerability occurs because sysfs attributes, intended only for the control interface, are improperly exposed on all interfaces. A local user could exploit this by accessing these attributes on data interfaces, leading to unexpected...
CVE-2026-80595
A flaw was found in the Linux kernel. The ims-pcu driver processes response data from device buffers without verifying the actual length of the data sent by the device. This oversight can lead to out-of-bounds reads, potentially allowing an attacker to access sensitive information or cause system...
CVE-2026-80594
A flaw was found in the Linux kernel's ims-pcu driver. This vulnerability allows a malicious device to trigger an infinite loop by providing a specially crafted descriptor with a zero-length field during the parsing of CDC union descriptors. This can lead to a Denial of Service DoS condition,...
SUSE CVE-2026-80594
In the Linux kernel, the following vulnerability has been resolved: Input: ims-pcu - fix potential infinite loop in CDC union descriptor parsing The driver parses CDC union descriptors in imspcugetcdcuniondesc by iterating through the extra descriptor data. However, it does not verify that the...
SUSE CVE-2026-80596
In the Linux kernel, the following vulnerability has been resolved: Input: ims-pcu - only expose sysfs attributes on control interface When the driver was converted to use the driver core to instantiate device attributes via .devgroups in the usbdriver structure, the attributes started appearing ...
CVE-2026-80595
In the Linux kernel, the following vulnerability has been resolved: Input: ims-pcu - add response length checks The driver processes response data from device buffers without verifying that the device actually sent enough data. This can lead to out-of-bounds reads or processing stale data. Add...
UBUNTU-CVE-2026-80594
In the Linux kernel, the following vulnerability has been resolved: Input: ims-pcu - fix potential infinite loop in CDC union descriptor parsing The driver parses CDC union descriptors in imspcugetcdcuniondesc by iterating through the extra descriptor data. However, it does not verify that the...
EUVD-2026-67471
In the Linux kernel, the following vulnerability has been resolved: Input: ims-pcu - add response length checks The driver processes response data from device buffers without verifying that the device actually sent enough data. This can lead to out-of-bounds reads or processing stale data. Add...
CVE-2026-80596
CVE-2026-80596 affects the Linux kernel ims-pcu USB input driver. When the driver was converted to use the driver core to instantiate device attributes (via .dev_groups in the usb_driver structure), sysfs attributes were incorrectly exposed on all USB interfaces , including the secondary data int...
EUVD-2026-67470
In the Linux kernel, the following vulnerability has been resolved: Input: ims-pcu - fix potential infinite loop in CDC union descriptor parsing The driver parses CDC union descriptors in imspcugetcdcuniondesc by iterating through the extra descriptor data. However, it does not verify that the...
CVE-2026-72079
A flaw was found in the Linux kernel's ims-pcu driver. A malicious device can exploit an issue in the imspcudisconnect function, which incorrectly distinguishes between control and data interfaces. By presenting a data interface with the same class as the control interface, a malicious device can...
CVE-2026-72077
A flaw was found in the Linux kernel's ims-pcu input driver. This vulnerability occurs when the firmware object is not properly released if validation fails during an asynchronous update. This oversight can lead to a firmware leak, potentially exposing sensitive information or system resources. T...
CVE-2026-72076
A flaw was found in the Linux kernel's ims-pcu driver. The debug logging in the imspcuirq function can attempt to read data beyond the allocated buffer when processing certain Universal Serial Bus USB control requests. This out-of-bounds read occurs if the length of the control request exceeds th...
CVE-2026-72074
A flaw was found in the Linux kernel's ims-pcu driver. A type confusion vulnerability exists in the CDC union descriptor parsing, where the driver trusts the bMasterInterface0 value without proper verification. This could allow a local attacker, or a malicious USB device, to overwrite the private...
CVE-2026-72076
In the Linux kernel, the following vulnerability has been resolved: Input: ims-pcu - fix out-of-bounds read in imspcuirq debug logging The debug logging in imspcuirq unconditionally prints data from pcu-urbinbuf. However, if the interrupt fired for pcu-urbctrl, the actual data resides in...
CVE-2026-72078
In the Linux kernel, the following vulnerability has been resolved: Input: ims-pcu - validate control endpoint type The driver currently assumes that the first endpoint of the control interface is an interrupt IN endpoint without verifying it. A malicious device could provide a different endpoint...
UBUNTU-CVE-2026-72076
In the Linux kernel, the following vulnerability has been resolved: Input: ims-pcu - fix out-of-bounds read in imspcuirq debug logging The debug logging in imspcuirq unconditionally prints data from pcu-urbinbuf. However, if the interrupt fired for pcu-urbctrl, the actual data resides in...
CVE-2026-72079
The CVE-2026-72079 issue affects the Linux kernel’s ims_pcu_disconnect path, where use-after-free/double-free could occur if a data interface is misidentified as the control interface due to relying on interface class for cleanup. The fix switches validation to ensure the disconnected interface i...
EUVD-2026-59034
In the Linux kernel, the following vulnerability has been resolved: Input: ims-pcu - fix out-of-bounds read in imspcuirq debug logging The debug logging in imspcuirq unconditionally prints data from pcu-urbinbuf. However, if the interrupt fired for pcu-urbctrl, the actual data resides in...
PT-2026-72267
In the Linux kernel, the following vulnerability has been resolved: Input: ims-pcu - validate control endpoint type The driver currently assumes that the first endpoint of the control interface is an interrupt IN endpoint without verifying it. A malicious device could provide a different endpoint...