152 matches found
CLSA-2026-1768895798 kernel: Fix of 4 CVEs
fs/proc: fix uaf in procreaddirde CVE-2025-40271 - fs: fix UAF/GPF bug in nilfsmdtdestroy CVE-2022-2978 - Bluetooth: L2CAP: fix "bad unlock balance" in l2capdisconnectrsp CVE-2023-53297 - net: sched: sfb: fix null pointer access issue when sfbinit fails CVE-2022-50356 - ALSA: usb-audio: Fix size...
CLSA-2025-1742322442 kernel: Fix of 176 CVEs
HID: core: zero-initialize the report buffer CVE-2024-50302 - Revert "drm/amdgpu: add missing size check in amdgpudebugfsgprwaveread" - drm/amd/amdgpu: Fix GPR read from debugfs v2 CVE-2024-50282 - USB: serial: ioedgeport: fix use after free in debug printk CVE-2024-50267 - wifi: iwlegacy: Clear...
CVE-2026-96582
A HID report descriptor is a sequence of items, each declaring in its header how many data bytes follow. The USBX host walks that sequence by advancing over each header and parsing the data behind it. The walk checked that an item fitted in the descriptor only after it had advanced past the heade...
CVE-2026-96582 Out-of-bounds Read via Check-after-use in the USBX HID Report Descriptor Parser
A HID report descriptor is a sequence of items, each declaring in its header how many data bytes follow. The USBX host walks that sequence by advancing over each header and parsing the data behind it. The walk checked that an item fitted in the descriptor only after it had advanced past the heade...
CVE-2026-96582
A HID report descriptor is a sequence of items, each declaring in its header how many data bytes follow. The USBX host walks that sequence by advancing over each header and parsing the data behind it. The walk checked that an item fitted in the descriptor only after it had advanced past the heade...
EUVD-2026-105000
A HID report descriptor is a sequence of items, each declaring in its header how many data bytes follow. The USBX host walks that sequence by advancing over each header and parsing the data behind it. The walk checked that an item fitted in the descriptor only after it had advanced past the heade...
CVE-2026-96582 Out-of-bounds Read via Check-after-use in the USBX HID Report Descriptor Parser
A HID report descriptor is a sequence of items, each declaring in its header how many data bytes follow. The USBX host walks that sequence by advancing over each header and parsing the data behind it. The walk checked that an item fitted in the descriptor only after it had advanced past the heade...
CVE-2026-96582 Out-of-bounds Read via Check-after-use in the USBX HID Report Descriptor Parser
A HID report descriptor is a sequence of items, each declaring in its header how many data bytes follow. The USBX host walks that sequence by advancing over each header and parsing the data behind it. The walk checked that an item fitted in the descriptor only after it had advanced past the heade...
CVE-2026-96582
The USBX HID Report Descriptor Parser is vulnerable to a heap out-of-bounds read during ordinary enumeration. The root cause is a check-after-use flaw where the host validates that an item fits in the descriptor only after advancing past the header and parsing the payload. Because the analysis fa...
PT-2026-118372
A HID report descriptor is a sequence of items, each declaring in its header how many data bytes follow. The USBX host walks that sequence by advancing over each header and parsing the data behind it. The walk checked that an item fitted in the descriptor only after it had advanced past the heade...
Eclipse ThreadX - USBX buffer error vulnerability
Eclipse ThreadX – Versions 6.5.1.202602 and earlier contain a buffer error vulnerability. This vulnerability arises because the USBX host fails to validate the declared size based on the actual bytes received when parsing HID report descriptors. Instead, it only checks whether the descriptor fits...
SUSE CVE-2026-98206
In the Linux kernel, the following vulnerability has been resolved: Input: cyttsp5 - clamp the HID report size before memcpy The size field comes from the device and is used as the memcpy length into responsebuf, which is CYMAXINPUT bytes...
DEBIAN-CVE-2026-98206
In the Linux kernel, the following vulnerability has been resolved: Input: cyttsp5 - clamp the HID report size before memcpy The size field comes from the device and is used as the memcpy length into responsebuf, which is CYMAXINPUT bytes...
AZL-106341 CVE-2026-98206 affecting package kernel for versions less than 6.6.158.1-1
In the Linux kernel, the following vulnerability has been resolved: Input: cyttsp5 - clamp the HID report size before memcpy The size field comes from the device and is used as the memcpy length into responsebuf, which is CYMAXINPUT bytes...
CVE-2026-98206
In the Linux kernel, the following vulnerability has been resolved: Input: cyttsp5 - clamp the HID report size before memcpy The size field comes from the device and is used as the memcpy length into responsebuf, which is CYMAXINPUT bytes...
UBUNTU-CVE-2026-98206
In the Linux kernel, the following vulnerability has been resolved: Input: cyttsp5 - clamp the HID report size before memcpy The size field comes from the device and is used as the memcpy length into responsebuf, which is CYMAXINPUT bytes...
CVE-2026-98206
In the Linux kernel, the following vulnerability has been resolved: Input: cyttsp5 - clamp the HID report size before memcpy The size field comes from the device and is used as the memcpy length into responsebuf, which is CYMAXINPUT bytes...
CVE-2026-98206
The Linux kernel is affected by a vulnerability where the HID report size provided by a device is used as the length for a memcpy() operation into response_buf . Because the size field originates from the device without prior validation, it could lead to a buffer overflow if it exceeds CY_MAX_INP...
EUVD-2026-93134
In the Linux kernel, the following vulnerability has been resolved: Input: cyttsp5 - clamp the HID report size before memcpy The size field comes from the device and is used as the memcpy length into responsebuf, which is CYMAXINPUT bytes...
CVE-2026-98206 Input: cyttsp5 - clamp the HID report size before memcpy
In the Linux kernel, the following vulnerability has been resolved: Input: cyttsp5 - clamp the HID report size before memcpy The size field comes from the device and is used as the memcpy length into responsebuf, which is CYMAXINPUT bytes...