Skip to main content
VulnerabilityPublished Updated

CVE-2026-97610: Linux kernel · netfs: Fix uninitialized return value in netfs_unbuffered_write()

Affects Linux kernelSource CVE Database V5

0

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

Data as of 26 Oct 2026, 13:37 UTC

Severity
Low

Rated Low by Threat Radar's AI analysis · CVSS not yet scored by NVD

EPSS
0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in f18e8774f4d3137fa0a5fb8ffa83d59a719666d8, 6.20, 6.18.53 +2

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Sep 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
  • >=6.18.17 <6.18.53
  • >=6.19.7 <6.20
Fixed in
  • f18e8774f4d3137fa0a5fb8ffa83d59a719666d8
  • 6.20
  • 6.18.53
  • 3d038eebdbd400c3bc4b66bd8aa0dff0c2bcce26
  • 2e38d500471d097cda87d7d374bbc1b13493075d
LinuxLinuxAffected
  • =7.0
Fixed in–

AI-suggested

A fix is available and has been applied in Linux kernel versions 6.18.53, 6.20, and 7.0 as well as specific commits. Users should update to these fixed versions to remediate the issue.

Description

A vulnerability in the Linux kernel's netfs subsystem caused uninitialized return values in netfs_unbuffered_write() when preparation of the first subrequest fails. This could lead to returning unrelated errors instead of the actual write error. The issue was fixed by initializing the return value properly.

References

Community reviews

Loading reviews…