LiveActive security incident?Get immediate response
CVE Record

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

A Linux kernel error path can leave allocated memory unreleased when an allocation fails in the pNFS FlexFiles client. Repeated triggering could increase memory consumption and potentially affect availability. The supplied sources provide no CVSS score or confirmed real-world exploitation.

Executive priority

Treat this as a targeted availability and maintenance issue, not an emergency based on current evidence. Identify pNFS FlexFiles users first, then deploy supported kernel fixes through normal expedited patching. Reassess promptly if vendors publish severity, exposure, or exploitation evidence.

Technical view

In nfs4_ff_alloc_deviceid_node(), failure to allocate ds_versions jumps to out_scratch without freeing the existing dsaddrs list. The published correction redirects execution to out_err_drain_dsaddrs, which drains that list before other cleanup.

Likely exposure

Exposure is limited to affected Linux kernels exercising the pNFS FlexFiles device-ID allocation path when the ds_versions allocation fails. The supplied affected-version data includes 4.0, 5.10.249, 5.15.199, 6.1.162, 6.6.122, 6.12.67, 6.18.7, 6.19, and an ambiguous entry of 0.

Exploitation context

The CVE is not listed as KEV in the supplied bundle. No source provided here reports active exploitation, a public exploit, required attacker access, or a demonstrated security impact beyond the memory leak.

Researcher notes

The vulnerable condition is a secondary allocation failure after dsaddrs has already been allocated. The source bundle supplies multiple stable-tree fix commits but does not map each commit to a specific release. It also lacks CVSS, CWE, reachability, privilege, and trigger-frequency evidence; the anomalous affected version 0 should be verified against vendor data.

Mitigation direction

  • Apply a vendor-supported kernel update containing the relevant stable fix.
  • Check distribution or appliance guidance for backported fixes and corrected package versions.
  • Prioritize systems that actively use pNFS FlexFiles.
  • Use vendor guidance if an update is unavailable; no workaround is documented here.

Validation and detection

  • Inventory running kernel versions and vendor package revisions.
  • Confirm whether pNFS FlexFiles is configured or used on each system.
  • Verify vendor changelogs or backport records reference CVE-2026-23038 or the linked fix.
  • After updating, confirm the corrected kernel is running following any required reboot.
  • Monitor affected systems for abnormal kernel-memory growth while remediation is pending.
Prepared
Confidence
medium
Sources
9

Public sources used

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.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

0CVSS vectors
3Timeline events
2ADP providers
10Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

siemens-SADPADP container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxd67ae825a59d639e4d8b82413af84d854617a87e, d67ae825a59d639e4d8b82413af84d854617a87e, d67ae825a59d639e4d8b82413af84d854617a87e, d67ae825a59d639e4d8b82413af84d854617a87e, d67ae825a59d639e4d8b82413af84d854617a87e, d67ae825a59d639e4d8b82413af84d854617a87e, d67ae825a59d639e4d8b82413af84d854617a87eunaffected
LinuxLinux4.0, 0, 5.10.249, 5.15.199, 6.1.162, 6.6.122, 6.12.67, 6.18.7, 6.19affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.