CVE-2026-53059: dm log: fix out-of-bounds write due to region_count overflow
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.14% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 12bd5b88e91a02785244ff1d20fb157e96e9cdc8, 3ec74da927b4e171a6fc0e77b1188ba4d019af51, 44ab8875ae4a2842bde2d756bed195d375e0debb; azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 6.6.143.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 12bd5b88e91a02785244ff1d20fb157e96e9cdc8, 3ec74da927b4e171a6fc0e77b1188ba4d019af51, 44ab8875ae4a2842bde2d756bed195d375e0debb; azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 6.6.143.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- ALSA-2026:45114
- ALSA-2026:45115
- ALSA-2026:45116
- ALSA-2026:45192
- openSUSE-SU-2026:22266-1
- RHSA-2026:45114
- RHSA-2026:45115
- RHSA-2026:45116
- RHSA-2026:45192
- RHSA-2026:47248
- RHSA-2026:52649
- RHSA-2026:53989
- RHSA-2026:55445
- RHSA-2026:56574
- RHSA-2026:59662
- RHSA-2026:59663
- RHSA-2026:61692
- RHSA-2026:63189
- RHSA-2026:73645
- RLSA-2026:45114
- Published
- Jun 24, 2026
- Updated
- Nov 6, 2026
- EPSS
- 0.1% · 3th percentile
- CWE
- CWE-787
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.8
- CNA · Linux
- 6.3
- 1.5 point gap
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 2.6.12affected
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 44ab8875ae4a2842bde2d756bed195d375e0debbaffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before defe483e47173768c227532694dc78cb65db5f09affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 3ec74da927b4e171a6fc0e77b1188ba4d019af51affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before d4ac87567f86a55c3c92e9a5144dcd943a9772a1affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 12bd5b88e91a02785244ff1d20fb157e96e9cdc8affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before b455903eed4558982be0811f5b7f44f6bbc4ff57affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 4ec8323b9f0764a14d532b1ae9b87f8a9fecb867affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before c20e36b7631d83e7535877f08af8b0af72c44b1aaffected · git
- before 2.6.12not affected · semver
Affected versions · NVD (8)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel2.6.12.1 and later · before 5.10.258
- linux linux kernel5.11 and later · before 5.15.209
- linux linux kernel5.16 and later · before 6.1.175
- linux linux kernel6.2 and later · before 6.6.141
- linux linux kernel6.7 and later · before 6.12.91
- linux linux kernel6.13 and later · before 6.18.33
- linux linux kernel6.19 and later · before 7.0.10
- linux linux kernel2.6.12
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | kernel | before 6.12.0-211.39.1.el10_2 | 6.12.0-211.39.1.el10_2 |
| AlmaLinux:10 | kernel-64k | before 6.12.0-211.39.1.el10_2 | 6.12.0-211.39.1.el10_2 |
| AlmaLinux:10 | kernel-64k-core | before 6.12.0-211.39.1.el10_2 | 6.12.0-211.39.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug | before 6.12.0-211.39.1.el10_2 | 6.12.0-211.39.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-core | before 6.12.0-211.39.1.el10_2 | 6.12.0-211.39.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel | before 6.12.0-211.39.1.el10_2 | 6.12.0-211.39.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel-matched | before 6.12.0-211.39.1.el10_2 | 6.12.0-211.39.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules | before 6.12.0-211.39.1.el10_2 | 6.12.0-211.39.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-core | before 6.12.0-211.39.1.el10_2 | 6.12.0-211.39.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-extra | before 6.12.0-211.39.1.el10_2 | 6.12.0-211.39.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel | before 6.12.0-211.39.1.el10_2 | 6.12.0-211.39.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel-matched | before 6.12.0-211.39.1.el10_2 | 6.12.0-211.39.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules | before 6.12.0-211.39.1.el10_2 | 6.12.0-211.39.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-core | before 6.12.0-211.39.1.el10_2 | 6.12.0-211.39.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-extra | before 6.12.0-211.39.1.el10_2 | 6.12.0-211.39.1.el10_2 |
| AlmaLinux:10 | kernel-abi-stablelists | before 6.12.0-211.39.1.el10_2 | 6.12.0-211.39.1.el10_2 |
| AlmaLinux:10 | kernel-core | before 6.12.0-211.39.1.el10_2 | 6.12.0-211.39.1.el10_2 |
| AlmaLinux:10 | kernel-cross-headers | before 6.12.0-211.39.1.el10_2 | 6.12.0-211.39.1.el10_2 |
| AlmaLinux:10 | kernel-debug | before 6.12.0-211.39.1.el10_2 | 6.12.0-211.39.1.el10_2 |
| AlmaLinux:10 | kernel-debug-core | before 6.12.0-211.39.1.el10_2 | 6.12.0-211.39.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel | before 6.12.0-211.39.1.el10_2 | 6.12.0-211.39.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel-matched | before 6.12.0-211.39.1.el10_2 | 6.12.0-211.39.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules | before 6.12.0-211.39.1.el10_2 | 6.12.0-211.39.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules-core | before 6.12.0-211.39.1.el10_2 | 6.12.0-211.39.1.el10_2 |
+96
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-53053Jun 24, 2026 · iommu/amd: Fix clone_alias() to use the original device's devid35Monitor
- ← EarlierCVE-2026-53055Jun 24, 2026 · crypto: hisilicon/sec2 - prevent req used-after-free for sec39Monitor
- Later →CVE-2026-53060Jun 24, 2026 · dm cache metadata: fix memory leak on metadata abort retry22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 12bd5b88e91a02785244ff1d20fb157e96e9cdc8 | Vendor (CNA) |
| Linux Linux | 3ec74da927b4e171a6fc0e77b1188ba4d019af51 | Vendor (CNA) |
| Linux Linux | 44ab8875ae4a2842bde2d756bed195d375e0debb | Vendor (CNA) |
| Linux Linux | 4ec8323b9f0764a14d532b1ae9b87f8a9fecb867 | Vendor (CNA) |
| Linux Linux | b455903eed4558982be0811f5b7f44f6bbc4ff57 | Vendor (CNA) |
| Linux Linux | c20e36b7631d83e7535877f08af8b0af72c44b1a | Vendor (CNA) |
| Linux Linux | d4ac87567f86a55c3c92e9a5144dcd943a9772a1 | Vendor (CNA) |
| Linux Linux | defe483e47173768c227532694dc78cb65db5f09 | Vendor (CNA) |
| azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 | 6.6.143.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| almalinux:kernel | 6.12.0-211.39.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k | 6.12.0-211.39.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-core | 6.12.0-211.39.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 6.12.0-211.39.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 6.12.0-211.39.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel | 6.12.0-211.39.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel-matched | 6.12.0-211.39.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 6.12.0-211.39.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 6.12.0-211.39.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 6.12.0-211.39.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-devel | 6.12.0-211.39.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-devel-matched | 6.12.0-211.39.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| debian:linux | 6.1.176-1 · Debian:12 | Package registry (OSV) |
| opensuse:dtb-aarch64 | 6.12.0-160000.41.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-64kb | 6.12.0-160000.41.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-azure | 6.12.0-160000.41.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-default | 6.12.0-160000.41.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-default-base | 6.12.0-160000.41.1.160000.2.31 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-docs | 6.12.0-160000.41.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-kvmsmall | 6.12.0-160000.41.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-obs-build | 6.12.0-160000.41.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
+42
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0440 · Jun 25, 2026(Linux Kernel Güvenlik Bildirimi)
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-787 · Out-of-bounds WriteCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (2)
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (19 more)Show less
- git.kernel.org/stable/c/3ec74da927b4e171a6fc0e77b1188ba4d019af51
- git.kernel.org/stable/c/44ab8875ae4a2842bde2d756bed195d375e0debb
- git.kernel.org/stable/c/4ec8323b9f0764a14d532b1ae9b87f8a9fecb867
- git.kernel.org/stable/c/b455903eed4558982be0811f5b7f44f6bbc4ff57
- git.kernel.org/stable/c/c20e36b7631d83e7535877f08af8b0af72c44b1a
- git.kernel.org/stable/c/d4ac87567f86a55c3c92e9a5144dcd943a9772a1
- git.kernel.org/stable/c/defe483e47173768c227532694dc78cb65db5f09
- access.redhat.com/errata/RHSA-2026:45114
- access.redhat.com/errata/RHSA-2026:45115
- access.redhat.com/errata/RHSA-2026:45116
- access.redhat.com/errata/RHSA-2026:45192
- access.redhat.com/errata/RHSA-2026:47248
- access.redhat.com/errata/RHSA-2026:52649
- access.redhat.com/errata/RHSA-2026:53989
- access.redhat.com/errata/RHSA-2026:55445
- access.redhat.com/errata/RHSA-2026:56574
- access.redhat.com/errata/RHSA-2026:59662
- access.redhat.com/errata/RHSA-2026:59663
- access.redhat.com/errata/RHSA-2026:61692
Vendor advisories and official records. Exploit/PoC links are deliberately left out.