{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2026-72107",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2026-72107"
  ],
  "published": "2026-08-15T06:04:33Z",
  "summary": "dm era: fix out-of-bounds memory access for non-zero start sector",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\ndm era: fix out-of-bounds memory access for non-zero start sector\n\ndm-era tracks writes in target-relative blocks, but era_map() calculates\nthe writeset block before applying the target offset.  Tables with a\nnon-zero start sector can therefore pass an absolute mapped-device block\nto metadata_current_marked().\n\nIf the absolute block is beyond the current writeset size,\nwriteset_marked() tests past the end of the in-core bitset.  KASAN reports\nthis as a vmalloc-out-of-bounds access.\n\nApply the target offset before calculating the era block so writeset\nlookups use the target-relative block number.",
  "severity": [
    {
      "type": "CVSS_V3",
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
    }
  ],
  "affected": [
    {
      "package": {
        "ecosystem": "Raspberry Pi OS:12",
        "name": "linux"
      },
      "versions": [
        "1:6.1.47-1+rpt4"
      ],
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-2712",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v6",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v7",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v7l",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v8",
            "binary_version": "1:6.1.47-1+rpt4"
          }
        ]
      },
      "database_specific": {
        "per_version": {
          "1:6.1.47-1+rpt4": {
            "linux_commit": "655fc658a15ae7a6f37103754adb39ba52a9a14e",
            "upstream_version": "6.1.47",
            "assessment": "commit ancestry (strak rule)",
            "upstream_fixed": "6.1.178",
            "compiled_filter": false
          }
        }
      }
    }
  ],
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-72107"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/fe94a0b14010a3c267ff9a2508afb4f27ff1c5bf"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/e3ffa8e492e5cdee62d916ee3e9244ccce2b73c5"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/9946a7176bd8c25ddd6e5f1799c54e572ee6bf0f"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/7e1822f83c5a1ee7b4a19e98edde8770a10b4c71"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/db5f9b4601f0012038e5a2628aedec2f47933380"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/1fcb5e29dd7a5b85adb9d8b539911741d878e829"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/bafe3e720cdac38cd7ea4eb7852a8f2dbe1bbfe6"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/a868196f03c2b19418ae3d2b69e195d668a271e5"
    }
  ],
  "database_specific": {
    "source": "https://git.kernel.org/pub/scm/linux/security/vulns.git",
    "upstream_modified": "2026-08-17T05:50:24Z",
    "severity": {
      "source": "kernel CNA",
      "cvss_v3_score": 8.8,
      "cvss_v3_severity": "High",
      "scenario": "AV:N - The bug is hit in era_map() on write bios submitted to a dm-era device; on storage servers that expose dm-era-backed LUNs via iSCSI or NVMe-oF, a remote initiator's SCSI/NVMe writes traverse the network stack into dm_submit_bio() and reach the flawed writeset lookup without local shell access.\nAC:L - Once a dm-era table uses a non-zero start sector (common when mapping a partition offset), any single write I/O deterministically passes an out-of-range block index to writeset_marked()/test_bit(); no race, special heap layout, or victim state beyond that configuration is required.\nPR:L - Exploitation requires only write access to the dm-era-backed block device (filesystem, raw /dev/dm-* node, or authenticated iSCSI/NVMe-oF initiator credentials); loading the dm table needs CAP_SYS_ADMIN, but triggering the OOB read does not\u2014unprivileged local users or remote storage clients with write permission suffice.\nUI:N - Triggering the flaw requires only the attacker's own write I/O to the dm-era volume; no victim must mount a filesystem, open a file, click a link, or perform any separate interactive action beyond routine storage writes.\nS:U - The vmalloc out-of-bounds read and any resulting kernel oops or privilege escalation occur entirely within the host kernel's device-mapper/storage subsystem on the same machine; this is not a VM escape, IOMMU bypass, or other cross-security-authority boundary violation.\nC:H - writeset_marked() calls test_bit() with an attacker-influenced block index derived from the write offset; when the absolute block exceeds the writeset size this is a vmalloc out-of-bounds read that can disclose adjacent kernel heap memory, matching CNA guidance for OOB reads.\nI:H - Kernel vmalloc out-of-bounds access via test_bit() is memory corruption in a privileged context; disclosed adjacent heap contents can be used to craft follow-on arbitrary-write or control-flow hijack primitives, so integrity impact is rated High when uncertain between Low and High.\nA:H - KASAN reports this as vmalloc-out-of-bounds, and reading past the vzalloc'd bitset can fault on unmapped pages or provoke a kernel oops/panic, causing immediate denial of service on storage nodes processing writes through dm-era."
    }
  }
}