Skip to main content
VulnerabilityPublished Updated

CVE-2026-98127: Linux kernel · smb/client: validate new EOF for insert range

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in f8cbfe3a3fcee7d991fd223f660f3e5df13221cf : 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 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in f8cbfe3a3fcee7d991fd223f660f3e5df13221cf, bc7602b9082ef195d913c4c16fa9853dd262333e, b7f2e33d9f5db7b8e6e5e0a5a93d0c5e31870356 +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
  • ≥ 7fe6fe95b936084dce6eedcc2cccadf96eafae73, < f8cbfe3a3fcee7d991fd223f660f3e5df13221cf
Fixed in
  • f8cbfe3a3fcee7d991fd223f660f3e5df13221cf
LinuxLinuxAffected
  • ≥ 7fe6fe95b936084dce6eedcc2cccadf96eafae73, < bc7602b9082ef195d913c4c16fa9853dd262333e
Fixed in
  • bc7602b9082ef195d913c4c16fa9853dd262333e
LinuxLinuxAffected
  • ≥ 7fe6fe95b936084dce6eedcc2cccadf96eafae73, < b7f2e33d9f5db7b8e6e5e0a5a93d0c5e31870356
Fixed in
  • b7f2e33d9f5db7b8e6e5e0a5a93d0c5e31870356
LinuxLinuxAffected
  • ≥ 7fe6fe95b936084dce6eedcc2cccadf96eafae73, < 1519dc88c87f5346dae0464d7d6da1b6bf1f6e8e
Fixed in
  • 1519dc88c87f5346dae0464d7d6da1b6bf1f6e8e
LinuxLinuxAffected
  • ≥ 7fe6fe95b936084dce6eedcc2cccadf96eafae73, < 7c2c69045aa76ccaa7f16f1478eb312130ce4951
Fixed in
  • 7c2c69045aa76ccaa7f16f1478eb312130ce4951
LinuxLinuxAffected
  • =5.13
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: smb/client: validate new EOF for insert range smb3_insert_range() does not check if the new file size (i_size + len) is valid. This allows FALLOC_FL_INSERT_RANGE to bypass RLIMIT_FSIZE, exceed s_maxbytes, or produce a size outside the loff_t range. Use check_add_overflow() to calculate the new EOF. Validate it with inode_newsize_ok() before modifying the file. Reproducer, using a file on a CIFS mount: bash -c ' FILE=/mnt/cifs/repro trap "" SIGXFSZ ulimit -f 3072 # RLIMIT_FSIZE = 3 MiB # A regular write is stopped at 3 MiB. dd if=/dev/zero of="$FILE" bs=1M count=4 status=none stat -c "size after write: %s" "$FILE" # Insert 2 MiB into a 2 MiB file. truncate -s 2M "$FILE" fallocate -i -o 0 -l 2M "$FILE" stat -c "size after insert: %s" "$FILE" ' Before this change, the regular write stops at the 3 MiB limit, but insert range grows the file to 4 MiB: dd: error writing '/mnt/cifs/repro': File too large size after write: 3145728 size after insert: 4194304 After this change, insert range also fails at the limit and leaves the 2 MiB file unchanged: dd: error writing '/mnt/cifs/repro': File too large size after write: 3145728 fallocate: fallocate failed: File too large size after insert: 2097152

References

Community reviews

Loading reviews…