CVE-2026-63975

In the Linux kernel Bluetooth L2CAP stack, CVE-2026-63975 describes a crash when a dcid arrives for an already-assigned destination CID. The fix avoids invalidating a temporary cursor from list_for_each_entry_safe and instead defers closing the channel by scheduling l2cap_chan_timeout with a dela...

CVE-2026-63974

CVE-2026-63974 affects the Linux kernel Bluetooth subsystem. The issue arises in hci_sync where HCI_CMD_DRAIN_WORKQUEUE must be set during device close because hci_dev_close_sync() can be invoked on a reset path, preventing timeouts from being queued while the hdev workqueue drains. The consequen...

EUVD-2026-45745

In the Linux kernel, the following vulnerability has been resolved: net: mana: Skip redundant detach on already-detached port When manaperportqueueresetworkhandler runs after a previous detach succeeded but attach failed, the port is left in a detached state with apc-txqp and apc-rxqs already...

CVE-2026-63971 sctp: fix race between sctp_wait_for_connect and peeloff

In the Linux kernel, the following vulnerability has been resolved: sctp: fix race between sctpwaitforconnect and peeloff sctpwaitforconnect drops and re-acquires the socket lock while waiting for the association to reach ESTABLISHED state. During this window, another thread can peeloff the...

CVE-2026-63970

CVE-2026-63970 — Linux kernel vulnerability in vsock/virtio where zerocopy skb handling could fail due to allocation order: uarg must be bound before filling the skb to ensure correct lifetime handling. The fix ensures the zerocopy uarg is passed into virtio_transport_alloc_skb() and bound prior ...

EUVD-2026-45742

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

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

EUVD-2026-45735

In the Linux kernel, the following vulnerability has been resolved: usb: typec: tcpm: bound altmodedesc per iteration in svdmconsumemodes svdmconsumemodes checks pmdata-altmodes against the array size once before the loop over the count, but forgot to check the bound at every point in the loop. I...

EUVD-2026-45733

In the Linux kernel, the following vulnerability has been resolved: usb: typec: wcove: don't write past struct pdmessage in wcovereadrxbuffer wcovereadrxbuffer copies the PD RX FIFO into the caller's struct pdmessage with for i = 0; i regmap, USBCRXDATA + i, msg + i; which has two problems:...

CVE-2026-63958

The CVE affects the Linux kernel USB Type-C UCSI implementation. In ucsi_connector_change(), the 7-bit connector number from a UCSI CCI notification is used to index ucsi->connector[] without validating it against the number of connectors reported at init time. A buggy/malicious PPM (EC firmwa...

CVE-2026-63954

In the Linux kernel, the following vulnerability has been resolved: hpfs: fix a crash if hpfsmapdnodebitmap fails If hpfsmapdnodebitmap fails, the code would call hpfsbrelse4 on uninitialized quad buffer head, causing a crash...

CVE-2026-63954 hpfs: fix a crash if hpfs_map_dnode_bitmap fails

In the Linux kernel, the following vulnerability has been resolved: hpfs: fix a crash if hpfsmapdnodebitmap fails If hpfsmapdnodebitmap fails, the code would call hpfsbrelse4 on uninitialized quad buffer head, causing a crash...

EUVD-2026-45727

In the Linux kernel, the following vulnerability has been resolved: hpfs: fix a crash if hpfsmapdnodebitmap fails If hpfsmapdnodebitmap fails, the code would call hpfsbrelse4 on uninitialized quad buffer head, causing a crash...

CVE-2026-63955

In the Linux kernel, the following vulnerability has been resolved: mm/vmalloc: do not trigger BUG on BH disabled context getvmareanode currently triggers a BUG if ininterrupt returns true. However, ininterrupt also reports true when BH are disabled. The bridge code can call...

CVE-2026-63954

CVE-2026-63954 pertains to the Linux kernel, specifically the hpfs driver. The issue occurs when hpfs_map_dnode_bitmap fails, which would cause the code to call hpfs_brelse4 on an uninitialized quad buffer head, resulting in a crash. The vulnerability has been resolved by the kernel patch referen...

CVE-2026-63955 mm/vmalloc: do not trigger BUG() on BH disabled context

In the Linux kernel, the following vulnerability has been resolved: mm/vmalloc: do not trigger BUG on BH disabled context getvmareanode currently triggers a BUG if ininterrupt returns true. However, ininterrupt also reports true when BH are disabled. The bridge code can call...

CVE-2026-63951

The CVE-2026-63951 issue concerns the Linux kernel zram subsystem, specifically a use-after-free in zram_writeback_endio. The root cause is a race between the bio completion handler and the writeback task: wake_up is invoked after releasing wb_ctl->done_lock, creating a window where the writeb...

CVE-2026-63952 memfd: deny writeable mappings when implying SEAL_WRITE

In the Linux kernel, the following vulnerability has been resolved: memfd: deny writeable mappings when implying SEALWRITE When SEALEXEC is added, SEALWRITE is implied to make W^X. But the implied seal is set after the check that makes sure the memfd can not have any writable mappings. This means...