Skip to content
Fencer Intel
medium 5.5

CVE-2026-98125 json

smb/client: fix stale page cache in insert/collapse range

published last mo. modified 20d ago also EUVD-2026-86956

cvss
5.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.1%
EPSS 0.1% chance of exploitation in 30 days, percentile 1%
public exploits
0
none known

Summary

In the Linux kernel, the following vulnerability has been resolved:

smb/client: fix stale page cache in insert/collapse range

smb3_insert_range() and smb3_collapse_range() use truncate_pagecache_range() to invalidate the affected page cache. However, if off or old_eof is not page-aligned, the boundary pages are only partially zeroed and remain uptodate. As a result, the client may return stale data after a successful insert/collapse range operation.

For example, with 4K pages:

page 0 page 1 page 2 0------4K 4K------8K 8K------12K ^ ^ off=2K old_eof=10K

Page 1 is removed from the page cache, while the boundary pages are only partially zeroed. After COPYCHUNK moves the data on the server, these cached pages may still return stale data.

This can be reproduced on a CIFS mount:

bash -c ' FILE=/mnt/scratch/repro

# Use a 6 KiB file so EOF is not page-aligned. dd if=/dev/urandom of=/tmp/src bs=1K count=6 status=none

# Expected: a 4 KiB hole followed by the original data. rm -f /tmp/expected truncate -s 4K /tmp/expected cat /tmp/src >> /tmp/expected

cp /tmp/src "$FILE"

# Prime the page cache before moving data on the server. cat "$FILE" > /dev/null

fallocate --insert-range -o 0 -l 4K "$FILE"

if cmp -s /tmp/expected "$FILE"; then echo "readback: OK" else echo "readback: STALE DATA" fi '

Fix this by writing back dirty data and discarding the page cache from the start of the page containing off to EOF before moving data on the server.

Patch / fix

  • Linux Linux 5.20, 6.6.160, 7.2.7, 7.3
  • linux Debian 14 7.2.7-1

debian advisories DEBIAN-CVE-2026-98125

  • linux Ubuntu 26.04 LTS 7.0.0-42.42
  • linux-aws Ubuntu 26.04 LTS 7.0.0-1016.17
  • linux-gcp Ubuntu 26.04 LTS 7.0.0-1016.18
  • linux-ibm Ubuntu 26.04 LTS 7.0.0-1017.17
  • linux-riscv Ubuntu 26.04 LTS 7.0.0-42.42.1
  • linux-oracle Ubuntu 26.04 LTS 7.0.0-1015.16
  • linux-hwe-7.0 Ubuntu 24.04 LTS 7.0.0-42.42~24.04.1
  • linux-oem-7.0 Ubuntu 26.04 LTS 7.0.0-1017.17

ubuntu advisories UBUNTU-CVE-2026-98125

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • kernel-source Linux Micro 6.0 6.4.0-159998.55.1
  • kernel-default Linux Micro 6.0 6.4.0-159998.55.1
  • kernel-kvmsmall Linux Micro 6.0 6.4.0-159998.55.1
  • kernel-default-base Linux Micro 6.0 6.4.0-159998.55.1.159998.21.42
  • kernel-rt Linux Micro 6.2 6.12.0-160000.40.1
  • kernel-64kb SLES 16.0, Linux Micro 6.2, SLES for SAP applications 16.0 6.12.0-160000.40.1
  • kernel-source SLES 16.0, Linux Micro 6.2, SLES for SAP applications 16.0 6.12.0-160000.40.1
  • kernel-default SLES 16.0, SLE High Availability Extension 16.0, Linux Micro 6.2 +1 more 6.12.0-160000.40.1

suse advisories SUSE-SU-2026:24550-1SUSE-SU-2026:24422-1SUSE-SU-2026:24446-1SUSE-SU-2026:24437-1SUSE-SU-2026:24386-1

  • kernel-rt openSUSE Leap 16.0 6.12.0-160000.40.1
  • dtb-aarch64 openSUSE Leap 16.0 6.12.0-160000.40.1
  • kernel-64kb openSUSE Leap 16.0 6.12.0-160000.40.1
  • kernel-syms openSUSE Leap 16.0 6.12.0-160000.40.1
  • kernel-azure openSUSE Leap 16.0 6.12.0-160000.40.1
  • kernel-obs-qa openSUSE Leap 16.0 6.12.0-160000.40.1
  • kernel-source openSUSE Leap 16.0 6.12.0-160000.40.1
  • kernel-default openSUSE Leap 16.0 6.12.0-160000.40.1

opensuse advisories openSUSE-SU-2026:22167-1openSUSE-SU-2026:12074-1

  • kernel Azure Linux 3.0 6.6.161.1-1

azure linux advisories AZL-104277

Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT

Is CVE-2026-98125 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-98125 updated cvss 5.5

kernel: smb/client: fix stale page cache in insert/collapse range

  • Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +82 more Red Hat Enterprise Linux 10 kernel Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-9 Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9
    affected: workaround, no fix available “Fix deferred”
  • Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 kernel-rt, kernel-rt-selftests-internal Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.12% chance of exploitation in the next 30 days, higher than 1% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Affected products

  • Linux Linux

Classification

Weakness
  • CWE-669 Incorrect Resource Transfer Between Spheres
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.