{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2026-74313",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2026-74313"
  ],
  "published": "2026-08-15T06:04:33Z",
  "summary": "vduse: hold vduse_lock across IDR lookup in open path",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nvduse: hold vduse_lock across IDR lookup in open path\n\nvduse_dev_open() looks up struct vduse_dev through the IDR and then\nacquires dev->lock only after vduse_lock has been dropped.\n\nThis leaves a window where a concurrent VDUSE_DESTROY_DEV can remove the\nsame object from the IDR and free it before the open path locks the\ndevice, leading to a use-after-free.\n\nClose this race by keeping vduse_lock held until dev->lock has been\nacquired in the open path, matching the lock ordering already used by\nthe destroy path.",
  "severity": [
    {
      "type": "CVSS_V3",
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/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-74313"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/35483c5306e09b3190ff937089d404a78012695c"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/5c1560be8aa6849356455af67518d35c551cbd95"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/93ed4692f2299a40346025979f40e4a9b7b33af7"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/d94e2947203aead590fd63f667d316d4475d65af"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/a2d0a57538fd0b3b3ab75d64bb64f4cd2fab13a2"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/79e12c891940b0c4c75881b7fd82a8cbb8ac97be"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/e440e077748939839d9f76e24383b76b785f80ce"
    }
  ],
  "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:L - The vulnerability is only reachable via local syscalls on VDUSE character devices: open(2) on /dev/vduse/$NAME racing with ioctl(VDUSE_DESTROY_DEV) on /dev/vduse/control. It is not triggered by remote network traffic, adjacent wireless protocols, or physical device attachment.\nAC:L - The attacker fully controls both sides of the race by creating a VDUSE device, then concurrently calling open() and VDUSE_DESTROY_DEV from their own threads. No timing or layout conditions outside attacker control are required beyond standard thread scheduling.\nPR:L - Neither the open nor destroy paths enforce capabilities beyond device-node access; only VIRTIO_ID_NET creation requires CAP_NET_ADMIN. VDUSE is designed so userspace dataplane operators with access to /dev/vduse nodes can create, open, and destroy block devices without full host admin rights.\nUI:N - Exploitation requires no victim interaction. The attacker creates their own VDUSE instance and triggers the open/destroy race from their process; no separate user must mount, configure, or open the device.\nS:C - On cloud and virtualization hosts where VDUSE is delegated to containers or NFV tenant workloads, kernel UAF exploitation crosses from the tenant/container security boundary to full host kernel compromise, comparable to a VM or sandbox escape.\nC:H - The race produces a use-after-free of kmalloc'd struct vduse_dev. Locking and dereferencing the freed object, plus subsequent ioctl/read/write using dangling file->private_data, enables slab reuse and arbitrary kernel memory disclosure.\nI:H - UAF of vduse_dev allows heap grooming over mutexes, virtqueue pointers, and config buffers. Follow-on VDUSE ioctls (SET_CONFIG, VQ_SETUP, IOTLB) on the dangling fd provide exploitable arbitrary-write and control-flow hijack primitives.\nA:H - Use-after-free during mutex_lock on the freed device or later VDUSE operations can immediately corrupt kernel memory and trigger oops/panic, fully denying system availability even before full exploitation."
    }
  }
}