{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2026-72489",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2026-72489"
  ],
  "published": "2026-08-15T06:04:33Z",
  "summary": "staging: nvec: fix use-after-free in nvec_rx_completed()",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nstaging: nvec: fix use-after-free in nvec_rx_completed()\n\nIn nvec_rx_completed(), when an incomplete RX transfer is detected,\nnvec_msg_free() is called to return the message back to the pool by\nclearing its 'used' atomic flag. Immediately after this, the code\naccesses nvec->rx->data[0] to check the message type.\n\nSince nvec_msg_free() marks the pool slot as available via atomic_set(),\nany concurrent or subsequent call to nvec_msg_alloc() could claim that\nsame slot and overwrite its data[] array. Reading nvec->rx->data[0] after\nfreeing the message is therefore a use-after-free.\n\nFix this by saving the message type byte before calling nvec_msg_free(),\nthen using the saved value for the battery quirk check.",
  "severity": [
    {
      "type": "CVSS_V3",
      "score": "CVSS:3.1/AV:L/AC:L/PR:N/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-72489"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/6b2ea886ebdae44a2394029844a4e78f58e1587d"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/a37625c7b688fcf68a54263528eccbabfd7fa17a"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/9f7fe4165a1f1014bdadc8e744c0fd3c2d8c0b89"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/08626fcfe12308ca3f8b22c538ba7dee0b2dce7a"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/f19a5bc059051143c489dd6f79a0f9c3bfd13aea"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/bb3d592c7d6c4ec8ac6640c690ca13298e7e8e90"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/5de04caa46b635e180cecbd164e333eca535db94"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/26813881181deb3a32fbb59eadb2599cbe8423f6"
    }
  ],
  "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.4,
      "cvss_v3_severity": "High",
      "scenario": "AV:L - The flaw is hit in the I2C slave IRQ handler when the embedded controller ends an RX transfer early; on affected Tegra20 PAZ00 netbooks a local actor can reach it by stressing EC traffic via kernel battery polling and userspace sysfs/input subdrivers (LED, keyboard) that call nvec_write_async().\nAC:L - This is a use-after-free where nvec_msg_free() returns the RX pool slot and the handler immediately re-reads nvec->rx->data[0]; on SMP an attacker can provoke incomplete NVEC_BAT responses while concurrent I2C IRQs call nvec_msg_alloc(), controlling both sides of the slot-reuse race.\nPR:N - No elevated privileges are needed because the nvec-power delayed worker automatically issues NVEC_BAT requests every five seconds at boot, and documented incomplete EC battery responses can reach the vulnerable IRQ path before any user authentication or special capabilities.\nUI:N - Exploitation does not require victim interaction; kernel background battery and AC polling plus EC-initiated incomplete transfers can invoke nvec_rx_completed() without the user mounting filesystems, opening files, or performing other deliberate actions.\nS:U - Impact is confined to kernel memory and privileges on the same Tegra SoC running the driver; this is not a VM escape, hypervisor breakout, or other cross-security-authority boundary violation.\nC:H - Reading nvec->rx->data[0] after nvec_msg_free() is a use-after-free on a msg_pool slot where concurrent nvec_msg_alloc() can overwrite data[], yielding attacker-influenced kernel memory reads and potential disclosure of pointers or adjacent structure contents.\nI:H - Use-after-free on reusable nvec_msg pool entries can be leveraged for controlled reuse of freed message buffers, enabling heap-style corruption primitives that may lead to arbitrary kernel memory writes and privilege escalation or code execution.\nA:H - The post-free read can mis-handle ec_transfer completion and corrupt IRQ-time state; use-after-free in hardirq context can kernel oops or panic the system, consistent with the original battery-quirk crash this code path was introduced to mitigate."
    }
  }
}