CVE-2026-64046 net: tls: prevent chain-after-chain in plain text SG

In the Linux kernel, the following vulnerability has been resolved: net: tls: prevent chain-after-chain in plain text SG Sashiko points out that if end = 0 start != 0 the current code will create a chain link to content type right after the wrap link: This would create a chain where the wrap link...

CVE-2026-64046

CVE-2026-64046 concerns a Linux kernel TLS issue where a chain-after-chain in the scatterlist could arise when end = 0 (start != 0). The bug creates a chain link to the content type immediately after the wrap link, and sg_next does not recursively resolve consecutive chain links, making the input...

CVE-2026-16221

Impact: fast-uri versions from 2.3.1 through 4.1.0 including the 3.x line up to 3.1.3 and the 2.x line up to 2.4.2 do not treat a literal backslash character U+005C as an authority delimiter. Node's native WHATWG URL parser, used by fetch, undici, and Node's http and https clients, normalizes the...

EUVD-2026-45758

In the Linux kernel, the following vulnerability has been resolved: ethtool: eeprom: add more safeties to EEPROM Netlink fallback The Netlink fallback path for reading module EEPROM fallbacksetparams validates that offset totallen return -EINVAL; This could lead to surprises in both drivers and...

CVE-2026-63970 vsock/virtio: bind uarg before filling zerocopy skb

In the Linux kernel, the following vulnerability has been resolved: vsock/virtio: bind uarg before filling zerocopy skb virtiotransportsendpktinfo allocates or reuses the zerocopy uarg before entering the send loop, but virtiotransportallocskb still fills the skb before it inherits that uarg. Whe...

CVE-2026-63969 ipv6: fix possible infinite loop in rt6_fill_node()

In the Linux kernel, the following vulnerability has been resolved: ipv6: fix possible infinite loop in rt6fillnode Sashiko reported this issue 1. Apply the same fix as commit f8d8ce1b515a "ipv6: fix possible infinite loop in fib6infousesdev". Writers holding tb6lock can listdelrcu&rt-fib6sibling...

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...

EUVD-2026-45740

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-63967

The Linux kernel contains a stack leak vulnerability within the iio: imu: st_lsm6dsx driver. The issue occurs because the tagged FIFO path declares iio_buff on the stack with __aligned(8) but lacks an initializer. This results in uninitialized space between the sample size and the timestamp being...

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

The Linux kernel contains a stack memory leak in the adis16550_trigger_handler() function within the drivers/iio/imu/adis16550.c module. The vulnerability occurs because the scan data array is declared on the stack without initialization; subsequently, memcpy() only fills the first 28 bytes, leav...

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-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-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-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 Linux kernel contains a stack leak vulnerability in the bmp580 trigger handler (bmp580_trigger_handler()) located within the drivers/iio/pressure/bmp280-core.c file. The root cause is that the scan buffer is declared on the stack without an initializer, and a subsequent memcpy() operation fai...

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...