CVE-2026-23038: pnfs/flexfiles: Fix memory leak in nfs4_ff_alloc_deviceid_node()
In the Linux kernel, the following vulnerability has been resolved:
pnfs/flexfiles: Fix memory leak in nfs4_ff_alloc_deviceid_node()
In nfs4_ff_alloc_deviceid_node(), if the allocation for ds_versions fails,
the function jumps to the out_scratch label without freeing the already
allocated dsaddrs list, leading to a memory leak.
Fix this by jumping to the out_err_drain_dsaddrs label, which properly
frees the dsaddrs list before cleaning up other resources.
Security readout for executives and security teams
Plain-English summary
CVE-2026-23038 is a Linux kernel memory leak in the pNFS flexfiles client path. A failed allocation can leave an already allocated address list unreleased. The public record does not provide CVSS, exploitation evidence, or confirmed business impact beyond resource leakage risk.
Executive priority
Treat as a kernel maintenance item unless pNFS flexfiles is widely used in critical environments. There is no source evidence of active exploitation or rated severity, but kernel memory leaks can affect availability if repeatedly triggered.
Technical view
In nfs4_ff_alloc_deviceid_node(), failure allocating ds_versions incorrectly jumps to out_scratch, bypassing cleanup of dsaddrs. The fix redirects cleanup through out_err_drain_dsaddrs so the dsaddrs list is freed before other resources are released.
Likely exposure
Exposure appears limited to Linux systems running affected kernel versions with the NFSv4 pNFS flexfiles code path reachable. The bundle lists Linux kernel versions as affected and provides stable kernel fix commits. Siemens advisories are referenced, but this bundle does not identify specific Siemens affected products.
Exploitation context
The source bundle marks KEV as false and provides no active exploitation report, exploit availability, or attack preconditions. The issue is a cleanup-path memory leak, so practical impact depends on whether an attacker or workload can repeatedly trigger the failed allocation path.
Researcher notes
Evidence supports a specific Linux kernel cleanup bug and fix path. The bundle lacks CVSS, CWE, exploit status, detailed reachability, and Siemens product impact. Avoid claiming remote exploitation without additional vendor or researcher evidence.
Mitigation direction
Update to a vendor-supported Linux kernel containing the referenced stable fixes.
Track distribution and Siemens advisories for product-specific remediation guidance.
Prioritize hosts using NFSv4 pNFS flexfiles functionality.
If pNFS flexfiles is unnecessary, review vendor guidance for reducing exposure.
Validation and detection
Inventory Linux kernel versions against the affected version list.
Confirm whether the stable fix commit is present or backported.
Identify systems using NFSv4 pNFS flexfiles mounts or configurations.
Review vendor advisories for appliance or embedded Linux exposure.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-23038 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.