{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2026-64118",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2026-64118"
  ],
  "published": "2026-07-19T15:41:06Z",
  "summary": "qed: fix double free in qed_cxt_tables_alloc()",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nqed: fix double free in qed_cxt_tables_alloc()\n\nIf one of the later PF or VF CID bitmap allocations fails,\nqed_cid_map_alloc() jumps to cid_map_fail and frees the previously\nallocated CID bitmaps before returning an error. qed_cxt_tables_alloc()\nthen calls qed_cxt_mngr_free(), which invokes qed_cid_map_free()\nagain.\n\nFix this by setting each CID bitmap pointer to NULL after bitmap_free()\nto avoid double free.\n\nThe bug was first flagged by an experimental analysis tool we are\ndeveloping for kernel memory-management bugs while analyzing\nv6.13-rc1. The tool is still under development and is not yet publicly\navailable. Manual inspection confirms that the bug is still\npresent in v7.1-rc3.\n\nRuntime reproduction was not attempted because exercising the failing\nallocation path requires device-specific setup.",
  "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.175",
            "compiled_filter": false
          }
        }
      }
    }
  ],
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-64118"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/9fe030719bd083b766602692ee96c8c985798e3c"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/06fa8e69019fd3c41a7b0ea8c5f509c3a33dc227"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/8cf5e4d2ca6b101d163c7423a426fb0aec34f7bb"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/3904b993cc17ec5d7c5d3b57dbd0b775dafb9684"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/bdf678a273cadbccc347f331ae2e93ff4d14834c"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/0e47fc1c9181ae029e0e35a865cbf2adcbae626c"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/a04c207f0801abdd23a169b5f902a9845059a65a"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/2bccfb8476ca5f3548afbd623dc7a6980d4e77de"
    }
  ],
  "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": 8.4,
      "cvss_v3_severity": "High",
      "scenario": "AV:L - The vulnerable code runs only during PF driver resource initialization (probe or firmware-initiated recovery), reached via local kernel driver bring-up paths rather than network packet processing or remote protocol handlers.\nAC:L - An attacker who can influence system memory pressure (e.g., via local memory exhaustion) can reliably force `bitmap_zalloc()` failures during the multi-step CID bitmap allocation loop, and can also time this with firmware recovery reprobes that re-enter `qed_resc_alloc()`.\nPR:N - No local account or capability is strictly required if a remote attacker can induce firmware process-kill recovery on an internet-facing QED host, causing automatic re-execution of `qed_resc_alloc()` where post-incident memory pressure can trigger the failing allocation path.\nUI:N - Exploitation does not require any victim user action such as opening files or mounting filesystems; driver recovery and re-allocation occur automatically in kernel context once the error/recovery conditions are met.\nS:U - Impact is confined to kernel heap corruption and potential privilege escalation within the same kernel security boundary, not a cross-authority escape such as VM breakout or IOMMU bypass.\nC:H - A double-free of kmalloc-allocated CID bitmap objects corrupts the kernel slab allocator state, which is classically leverageable for arbitrary kernel memory disclosure through heap manipulation primitives.\nI:H - Slab double-free is a standard heap corruption primitive that can be developed into arbitrary kernel writes and control-flow hijacking, not merely a bounded or cosmetic modification.\nA:H - Double-free during driver initialization can cause immediate kernel oops/panic from allocator corruption, and repeated recovery attempts on production QED hardware can produce sustained denial of service."
    }
  }
}