{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2026-64016",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2026-64016"
  ],
  "published": "2026-07-19T15:41:06Z",
  "summary": "ksmbd: fix durable reconnect error path file lifetime",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: fix durable reconnect error path file lifetime\n\nAfter a durable reconnect succeeds, ksmbd_reopen_durable_fd() republishes\nthe same ksmbd_file into the session volatile-id table. If smb2_open()\nthen takes a later error path, cleanup first calls ksmbd_fd_put(work, fp)\nand then unconditionally calls ksmbd_put_durable_fd(dh_info.fp).\n\nIn this case fp and dh_info.fp are the same object. The first put drops the\nreconnect lookup reference, but the final durable put can run\n__ksmbd_close_fd(NULL, fp). Because the final close is not session-aware,\nit can free the file object without removing the volatile-id entry that was\njust published into the session table.\n\nUse the session-aware put for the final reconnect drop when the reconnect\nhad already succeeded and the error path is cleaning up the republished\nfile. Earlier reconnect failures, before fp is assigned to dh_info.fp, keep\nusing the durable-only put path.",
  "severity": [
    {
      "type": "CVSS_V3",
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
    }
  ],
  "affected": [
    {
      "package": {
        "ecosystem": "Raspberry Pi OS:13",
        "name": "linux"
      },
      "versions": [
        "1:6.18.33-1+rpt1"
      ],
      "ecosystem_specific": {
        "binaries": [
          {
            "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"
          }
        ]
      },
      "database_specific": {
        "per_version": {
          "1:6.18.33-1+rpt1": {
            "linux_commit": "95b85bebbedcaedfa7ca79116ed38b7376fba412",
            "upstream_version": "6.18.33",
            "assessment": "commit ancestry (strak rule)",
            "upstream_fixed": "6.18.34"
          }
        }
      }
    }
  ],
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-64016"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/5e641e4ee0bc1937408d41051a908ad4151be63b"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/478bfaa036bd0c7e179acff8b8484bccdee3b8c7"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/a1a39f227c80cbf369767badc32cba2b225147d1"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/6cb0b9385320110fe24a5d5ac0000ade4bb3a3f3"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/3515503322f4819277091839eed46b695096aca5"
    }
  ],
  "database_specific": {
    "source": "https://git.kernel.org/pub/scm/linux/security/vulns.git",
    "upstream_modified": "2026-09-14T12:06:03Z",
    "severity": {
      "source": "kernel CNA",
      "cvss_v3_score": 9.8,
      "cvss_v3_severity": "Critical",
      "scenario": "AV:N - The vulnerability is reached through ksmbd's in-kernel SMB2 server on TCP port 445 via SMB2_CREATE durable-handle reconnect processing in smb2_open(), reachable by any remote SMB client that can connect to the server.\nAC:L - An authenticated attacker can fully control the durable reconnect sequence (open with durable handle, disconnect to preserve it, reconnect, then force a post-reconnect error such as ksmbd_iov_pin_rsp() ENOMEM) and immediately exercise the stale volatile file ID via further SMB2 operations.\nPR:N - Exploitation requires only network reachability to ksmbd and valid SMB session credentials (guest or any share user); no elevated kernel privileges, capabilities, or local access are needed beyond what any remote SMB client possesses.\nUI:N - No victim user interaction is required beyond the server running ksmbd with durable handles enabled; the attacker drives the entire reconnect-and-error sequence over the network.\nS:U - The use-after-free corrupts kernel heap memory within the ksmbd server context and can lead to privilege escalation on the host, but does not cross a VM, container, or IOMMU security boundary.\nC:H - Freeing the ksmbd_file while its volatile ID remains in the session IDR creates a use-after-free; subsequent ksmbd_lookup_fd_slow() dereferences freed slab memory, enabling kernel information disclosure.\nI:H - The UAF corrupts kernel heap objects (struct ksmbd_file in the filp kmem cache) and can be leveraged with heap grooming for arbitrary kernel memory writes or code execution.\nA:H - Use-after-free of the ksmbd_file object can cause kernel oopses or panics when freed memory is reused or dereferenced during subsequent SMB2 file operations on the stale volatile ID."
    }
  }
}