{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2026-23434",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2026-23434"
  ],
  "published": "2026-04-03T15:24:34Z",
  "summary": "mtd: rawnand: serialize lock/unlock against other NAND operations",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nmtd: rawnand: serialize lock/unlock against other NAND operations\n\nnand_lock() and nand_unlock() call into chip->ops.lock_area/unlock_area\nwithout holding the NAND device lock. On controllers that implement\nSET_FEATURES via multiple low-level PIO commands, these can race with\nconcurrent UBI/UBIFS background erase/write operations that hold the\ndevice lock, resulting in cmd_pending conflicts on the NAND controller.\n\nAdd nand_get_device()/nand_release_device() around the lock/unlock\noperations to serialize them against all other NAND controller access.",
  "severity": [
    {
      "type": "CVSS_V3",
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/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.167",
            "compiled_filter": false
          }
        }
      }
    }
  ],
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-23434"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/28ea836cc44cb8b89c1c174707ead0c1133c60e9"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/fe4a73c3dd48308149d57a10c2761e1d36ced7ba"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/ce5229e78078e437704157eb542f43a6f83b429b"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/a80291e577b44593a724d6cd64c14337c78f194d"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/f71ce0ae5aefe39dd5b2f996c0e08550d2153ad2"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/5fd5c078af23cb353507aa522e09d557d7eaef04"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/f25446e2c28939753d3b62d34dfda49952b2557d"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/bab2bc6e850a697a23b9e5f0e21bb8c187615e95"
    }
  ],
  "database_specific": {
    "source": "https://git.kernel.org/pub/scm/linux/security/vulns.git",
    "upstream_modified": "2026-08-05T13:16:28Z",
    "severity": {
      "source": "kernel CNA",
      "cvss_v3_score": 7.1,
      "cvss_v3_severity": "High",
      "scenario": "AV:L - The vulnerable path is reached through local MTD character-device ioctls such as MEMLOCK/MEMUNLOCK on /dev/mtdX, not by network packets or physical hotplug alone.\nAC:L - The attacker can repeatedly issue lock/unlock ioctls while inducing concurrent UBI/UBIFS writes or erase work, so the race is under attacker influence and can be retried.\nPR:L - The kernel path requires write access to the MTD character device but performs no capable() check beyond FMODE_WRITE; when uncertain between device-permission-dependent low and high privilege, the higher-severity PR:L is appropriate.\nUI:N - No victim action is required once the attacker has local access to the relevant MTD device and can trigger concurrent operations.\nS:U - The impact remains within the same kernel/device security authority and does not cross a VM, IOMMU, or sandbox boundary.\nC:N - The bug is a missing NAND controller serialization lock causing command-state races, with no evident kernel memory disclosure or arbitrary read primitive.\nI:H - The race can interleave lock/unlock SET_FEATURES with NAND erase/write operations, plausibly corrupting persistent flash contents or protection state; under the required uncertainty rule, this is scored as high integrity impact.\nA:H - On affected controllers such as brcmnand, the race can hit cmd_pending conflicts and BUG_ON paths, causing a kernel crash or severe storage subsystem failure."
    }
  }
}