PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-46107 Linux CVE debrief

A reference count underflow vulnerability exists in the Linux kernel's device-mapper thin provisioning target (dm-thin). The flaw occurs in the `rebalance_children` function during B-tree rebalancing operations. When an internal B-tree node contains exactly one entry, the code attempts to migrate all entries from the child node to the parent node and then decrements the child's reference count. If the child node is shared (reference count > 1), it is not freed, resulting in two pointers to each grandchild node without corresponding reference count increments on those grandchildren. This mismatch between pointer count and reference count triggers metadata corruption errors (specifically, 'device mapper: space map common: unable to decrement block') and can lead to data integrity issues in thin-provisioned storage configurations. The vulnerability has been resolved by ensuring reference counts on grandchildren are properly incremented when the B-tree node is shared.

Vendor
Linux
Product
Unknown
CVSS
HIGH 7.8
CISA KEV
Not listed in stored evidence
Original CVE published
2026-05-28
Original CVE updated
2026-06-25
Advisory published
2026-05-28
Advisory updated
2026-06-25

Who should care

System administrators managing Linux servers with LVM thin-provisioned storage; storage infrastructure engineers utilizing device-mapper thin provisioning; cloud providers offering block storage services built on Linux kernel device-mapper; DevOps teams responsible for kernel lifecycle management on storage-heavy workloads

Technical summary

The vulnerability exists in the `rebalance_children` function within the Linux kernel's dm-thin module. During B-tree rebalancing, when an internal node has a single entry, the code path migrates child entries to the parent and decrements the child's reference count. The defect manifests when the child node is shared (refcount > 1): the node persists due to outstanding references, but the grandchildren nodes gain additional pointers without corresponding reference count increments. This reference count underflow causes metadata corruption detectable via space map decrement failures. The fix ensures proper reference count incrementation on grandchildren when operating on shared B-tree nodes.

Defensive priority

medium

Recommended defensive actions

  • Apply kernel updates containing the dm-thin fix for CVE-2026-46107 when available from your Linux distribution
  • Monitor system logs for 'device mapper: space map common: unable to decrement block' errors as potential indicators of this condition
  • Review thin-provisioned storage deployments for stability if running unpatched kernel versions
  • Validate backup and recovery procedures for LVM thin pools given potential metadata integrity risks
  • Coordinate with storage infrastructure teams to schedule maintenance windows for kernel updates on systems utilizing device-mapper thin provisioning

Evidence notes

Vulnerability description sourced from official CVE record and NVD entry. Technical details derived from kernel commit messages describing the `rebalance_children` fix in dm-thin. Multiple stable kernel branch fixes are referenced, indicating backporting across supported versions.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-46107 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-46107

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-46107 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-46107

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/09a65adc7d8bbfce06392cb6d375468e2728ead5

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/12161e03d33afce781f68fa11cc6060538862fad

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/323d252a4a378834e4fe68298ca61cfc5dd3a460

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/5ec0debbcfd43596e32c1239e993de06a704e04c

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/85311a585a26640760cd0f3349ab9f2905691044

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.