{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2026-64260",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2026-64260"
  ],
  "published": "2026-07-25T08:51:45Z",
  "summary": "fuse-uring: Avoid queue->stopped races and set/read that value under lock",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nfuse-uring: Avoid queue->stopped races and set/read that value under lock\n\nThere are several readers of queue->stopped that check the value\nunder lock, but fuse_uring_commit_fetch() did not and actually\nthe value was not set under the lock in fuse_uring_abort_end_requests()\neither. Especially in fuse_uring_commit_fetch it is important\nto check under a lock, because due to races 'struct fuse_req'\nmight be freed with fuse_request_end, but another thread/cpu\nmight already do teardown work.",
  "severity": [
    {
      "type": "CVSS_V3",
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
    }
  ],
  "affected": [
    {
      "package": {
        "ecosystem": "Raspberry Pi OS:13",
        "name": "linux"
      },
      "versions": [
        "1:6.18.29-1+rpt1",
        "1:6.18.33-1+rpt1",
        "1:6.18.34-1+rpt1"
      ],
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-image-6.18.29+rpt-rpi-2712",
            "binary_version": "1:6.18.29-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.29+rpt-rpi-v6",
            "binary_version": "1:6.18.29-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.29+rpt-rpi-v7",
            "binary_version": "1:6.18.29-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.29+rpt-rpi-v8",
            "binary_version": "1:6.18.29-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.29+rpt-rpi-v8-rt",
            "binary_version": "1:6.18.29-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.33+rpt-rpi-2712",
            "binary_version": "1:6.18.33-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.33+rpt-rpi-v6",
            "binary_version": "1:6.18.33-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.33+rpt-rpi-v7",
            "binary_version": "1:6.18.33-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.33+rpt-rpi-v8",
            "binary_version": "1:6.18.33-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.33+rpt-rpi-v8-rt",
            "binary_version": "1:6.18.33-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.34+rpt-rpi-2712",
            "binary_version": "1:6.18.34-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.34+rpt-rpi-v6",
            "binary_version": "1:6.18.34-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.34+rpt-rpi-v7",
            "binary_version": "1:6.18.34-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.34+rpt-rpi-v8",
            "binary_version": "1:6.18.34-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.34+rpt-rpi-v8-rt",
            "binary_version": "1:6.18.34-1+rpt1"
          }
        ]
      },
      "database_specific": {
        "per_version": {
          "1:6.18.29-1+rpt1": {
            "linux_commit": "66318c5b5cd8145a662303af12ed39ac07eb27cc",
            "upstream_version": "6.18.29",
            "assessment": "commit ancestry (strak rule)",
            "upstream_fixed": "6.18.39"
          },
          "1:6.18.33-1+rpt1": {
            "linux_commit": "95b85bebbedcaedfa7ca79116ed38b7376fba412",
            "upstream_version": "6.18.33",
            "assessment": "commit ancestry (strak rule)",
            "upstream_fixed": "6.18.39"
          },
          "1:6.18.34-1+rpt1": {
            "linux_commit": "c8c7494100e99ee05b11aaa4f0588a223a63d1af",
            "upstream_version": "6.18.34",
            "assessment": "commit ancestry (strak rule)",
            "upstream_fixed": "6.18.39"
          }
        }
      }
    }
  ],
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-64260"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/39c8e925b207afceffaa5382416ed405e0223a03"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/4021a3a79eee551d95fe1e1e7c1b195d34ba8c08"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/b70a3aca16934c196f92abb17b01c1647b9bb63c"
    }
  ],
  "database_specific": {
    "source": "https://git.kernel.org/pub/scm/linux/security/vulns.git",
    "upstream_modified": "2026-08-17T05:24:08Z",
    "severity": {
      "source": "kernel CNA",
      "cvss_v3_score": 7.8,
      "cvss_v3_severity": "High",
      "scenario": "AV:L - The flaw is reached locally by submitting IORING_OP_URING_CMD/FUSE_IO_URING_CMD_COMMIT_AND_FETCH operations on an attached /dev/fuse descriptor.\nAC:L - Once FUSE-over-io-uring is enabled, the attacker controls both race participants by issuing commit SQEs while concurrently aborting or unmounting the connection.\nPR:L - An ordinary user can create a FUSE mount through FS_USERNS_MOUNT and user namespaces, submit commands through /dev/fuse, and access the user-owned fusectl abort control without init-namespace capabilities.\nUI:N - The attacker can create the mount, generate FUSE requests, submit commits, and trigger teardown without another user's participation.\nS:U - This is a standard local kernel privilege-escalation condition within the kernel's security authority, not a guest-to-host or IOMMU boundary escape.\nC:H - The race causes a fuse_req use-after-free and double-end with stale list, pointer, and refcount accesses, which can be leveraged to disclose arbitrary kernel memory.\nI:H - Teardown writes through stale list pointers, flags, error fields, and refcounts and can corrupt or double-free a reallocated fuse_req, enabling arbitrary kernel writes or control-flow hijacking.\nA:H - The use-after-free, list corruption, and double-ending of requests can cause an oops, panic, deadlock, or complete system compromise."
    }
  }
}