CVE-2026-72111

CVE-2026-72111 affects the Linux kernel BPF verifier. The issue occurs when processing a context load of an LSM hook return value: __mark_reg_s32_range() narrows the destination register by intersecting with stale bounds instead of replacing them, potentially creating a verifier/runtime mismatch ...

CVE-2026-72111 bpf: Reset register bounds before narrowing retval range in check_mem_access()

In the Linux kernel, the following vulnerability has been resolved: bpf: Reset register bounds before narrowing retval range in checkmemaccess When the BPF verifier processes a context load of an LSM hook return value, it calls markregs32range to narrow the register to the hook's valid range...

EUVD-2026-59067

In the Linux kernel, the following vulnerability has been resolved: net: sparx5: unregister blocking notifier on init failure sparx5registernotifierblocks registers the switchdev blocking notifier before allocating the ordered workqueue. If the workqueue allocation fails, the error path unregiste...

CVE-2026-72109 net: sparx5: unregister blocking notifier on init failure

In the Linux kernel, the following vulnerability has been resolved: net: sparx5: unregister blocking notifier on init failure sparx5registernotifierblocks registers the switchdev blocking notifier before allocating the ordered workqueue. If the workqueue allocation fails, the error path unregiste...

CVE-2026-72110

In the Linux kernel, the following vulnerability has been resolved: bpf,fork: wipe -bpfstorage before bailouts that access it Currently, copyprocess can bail out to freetask before p-bpfstorage has been initialized, with this call graph shown here for the !CONFIGMEMCG case: copyprocess...

CVE-2026-72108

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

Summary (CVE-2026-72107) In the Linux kernel, the vulnerability is in the dm-era code path where writes are tracked in target-relative blocks. The root cause is that era_map() calculates the writeset block before applying the target offset, allowing a non-zero start sector to pass an absolute map...

CVE-2026-72107 dm era: fix out-of-bounds memory access for non-zero start sector

In the Linux kernel, the following vulnerability has been resolved: dm era: fix out-of-bounds memory access for non-zero start sector dm-era tracks writes in target-relative blocks, but eramap calculates the writeset block before applying the target offset. Tables with a non-zero start sector can...

CVE-2026-72107 dm era: fix out-of-bounds memory access for non-zero start sector

In the Linux kernel, the following vulnerability has been resolved: dm era: fix out-of-bounds memory access for non-zero start sector dm-era tracks writes in target-relative blocks, but eramap calculates the writeset block before applying the target offset. Tables with a non-zero start sector can...

CVE-2026-72107

In the Linux kernel, the following vulnerability has been resolved: dm era: fix out-of-bounds memory access for non-zero start sector dm-era tracks writes in target-relative blocks, but eramap calculates the writeset block before applying the target offset. Tables with a non-zero start sector can...

CVE-2026-72105

The CVE-2026-72105 entry concerns the Linux kernel dm-log component, where a bitset_size overflow on 32‑bit architectures could occur during region_count handling. The root cause is a miscalculation of bitset_size (size_t) when computing the bitmap memory based on region_count, which could wrap t...

CVE-2026-72105 dm-log: fix a bitset_size overflow on 32bit machines

In the Linux kernel, the following vulnerability has been resolved: dm-log: fix a bitsetsize overflow on 32bit machines Commit c20e36b7631d "dm log: fix out-of-bounds write due to regioncount overflow" made sure that regioncount could fit in an unsigned int. But the bitmap memory isn't allocated...

CVE-2026-72105

In the Linux kernel, the following vulnerability has been resolved: dm-log: fix a bitsetsize overflow on 32bit machines Commit c20e36b7631d "dm log: fix out-of-bounds write due to regioncount overflow" made sure that regioncount could fit in an unsigned int. But the bitmap memory isn't allocated...

CVE-2026-72104

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

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

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

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

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