CVE-2026-53059·Kernel vulnerability
In the Linux kernel, the following vulnerability has been resolved: dm log: fix out-of-bounds write due to region_count overflow The local variable region_count in create_log_context() is declared as unsigned int (32-bit), but dm_sector_div_up() returns sector_t (64-bit). When a device-mapper target has a sufficiently large ti->len with a small region_size, the division result can exceed UINT_MAX. The truncated value is then used to calculate bitset_size, causing clean_bits, sync_bits, and recovering_bits to be allocated far smaller than needed for the actual number of regions. Subsequent log operations (log_set_bit, log_clear_bit, log_test_bit) use region indices derived from the full untruncated region space, causing out-of-bounds writes to kernel heap memory allocated by vmalloc. This can be reproduced by creating a mirror target whose region_count overflows 32 bits: dmsetup create bigzero --table '0 8589934594 zero' dmsetup create mymirror --table '0 8589934594 mirror \ core 2 2 nosync 2 /dev/mapper/bigzero 0 \ /dev/mapper/bigzero 0' The status output confirms the truncation (sync_count=1 instead of 4294967297, because 0x100000001 was truncated to 1): $ dmsetup status mymirror 0 8589934594 mirror 2 254:1 254:1 1/4294967297 ... This leads to a kernel crash in core_in_sync: BUG: scheduling while atomic: (udev-worker)/9150/0x00000000 RIP: 0010:core_in_sync+0x14/0x30 [dm_log] CR2: 0000000000000008 Fixing recursive fault but reboot is needed! Fix by widening the local region_count to sector_t and adding an explicit overflow check before the value is assigned to lc->region_count.
- Severity
- high
- Software
- Kernel
- Fixed in
- 7.0.10
- Published
How likely is exploitation
FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 0.14% — higher than 3% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.
Read the two together. CVE-2026-53059 scores 7.8 on CVSS, so a successful attack would be serious — but at 0.14%, almost nobody is currently attempting it. That is a different situation from a flaw under mass exploitation, and it is usually the difference between patching on your next maintenance window and patching tonight.
Affected versions
From: 6.19
Until: 7.0.10
Fixed in: 7.0.10
How to fix this CVE
Update your Linux kernel to version 7.0.10 or later to fix a critical integer overflow vulnerability in the device-mapper logging subsystem. This vulnerability can cause kernel heap corruption when device-mapper targets are configured with large storage capacities and small region sizes. Apply the security patch immediately to all affected systems, particularly those running mirrors or other dm-log dependent configurations.
sudo dnf update kernel kernel-headers kernel-develDefensia detects this vulnerability
How to check if you are affected
- Step 1: Check your kernel version with `uname -r` and compare against the vulnerable range (6.19 to 7.0.10)
- Step 2: Verify if dm-log is active by running `lsmod | grep dm_log` and check for active device-mapper mirrors using `dmsetup table`
- Step 3: Search kernel logs for scheduler warnings and BUG messages related to dm_log using `sudo dmesg | grep -i 'dm_log\|core_in_sync\|scheduling while atomic'`
- Step 4: After patching, confirm the new kernel version with `uname -r` and verify dm-log functionality with `sudo dmsetup status`
FAQ
What is CVE-2026-53059?
This vulnerability involves a 32-bit integer overflow in the Linux kernel's device-mapper logging layer that occurs when calculating the region count for large storage devices. The overflow causes undersized memory allocation, leading to heap buffer overflows when device-mapper operations attempt to access regions beyond the truncated buffer boundaries.
Is CVE-2026-53059 being actively exploited?
No, CVE-2026-53059 is not currently listed in CISA's Known Exploited Vulnerabilities catalog, and no public exploits are available. However, local attackers with device-mapper configuration privileges could potentially trigger the vulnerability through crafted mirror target configurations.
What versions of Kernel are affected by CVE-2026-53059?
Kernel versions 6.19 through 7.0.10 (inclusive) are affected by this vulnerability. The fix was introduced in kernel 7.0.10 and backported to stable branches.
How do I check if my server is vulnerable to CVE-2026-53059?
Run `uname -r` to check your kernel version. If the version is between 6.19 and 7.0.9, your system is vulnerable. Additionally, check if dm-log is loaded with `lsmod | grep dm_log` to determine exposure.
Does Defensia detect CVE-2026-53059?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Kernel is installed on a monitored server, CVE-2026-53059 will appear in your dashboard with remediation steps.
Related Kernel CVEs
References
- https://git.kernel.org/stable/c/12bd5b88e91a02785244ff1d20fb157e96e9cdc8
- https://git.kernel.org/stable/c/3ec74da927b4e171a6fc0e77b1188ba4d019af51
- https://git.kernel.org/stable/c/44ab8875ae4a2842bde2d756bed195d375e0debb
- https://git.kernel.org/stable/c/4ec8323b9f0764a14d532b1ae9b87f8a9fecb867
- https://git.kernel.org/stable/c/b455903eed4558982be0811f5b7f44f6bbc4ff57
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-53059. Free for 1 server.
Get started free