HighCVE-2026-53059

    Linux Kernel: Out-of-Bounds Write (CVE-2026-53059)

    Published Last modified Sources: SUSE, Debian LTS, BSI, Ubuntu, Red Hat, Msrc Update Guide, CVE.org

    Share

    What is affected, what to do

    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.

    Update Linux Kernel to version 5.10.258, Linux Kernel to version 5.15.209, Linux Kernel to version 6.1.175.

    Affected
    • Linux Kernel lt 2.6.12..5.10.258
    • Linux Kernel lt 5.11..5.15.209
    • Linux Kernel lt 5.16..6.1.175
    • Linux Kernel lt 6.2..6.6.141
    • Linux Kernel lt 6.7..6.12.91
    • Linux Kernel lt 6.13..6.18.33
    • Linux Kernel lt 6.19..7.0.10
    Fixed in
    • Linux Kernel 5.10.258
    • Linux Kernel 5.15.209
    • Linux Kernel 6.1.175
    • Linux Kernel 6.6.141
    • Linux Kernel 6.12.91
    • Linux Kernel 6.18.33
    • Linux Kernel 7.0.10
    • Linux Kernel 7.1

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    7.8

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: NVD, CVSS v3

    7.8

    CVSS v3

    Severity High on the scale from 0 to 10.

    Source: SUSE, Debian LTS, BSI, Ubuntu, Red Hat, Msrc Update Guide, CVE.org

    0.1 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 3.4

    Show all metrics
    Severity
    High
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    58.06 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    no public PoC known
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    7.8 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    7.8
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    0.1 %
    Low — model estimates < 1% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    3.4
    Low — this CVE sits in the lower 10% of all CVEs scored today.
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    —
    Published
    CISA assessment (SSVC)
    Exploitation: none known · not automatable · Technical impact: partial
    Source: CISA Vulnrichment, as of 6 November 2026

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    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.

    Source: suse_csaf, Debian LTS Advisories, BSI WID Portal, BSI CSAF, Ubuntu Security Notices, redhat_csaf, Microsoft Security Update Guide, NVD (NIST), CVE.org (MITRE), cvelistv5

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    LinuxLinux
    • 5.16 – < 6.1.175
    • 5.11 – < 5.15.209
    • 2.6.12 – < 5.10.258
    • 6.7 – < 6.12.91
    • —
    • 6.13 – < 6.18.33
    • 6.2 – < 6.6.141
    • 6.19 – < 7.0.10
    • 6.1.175
    • 5.15.209
    • 5.10.258
    • 6.12.91
    • 7.1
    • 6.18.33
    • 6.6.141
    • 7.0.10
    IBMQRadar SIEM
    • <7.5.0 UP15 IF06
    • —

    Vendors and products

    Affected operating systems

    Affected operating systems
    Linuxdebianlinuxbookworm
    Linuxdebianlinuxbullseye
    Linuxdebianlinux-6.1bullseye
    Linuxubuntulinux-oracle-7.0noble
    Linuxlinuxlinux_kernel2.6.12
    Linuxlinuxlinux_kernel—

    References & sources

    Changes to this CVE

    Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

    1. Record modifiedCISA ADP

      CISA assessment (SSVC): exploitation: none known, automatable: no

      Show the original change
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      SSVC assessmentadded
      —
      {"id":"CVE-2026-53059","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"partial"}],"version":"2.0.3","timestamp":"2026-11-06T16:17:22.400461Z"}

      Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

    2. Record modifiedRed Hat ADP

      Show the original change
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Referenceadded
      —
      https://access.redhat.com/errata/RHSA-2026:61692

      Source identifier: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c

    3. Record modifiedRed Hat ADP

      Show 2 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Referenceadded
      —
      https://access.redhat.com/errata/RHSA-2026:56574
      Affected versions (publisher)changed
      Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 8 (+11)
      Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 10.0 Extended Update Support, Red Hat Enterprise Linux 8 (+12)

      Source identifier: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c

    4. Record modifiedRed Hat ADP

      Show the original change
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Referenceadded
      —
      https://access.redhat.com/errata/RHSA-2026:52649

      Source identifier: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c

    5. Record modifiedRed Hat ADP

      Show 4 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Referenceadded
      —
      https://access.redhat.com/errata/RHSA-2026:45114
      Referenceadded
      —
      https://access.redhat.com/errata/RHSA-2026:45116
      Referenceadded
      —
      https://access.redhat.com/errata/RHSA-2026:45192
      Affected versions (publisher)changed
      Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 6 (+5)
      Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 8 (+5)

      Source identifier: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c

    Show 3 older changes

    1. Record modifiedRed Hat ADP

      Show 2 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Referenceadded
      —
      https://access.redhat.com/errata/RHSA-2026:45115
      Affected versions (publisher)changed
      Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 6, Red Hat Enterprise Linux 7 (+5)
      Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 6 (+5)

      Source identifier: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c

    2. Initial analysis by NVDNVD

      Newly listed as affected:
      • Linux Kernel (6.2 – before 6.6.141; 6.7 – before 6.12.91; 6.13 – before 6.18.33; 6.19 – before 7.0.10; 5.16 – before 6.1.175; 5.11 – before 5.15.209; 2.6.12.1 – before 5.10.258; 5 individual versions)

      CVSS V3.1: AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

      Weakness type: CWE-787

      Show 14 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      CVSSadded
      —
      AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
      Weakness type (CWE)added
      —
      CWE-787
      Product configurationadded
      —
      OR *cpe:2.3:o:linux:linux_kernel:2.6.12:rc4:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:2.6.12:rc5:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:2.6.12:rc2:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:2.6.12:rc3:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:2.6.12:-:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.2 up to (excluding) 6.6.141 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.7 up to (excluding) 6.12.91 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.13 up to (excluding) 6.18.33 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.19 up to (excluding) 7.0.10 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.16 up to (excluding) 6.1.175 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.11 up to (excluding) 5.15.209 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 2.6.12.1 up to (excluding) 5.10.258
      Reference typeadded
      —
      kernel.org: https://git.kernel.org/stable/c/12bd5b88e91a02785244ff1d20fb157e96e9cdc8 Types: Patch
      Reference typeadded
      —
      kernel.org: https://git.kernel.org/stable/c/3ec74da927b4e171a6fc0e77b1188ba4d019af51 Types: Patch
      Reference typeadded
      —
      kernel.org: https://git.kernel.org/stable/c/44ab8875ae4a2842bde2d756bed195d375e0debb Types: Patch
      Reference typeadded
      —
      kernel.org: https://git.kernel.org/stable/c/4ec8323b9f0764a14d532b1ae9b87f8a9fecb867 Types: Patch
      Reference typeadded
      —
      kernel.org: https://git.kernel.org/stable/c/b455903eed4558982be0811f5b7f44f6bbc4ff57 Types: Patch
      Reference typeadded
      —
      kernel.org: https://git.kernel.org/stable/c/c20e36b7631d83e7535877f08af8b0af72c44b1a Types: Patch
      Reference typeadded
      —
      kernel.org: https://git.kernel.org/stable/c/d4ac87567f86a55c3c92e9a5144dcd943a9772a1 Types: Patch
      Reference typeadded
      —
      kernel.org: https://git.kernel.org/stable/c/defe483e47173768c227532694dc78cb65db5f09 Types: Patch
      Reference typeadded
      —
      redhat-SADP: https://access.redhat.com/security/cve/CVE-2026-53059 Types: Third Party Advisory
      Reference typeadded
      —
      redhat-SADP: https://bugzilla.redhat.com/show_bug.cgi?id=2492277 Types: Third Party Advisory
      Reference typeadded
      —
      redhat-SADP: https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-53059.json Types: Third Party Advisory

      Source identifier: nvd@nist.gov

    3. ReceivedLinux

      Description added or changed

      Show 10 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Affected versions (publisher)added
      —
      Linux, Linux
      Descriptionadded
      —
      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.
      Referenceadded
      —
      https://git.kernel.org/stable/c/12bd5b88e91a02785244ff1d20fb157e96e9cdc8
      Referenceadded
      —
      https://git.kernel.org/stable/c/3ec74da927b4e171a6fc0e77b1188ba4d019af51
      Referenceadded
      —
      https://git.kernel.org/stable/c/44ab8875ae4a2842bde2d756bed195d375e0debb
      Referenceadded
      —
      https://git.kernel.org/stable/c/4ec8323b9f0764a14d532b1ae9b87f8a9fecb867
      Referenceadded
      —
      https://git.kernel.org/stable/c/b455903eed4558982be0811f5b7f44f6bbc4ff57
      Referenceadded
      —
      https://git.kernel.org/stable/c/c20e36b7631d83e7535877f08af8b0af72c44b1a
      Referenceadded
      —
      https://git.kernel.org/stable/c/d4ac87567f86a55c3c92e9a5144dcd943a9772a1
      Referenceadded
      —
      https://git.kernel.org/stable/c/defe483e47173768c227532694dc78cb65db5f09

      Source identifier: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2026-53059
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-53059"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-53059.svg?lang=en" alt="CVE-2026-53059 – NEOSEC Intel" height="20"></a>