CVE-2026-72105High· 7.8▾ TwilightIn the Linux kernel, the following vulnerability has been resolved: dm-log: fix a bitset_size overflow on 32bit machines Commit c20e36b7631d ("dm log: fix out-of-bounds write due to region_count overflow") made sure that region_count c…
▾ Twilight zone — High severity, or a signal on a lesser flaw
impact 42.9 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake. The CVSS score shown above comes from the assigning CNA record, not NVD.
Exploit-prediction probability, daily snapshots since Oct 16.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
0.2%
Last analysed / modified upstream
In the Linux kernel, the following vulnerability has been resolved:
dm-log: fix a bitset_size overflow on 32bit machines
Commit c20e36b7631d ("dm log: fix out-of-bounds write due to region_count overflow") made sure that region_count could fit in an unsigned int. But the bitmap memory isn't allocated based on region_count. It uses bitset_size (a size_t variable). The first step of calculating bitset_size is to set it to region_count, rounded up to a multiple of BITS_PER_LONG. If region_size is less than BITS_PER_LONG smaller than UINT_MAX, it will get rounded up to 2^32. On a 32bit architecture, this will make bitset_size wrap around to 0 and fail, despite region_count being valid.
Since bitset_size gets divided by 8, it can hold any valid region_count. It just needs a special case to handle the rollover. If it is 0, the value rolled over, and bitset size should be set to the number of bytes needed to hold 2^32 bits.
Linux >= 44ab8875ae4a2842bde2d756bed195d375e0debb < cdc4ddf9db2cb79f4ab86b1a509b7ac21b0b6cf5Linux >= defe483e47173768c227532694dc78cb65db5f09 < 4b0de5a3ac1fd42acb0dc1f80ac5747e3287d723Linux >= 3ec74da927b4e171a6fc0e77b1188ba4d019af51 < 567602fa72d57169365cbc589e0b8c3be900636dLinux >= d4ac87567f86a55c3c92e9a5144dcd943a9772a1 < d05e0edfecf5260e6dddd28b2f0cce02bfc6ed7aLinux >= 12bd5b88e91a02785244ff1d20fb157e96e9cdc8 < 1c3412b584e1fb6c665ff33ba7259253bc0082cbLinux >= b455903eed4558982be0811f5b7f44f6bbc4ff57 < e0b0163a65758ec3a2361ae1cea407898c27f21eLinux >= c20e36b7631d83e7535877f08af8b0af72c44b1a < 79feb87ab2396d49b9b65e4bb815d33cc71cba47Linux >= c20e36b7631d83e7535877f08af8b0af72c44b1a < 9743132a41f4d9d0e54c5f2adcb821b04796bab1Linux 4ec8323b9f0764a14d532b1ae9b87f8a9fecb867Linux >= 5.10.258 < 5.10.261Linux >= 5.15.209 < 5.15.212Linux >= 6.1.175 < 6.1.178Linux >= 6.6.141 < 6.6.145Linux >= 6.12.91 < 6.12.97Linux >= 6.18.33 < 6.18.40Linux >= 7.0.10 < 7.1Linux 7.1Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2024-38564High· 7.8bpf: Add BPF_PROG_TYPE_CGROUP_SKB attach type enforcement in BPF_LINK_CREATE
CVE-2026-99092Noneriscv: patch: fix handling of bpf-jit execmem addresses
CVE-2026-99089NoneASoC: samsung: i2s: enable op_clk in probe to balance runtime PM
CVE-2026-99093Nonemm: don't schedule deferred kernel page table freeing while booting
CVE-2026-99088Nonenet: openvswitch: validate transport header presence in set_ipv6_addr
CVE-2026-99090Nonedrm/amdgpu: serialize vblank counter reads against GPU reset