CVE-2026-98124

smb/client: invalidate fscache for fallocate range operations

Description

In the Linux kernel, the following vulnerability has been resolved: smb/client: invalidate fscache for fallocate range operations smb3_zero_range(), smb3_punch_hole(), smb3_insert_range(), and smb3_collapse_range() modify file contents through server-side range operations. These operations discard the affected page cache, but leave the FS-Cache cookie valid, so a later read may return data cached before the range operation. Fix this by invalidating FS-Cache after outstanding I/O has completed and before modifying the file on the server. Run the following as root on a CIFS mount with fsc enabled and an active CacheFiles backend: bash -c ' MNT=/mnt/cifs FILE="$MNT/repro" # Generate four 1 MiB random blocks: [A][B][C][D]. dd if=/dev/urandom of=/tmp/src bs=1M count=4 status=none # Expected contents after zeroing B: [A][zero][C][D]. cp /tmp/src /tmp/expected dd if=/dev/zero of=/tmp/expected bs=1M seek=1 count=1 \ conv=notrunc status=none cp /tmp/src "$FILE" # Populate FS-Cache, then discard the page cache. sync echo 1 > /proc/sys/vm/drop_caches cat "$FILE" > /dev/null sync echo 1 > /proc/sys/vm/drop_caches fallocate --zero-range -o 1M -l 1M "$FILE" if cmp -s /tmp/expected "$FILE"; then echo "readback: OK" else echo "readback: STALE DATA" fi ' Before this change, the readback differs from /tmp/expected: readback: STALE DATA After this change, it matches: readback: OK

Key facts

Published
25 Sep 2026
Last changed
21 Oct 2026
Assigned by
Linux
EPSS
0.186% likely to be exploited in the next 30 days, higher than 8.283% 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
  • 31742c5a331766bc7df6b0d525df00c6cd20d5a6 up to but excluding cc7202a51b8777a757bda9dcfbf339f828c6a130 (affected)
  • 31742c5a331766bc7df6b0d525df00c6cd20d5a6 up to but excluding dd8b1e808f5c19479e6ed47e2f88a1fd46f8b0e5 (affected)
  • 31742c5a331766bc7df6b0d525df00c6cd20d5a6 up to but excluding 93c6e5a8d7c5071d586c1411596d5db5faad22b2 (affected)
  • 31742c5a331766bc7df6b0d525df00c6cd20d5a6 up to but excluding 448ba0ae65ca61064183564d2983c9aa59bd6ba7 (affected)
LinuxLinux
  • Default status: affected
  • 3.17 (affected)
  • 0 up to but excluding 3.17 (unaffected)
  • 6.6.160 up to and including 6.6.* (unaffected)
  • 6.12.114 up to and including 6.12.* (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