CVE-2026-98127

smb/client: validate new EOF for insert range

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

Key facts

Published
25 Sep 2026
Last changed
21 Oct 2026
Assigned by
Linux
EPSS
0.13% likely to be exploited in the next 30 days, higher than 2.713% of CVEs (scores for 17 Nov 2026)

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • 7fe6fe95b936084dce6eedcc2cccadf96eafae73 up to but excluding b7f2e33d9f5db7b8e6e5e0a5a93d0c5e31870356 (affected)
  • 7fe6fe95b936084dce6eedcc2cccadf96eafae73 up to but excluding 7c2c69045aa76ccaa7f16f1478eb312130ce4951 (affected)
  • 7fe6fe95b936084dce6eedcc2cccadf96eafae73 up to but excluding bc7602b9082ef195d913c4c16fa9853dd262333e (affected)
  • 7fe6fe95b936084dce6eedcc2cccadf96eafae73 up to but excluding f8cbfe3a3fcee7d991fd223f660f3e5df13221cf (affected)
  • 7fe6fe95b936084dce6eedcc2cccadf96eafae73 up to but excluding 1519dc88c87f5346dae0464d7d6da1b6bf1f6e8e (affected)
LinuxLinux
  • Default status: affected
  • 5.13 (affected)
  • 0 up to but excluding 5.13 (unaffected)
  • 6.6.160 up to and including 6.6.* (unaffected)
  • 6.12.111 up to and including 6.12.* (unaffected)
  • 6.18.53 up to and including 6.18.* (unaffected)
  • 7.2.7 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 25 Sep 2026 Published

References