CVE-2026-72116 can: bcm: fix stale rx/tx ops after device removal

In the Linux kernel, the following vulnerability has been resolved: can: bcm: fix stale rx/tx ops after device removal RX: an RXSETUP update! for an existing op skipped canrxregister unconditionally, even when a concurrent NETDEVUNREGISTER had already torn down its registration op-rxregdev == NUL...

CVE-2026-72116

The CVE-2026-72116 entry describes a Linux kernel issue in the CAN networking path (bcm) where stale RX/TX operation references could occur after device removal. RX: an RX_SETUP update could skip can_rx_register() if NETDEV_UNREGISTER occurred, leaving rx_ops with ifindex=0 and not re-enabling fr...

CVE-2026-72113

Technical details are not publicly available in the provided documents. Monitor for updates from vendors and security advisories.

CVE-2026-72113 can: bcm: add missing device refcount for CAN filter removal

In the Linux kernel, the following vulnerability has been resolved: can: bcm: add missing device refcount for CAN filter removal sashiko-bot remarked a problem with a concurrent device unregistration in isotp.c which also is present in the bcm.c code. A former fix for raw.c commit c275a176e4b6...

CVE-2026-72108 dm thin metadata: fix metadata snapshot consistency on commit failure

In the Linux kernel, the following vulnerability has been resolved: dm thin metadata: fix metadata snapshot consistency on commit failure reservemetadatasnap and releasemetadatasnap modify the superblock's heldroot directly in the blockmanager's buffer. If the subsequent metadata commit fails, th...

EUVD-2026-59066

In the Linux kernel, the following vulnerability has been resolved: dm thin metadata: fix metadata snapshot consistency on commit failure reservemetadatasnap and releasemetadatasnap modify the superblock's heldroot directly in the blockmanager's buffer. If the subsequent metadata commit fails, th...

CVE-2026-72108 dm thin metadata: fix metadata snapshot consistency on commit failure

In the Linux kernel, the following vulnerability has been resolved: dm thin metadata: fix metadata snapshot consistency on commit failure reservemetadatasnap and releasemetadatasnap modify the superblock's heldroot directly in the blockmanager's buffer. If the subsequent metadata commit fails, th...

CVE-2026-72106 dm-ioctl: fix a possible overflow in list_version_get_info

In the Linux kernel, the following vulnerability has been resolved: dm-ioctl: fix a possible overflow in listversiongetinfo sizeoftt-version is 12 bytes, but the code writes 16 bytes into the output buffer - info-vers-version0, info-vers-version1, info-vers-version2 and info-vers-next. This can...

CVE-2026-72104 dm-pcache: reject option groups without values

In the Linux kernel, the following vulnerability has been resolved: dm-pcache: reject option groups without values The pcache target parses optional arguments as name/value pairs. A table that advertises one optional argument and supplies only a recognized option name, for example "cachemode",...

CVE-2026-72103 dm: avoid leaking the caller's thread keyring via the table device file

In the Linux kernel, the following vulnerability has been resolved: dm: avoid leaking the caller's thread keyring via the table device file The refactoring in commit a28d893eb327 "md: port block device access to file" accidentally causes the caller's thread keyring to be kept alive long beyond th...

CVE-2026-72102 dm_early_create: fix freeing used table on dm_resume failure

In the Linux kernel, the following vulnerability has been resolved: dmearlycreate: fix freeing used table on dmresume failure If dmresume fails, the kernel attempts to free table with dmtabledestroy, but the table was already instantiated with dmswaptable. This commit skips the call to...

CVE-2026-72102 dm_early_create: fix freeing used table on dm_resume failure

In the Linux kernel, the following vulnerability has been resolved: dmearlycreate: fix freeing used table on dmresume failure If dmresume fails, the kernel attempts to free table with dmtabledestroy, but the table was already instantiated with dmswaptable. This commit skips the call to...

CVE-2026-72103 dm: avoid leaking the caller's thread keyring via the table device file

In the Linux kernel, the following vulnerability has been resolved: dm: avoid leaking the caller's thread keyring via the table device file The refactoring in commit a28d893eb327 "md: port block device access to file" accidentally causes the caller's thread keyring to be kept alive long beyond th...

CVE-2026-72102

The CVE-2026-72102 entry concerns the Linux kernel. Affected area: dm_early_create logic related to dynamic device-mapper table handling. Root cause: when dm_resume fails, a table is freed via dm_table_destroy even though it was already instantiated with dm_swap_table, leading to a potential use-...

CVE-2026-72103

CVE-2026-72103 relates to the Linux kernel’s dm-crypt flow. A refactoring bug caused the caller’s thread keyring to be kept alive beyond the caller’s lifetime, making the LUKS volume key linger in memory. As a result, cryptsetup luksSuspend could fail to wipe the key, even though luksOpen passes ...

EUVD-2026-59060

In the Linux kernel, the following vulnerability has been resolved: dmearlycreate: fix freeing used table on dmresume failure If dmresume fails, the kernel attempts to free table with dmtabledestroy, but the table was already instantiated with dmswaptable. This commit skips the call to...

EUVD-2026-59055

In the Linux kernel, the following vulnerability has been resolved: dm-verity: fix a possible NULL pointer dereference Fix a possible NULL pointer dereference dmverityloadpinisbdevtrusted if the device has no table...

CVE-2026-72097 dm-verity: fix a possible NULL pointer dereference

In the Linux kernel, the following vulnerability has been resolved: dm-verity: fix a possible NULL pointer dereference Fix a possible NULL pointer dereference dmverityloadpinisbdevtrusted if the device has no table...

CVE-2026-72079 Input: ims-pcu - fix use-after-free and double-free in disconnect

In the Linux kernel, the following vulnerability has been resolved: Input: ims-pcu - fix use-after-free and double-free in disconnect imspcudisconnect only intended to perform cleanup when the primary control interface is unbound. However, it currently relies on the interface class to distinguish...

CVE-2026-72078 Input: ims-pcu - validate control endpoint type

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