boxscore/security
CVE · referencelatest edition

Reference page — cumulative record through Wednesday, August 19, 2026 UTC. Reference pages update as the archive grows; only dated daily editions are immutable pages of record.

CVE-2023-52909MEDIUM
Linux Linux — nfsd: fix handling of cached open files in nfsd4_open codepath
  AV  AC  PR  UI  S  C  I  A   CVSS    EPSS   %ile   KEV
   L   H   L   N  U  N  N  H    4.7   .0064   48.0     —
AFFECTED
  Product  Versions                                    Fixed
  Linux    c20097329d2c196b818c4666c7820c1378d69d61 –  —
  Linux    5.19 –                                      6.1.7
TIMELINE
  Aug 21  Reserved by Linux
  Aug 21  Published (CNA: Linux)
  Aug 4   RESCORED — CVE-2023-52909 (Linux). CVSS 7.5 → 4.7 (NVD).
CWE-476 · CNA: Linux · CVSS v3.1 · 4 references · NVD status: Modified

Description

In the Linux kernel, the following vulnerability has been resolved: nfsd: fix handling of cached open files in nfsd4_open codepath Commit fb70bf124b05 ("NFSD: Instantiate a struct file when creating a regular NFSv4 file") added the ability to cache an open fd over a compound. There are a couple of problems with the way this currently works: It's 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'll 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'll take a new reference to it instead of trying to open the file. If the nfsd_file already has a valid nf_file, we'll just ignore the optional file and pass the nfsd_file back as-is. Also rework the tracepoints a bit to allow for an "opened" variant and don't try to avoid counting acquisitions in the case where we already have a cached open file.

Lifecycle

Complete event history — 3 events, chronological
DateEventDetail
August 21, 2024ReservedReserved by Linux
August 21, 2024PublishedPublished (CNA: Linux)
August 4, 2026RESCOREDRESCORED — CVE-2023-52909 (Linux). CVSS 7.5 → 4.7 (NVD).

Affected

Affected products and packages — 2 rows
VendorProduct / PackageEcosystemVersion introducedFixed
LinuxLinuxc20097329d2c196b818c4666c7820c1378d69d61
LinuxLinux5.196.1.7

Weaknesses

CWE-476

References (4)

Related

Authoritative record: CVE-2023-52909 at cve.org

Vendors: linux

Weaknesses: CWE-476

About this page

This is a reference page, not a dated page of record. It assembles the complete lifecycle of CVE-2023-52909 from the CVE Program record, NVD enrichment, the CISA KEV catalog, EPSS, and OSV advisories. The box score's numbers (CVSS, EPSS, KEV status) are current as of Wednesday, August 19, 2026 UTC and are re-derived as the archive grows; only dated daily editions are immutable pages of record. The authoritative source for this identifier is cve.org.