CVE-2026-63966

In the Linux kernel, the following vulnerability has been resolved: iio: imu: adis16550: fix stack leak in trigger handler adis16550triggerhandler declares the scan data array on the stack without initializing it. The memcpy at the bottom fills only the first 28 bytes TEMP + 6 channels of...

CVE-2026-63966 iio: imu: adis16550: fix stack leak in trigger handler

In the Linux kernel, the following vulnerability has been resolved: iio: imu: adis16550: fix stack leak in trigger handler adis16550triggerhandler declares the scan data array on the stack without initializing it. The memcpy at the bottom fills only the first 28 bytes TEMP + 6 channels of...

CVE-2026-63966

The CVE-2026-63966 issue affects the Linux kernel IIO imu driver for adis16550. The trigger handler allocates a scan data array on the stack but does not initialize it. A memcpy fills only the first 28 bytes (TEMP + 6 channels of GYRO/ACCEL), while a timestamp is written at offset 32, leaving byt...

CVE-2026-63967

In the Linux kernel, the following vulnerability has been resolved: iio: imu: stlsm6dsx: fix stack leak in tagged FIFO buffer The tagged FIFO path declares iiobuff on the stack with aligned8 but no initializer, but there is a hole in the structure, which will then leak to userspace as...

CVE-2026-63966 iio: imu: adis16550: fix stack leak in trigger handler

In the Linux kernel, the following vulnerability has been resolved: iio: imu: adis16550: fix stack leak in trigger handler adis16550triggerhandler declares the scan data array on the stack without initializing it. The memcpy at the bottom fills only the first 28 bytes TEMP + 6 channels of...

EUVD-2026-45739

In the Linux kernel, the following vulnerability has been resolved: iio: imu: adis16550: fix stack leak in trigger handler adis16550triggerhandler declares the scan data array on the stack without initializing it. The memcpy at the bottom fills only the first 28 bytes TEMP + 6 channels of...

CVE-2026-63967 iio: imu: st_lsm6dsx: fix stack leak in tagged FIFO buffer

In the Linux kernel, the following vulnerability has been resolved: iio: imu: stlsm6dsx: fix stack leak in tagged FIFO buffer The tagged FIFO path declares iiobuff on the stack with aligned8 but no initializer, but there is a hole in the structure, which will then leak to userspace as...

CVE-2026-63965 iio: pressure: bmp280: fix stack leak in bmp580 trigger handler

In the Linux kernel, the following vulnerability has been resolved: iio: pressure: bmp280: fix stack leak in bmp580 trigger handler bmp580triggerhandler declares its scan buffer on the stack without an initializer and then memcpys 3 bytes of 24-bit sensor data into each 4-byte le32 field. The hig...

CVE-2026-63965

In the Linux kernel, the following vulnerability has been resolved: iio: pressure: bmp280: fix stack leak in bmp580 trigger handler bmp580triggerhandler declares its scan buffer on the stack without an initializer and then memcpys 3 bytes of 24-bit sensor data into each 4-byte le32 field. The hig...

CVE-2026-63965

The CVE-2026-63965 entry describes a Linux kernel IIO BMP280/BMP580 trigger handler stack leak: bmp580_trigger_handler() allocated a stack scan buffer and copied 24-bit sensor data into 32-bit fields without proper initialization, leaving high bytes uninitialized and causing two stack bytes per s...

EUVD-2026-45738

In the Linux kernel, the following vulnerability has been resolved: iio: pressure: bmp280: fix stack leak in bmp580 trigger handler bmp580triggerhandler declares its scan buffer on the stack without an initializer and then memcpys 3 bytes of 24-bit sensor data into each 4-byte le32 field. The hig...

CVE-2026-63958 usb: typec: ucsi: validate connector number in ucsi_connector_change()

In the Linux kernel, the following vulnerability has been resolved: usb: typec: ucsi: validate connector number in ucsiconnectorchange The connector number in a UCSI CCI notification is a 7-bit field supplied by the PPM. ucsiconnectorchange uses it to index the ucsi-connector array without checki...

CVE-2026-63949

The CVE-2026-63949 issue is a Linux kernel auxdisplay vulnerability in which linedisp_display() unconditionally reads msg[count - 1] before confirming count > 0, allowing an OOB read on zero-length writes to the message sysfs attribute. The underlying problem occurs in the message_store() call...

EUVD-2026-45722

In the Linux kernel, the following vulnerability has been resolved: auxdisplay: line-display: fix OOB read on zero-length messagestore linedispdisplay unconditionally reads msgcount - 1 before checking whether count is zero, so a write of zero bytes to the message sysfs attribute hits msg-1:...

CVE-2026-63949

In the Linux kernel, the following vulnerability has been resolved: auxdisplay: line-display: fix OOB read on zero-length messagestore linedispdisplay unconditionally reads msgcount - 1 before checking whether count is zero, so a write of zero bytes to the message sysfs attribute hits msg-1:...

CVE-2026-63949 auxdisplay: line-display: fix OOB read on zero-length message_store()

In the Linux kernel, the following vulnerability has been resolved: auxdisplay: line-display: fix OOB read on zero-length messagestore linedispdisplay unconditionally reads msgcount - 1 before checking whether count is zero, so a write of zero bytes to the message sysfs attribute hits msg-1:...

CVE-2026-63949 auxdisplay: line-display: fix OOB read on zero-length message_store()

In the Linux kernel, the following vulnerability has been resolved: auxdisplay: line-display: fix OOB read on zero-length messagestore linedispdisplay unconditionally reads msgcount - 1 before checking whether count is zero, so a write of zero bytes to the message sysfs attribute hits msg-1:...

EUVD-2026-45713

In the Linux kernel, the following vulnerability has been resolved: KVM: SEV: Ignore Port I/O requests of length '0' Explicitly ignore Port I/O requests of length '0' or count '0', so that setting up the software scratch area and other code doesn't have to worry about underflowing the length, and...

CVE-2026-63940

In the Linux kernel, the following vulnerability has been resolved: KVM: SEV: Ignore Port I/O requests of length '0' Explicitly ignore Port I/O requests of length '0' or count '0', so that setting up the software scratch area and other code doesn't have to worry about underflowing the length, and...

CVE-2026-63940

In the Linux kernel KVM SEV issue, the vulnerability concerns ignoring Port I/O requests of length 0. The fix ensures that Port I/O requests with length 0 (or count 0) are explicitly ignored so that the software scratch area setup and related code won’t underflow the length, and to enable a warni...