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.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - 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. (CVE-2026-98125)

Note that Nessus relies on the presence of the package as reported by the vendor.

ID	Name	Product	Family	Type	Severity
376443	Ubuntu 24.04 LTS / 26.04 LTS : Linux kernel vulnerabilities (USN-8959-1)	Nessus	Ubuntu Local Security Checks	Local	high
374174	SUSE SLES16 Security Update : kernel (SUSE-SU-2026:24437-1)	Nessus	SuSE Local Security Checks	Local	high
374162	SUSE SLES16: cluster-md-kmp-default / dlm-kmp-default / gfs2-kmp-default / etc (SUSE-SU-2026:24446-1)	Nessus	SuSE Local Security Checks	Local	high
372022	openSUSE 16: cluster-md-kmp-64kb / cluster-md-kmp-azure / cluster-md-kmp-default / etc (openSUSE-SU-2026:22167-1)	Nessus	SuSE Local Security Checks	Local	high
350358	Linux Distros Unpatched Vulnerability : CVE-2026-98125	Nessus	Misc.	Local	medium

Detections

Analytics

CVE-2026-98125

medium

Tenable Plugins

high

high

high

high

medium