Skip to main content
VulnerabilityPublished Updated

CVE-2026-98126: Linux kernel · smb/client: validate new EOF for zero range

Affects Linux kernelSource CVE Database V5

0

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

Data as of 26 Oct 2026, 13:07 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS
0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in f320ca20c273a26cd779bdb2b2e4b076a95c76f6, 88972e35750792e717af287dc71f42a03b5cbce4, 3673f057b64abfa957e8ae84448db69369a5091a +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
  • ≥ 72c419d9b073628d3b5b0b2fc787b724f1a8c726, < f320ca20c273a26cd779bdb2b2e4b076a95c76f6
Fixed in
  • f320ca20c273a26cd779bdb2b2e4b076a95c76f6
LinuxLinuxAffected
  • ≥ 72c419d9b073628d3b5b0b2fc787b724f1a8c726, < 88972e35750792e717af287dc71f42a03b5cbce4
Fixed in
  • 88972e35750792e717af287dc71f42a03b5cbce4
LinuxLinuxAffected
  • ≥ 72c419d9b073628d3b5b0b2fc787b724f1a8c726, < 3673f057b64abfa957e8ae84448db69369a5091a
Fixed in
  • 3673f057b64abfa957e8ae84448db69369a5091a
LinuxLinuxAffected
  • ≥ 72c419d9b073628d3b5b0b2fc787b724f1a8c726, < 06a4f9049cb6dc319bceec2dc813ba89add8b828
Fixed in
  • 06a4f9049cb6dc319bceec2dc813ba89add8b828
LinuxLinuxAffected
  • ≥ 72c419d9b073628d3b5b0b2fc787b724f1a8c726, < 5fbd8848f2e25c8163896ec52863df2305a3bb63
Fixed in
  • 5fbd8848f2e25c8163896ec52863df2305a3bb63
LinuxLinuxAffected
  • =5.1
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: smb/client: validate new EOF for zero range When FALLOC_FL_ZERO_RANGE is used without FALLOC_FL_KEEP_SIZE, smb3_zero_range() may extend EOF without checking RLIMIT_FSIZE, allowing the file to grow beyond the caller's file-size limit. Fix this by calling inode_newsize_ok() before sending the zero-range request when the operation would extend EOF. Reproducer, using a file on a CIFS mount: bash -c ' FILE=/mnt/cifs/repro trap "" SIGXFSZ ulimit -f 3072 truncate -s 2M "$FILE" fallocate --zero-range -o 0 -l 4M "$FILE" echo "fallocate rc=$?" stat -c "file size=%s" "$FILE" ' Before this change, the operation succeeds despite the 3 MiB limit: fallocate rc=0 file size=4194304 After this change, fallocate fails and leaves the file at 2 MiB.

References

Community reviews

Loading reviews…