Skip to main content
VulnerabilityPublished Updated

CVE-2026-23038: Linux kernel · pnfs/flexfiles: Fix memory leak in nfs4_ff_alloc_deviceid_node()

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in ed5d3f2f6885eb99f729e6ffd946e3aa058bd3eb : update Linux kernel when convenient.

Data as of 26 Oct 2026, 12:55 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS
0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-06-16.

Patch
Available – fixed in ed5d3f2f6885eb99f729e6ffd946e3aa058bd3eb, e2dde5dafb80f1af4028ed10ad255f42af71c784, 869862056e100973e76ce9f5f1b01837771b7722 +4

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 31 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ d67ae825a59d639e4d8b82413af84d854617a87e, < ed5d3f2f6885eb99f729e6ffd946e3aa058bd3eb
Fixed in
  • ed5d3f2f6885eb99f729e6ffd946e3aa058bd3eb
LinuxLinuxAffected
  • ≥ d67ae825a59d639e4d8b82413af84d854617a87e, < e2dde5dafb80f1af4028ed10ad255f42af71c784
Fixed in
  • e2dde5dafb80f1af4028ed10ad255f42af71c784
LinuxLinuxAffected
  • ≥ d67ae825a59d639e4d8b82413af84d854617a87e, < 869862056e100973e76ce9f5f1b01837771b7722
Fixed in
  • 869862056e100973e76ce9f5f1b01837771b7722
LinuxLinuxAffected
  • ≥ d67ae825a59d639e4d8b82413af84d854617a87e, < 86da7efd12295a7e2b4abde5e5984c821edd938f
Fixed in
  • 86da7efd12295a7e2b4abde5e5984c821edd938f
LinuxLinuxAffected
  • ≥ d67ae825a59d639e4d8b82413af84d854617a87e, < 34b9dd179818ff7af2b36410985fd8166573c62d
Fixed in
  • 34b9dd179818ff7af2b36410985fd8166573c62d
LinuxLinuxAffected
  • ≥ d67ae825a59d639e4d8b82413af84d854617a87e, < 27c90d8ed81e7a289c9fe41b5e31d8bb609a3385
Fixed in
  • 27c90d8ed81e7a289c9fe41b5e31d8bb609a3385

Description

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.

References

Community reviews

Loading reviews…