{
  "cveId": "CVE-2023-52909",
  "url": "https://patchblox.com/security/cve/CVE-2023-52909",
  "summary": "CVE-2023-52909 is fixed in linux on 1 platform, first by DEBIAN-CVE-2023-52909, released August 21, 2024. It is not reported as exploited. Patch Radar priority: Routine.",
  "title": "linux: In the Linux kernel, the following vulnerability has been resolved:  nfsd: fix handling of cached open files in nfsd4...",
  "description": "In the Linux kernel, the following vulnerability has been resolved:  nfsd: fix handling of cached open files in nfsd4_open codepath  Commit fb70bf124b05 (\u0022NFSD: Instantiate a struct file when creating a regular NFSv4 file\u0022) added the ability to cache an open fd over a compound. There are a couple of problems with the way this currently works:  It\u0027s racy, as a newly-created nfsd_file can end up with its PENDING bit cleared while the nf is hashed, and the nf_file pointer is still zeroed out. Other tasks can find it in this state and they expect to see a valid nf_file, and can oops if nf_file is NULL.  Also, there is no guarantee that we\u0027ll end up creating a new nfsd_file if one is already in the hash. If an extant entry is in the hash with a valid nf_file, nfs4_get_vfs_file will clobber its nf_file pointer with the value of op_file and the old nf_file will leak.  Fix both issues by making a new nfsd_file_acquirei_opened variant that takes an optional file pointer. If one is present when this is called, we\u0027ll take a new reference to it instead of trying to open the file. If the nfsd_file already has a valid nf_file, we\u0027ll just ignore the optional file and pass the nfsd_file back as-is.  Also rework the tracepoints a bit to allow for an \u0022opened\u0022 variant and don\u0027t try to avoid counting acquisitions in the case where we already have a cached open file.",
  "published": "2024-08-21T07:15:06Z",
  "severity": "medium",
  "cvss": 4.7,
  "cvssVector": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H",
  "epss": 0.00643,
  "epssPercentile": 0.51065,
  "priority": "Routine",
  "priorityTier": 4,
  "exploited": false,
  "vendorExploited": false,
  "disclosed": false,
  "fixes": [
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 12.15 (bookworm)",
      "fixedVersion": "6.1.7-1",
      "fix": "DEBIAN-CVE-2023-52909",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2023-52909",
      "released": "2024-08-21T07:15:06Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 13.5 (trixie)",
      "fixedVersion": "6.1.7-1",
      "fix": "DEBIAN-CVE-2023-52909",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2023-52909",
      "released": "2024-08-21T07:15:06Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 14",
      "fixedVersion": "6.1.7-1",
      "fix": "DEBIAN-CVE-2023-52909",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2023-52909",
      "released": "2024-08-21T07:15:06Z"
    }
  ],
  "noFixYet": [],
  "dataAsOf": "2026-11-08T13:06:02Z",
  "attribution": {
    "text": "Data: Patchblox Patch Radar",
    "url": "https://patchblox.com/security/patch-radar",
    "terms": "https://patchblox.com/security/patch-radar/use-the-data"
  }
}