CVE-2026-98169

HIGHCVSS 7.1/10EPSS 0.21%

Last modified

CVE-2026-98169 is a high-severity vulnerability rated 7.1/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: smb: client: fix potential OOB read in smb3_enum_snapshots() If snapshot_array_size is smaller than GMT_TOKEN_SIZE, smb3_enum_snapshots() sets ret_data_len to sizeof(struct smb_snapshot_array) without verifying the actual length of the server's reply. Because SMB2_ioctl() places no lower bound on the server-supplied OutputCount and allocates retbuf to exactly that length, a short reply results in ret_data_len exceeding the size of retbuf. The subsequent copy_to_user() then reads past the end of retbuf, leaking adjacent slab memory to userspace. EPSS estimates a 0.21% chance of exploitation in the next 30 days.

Description

In the Linux kernel, the following vulnerability has been resolved: smb: client: fix potential OOB read in smb3_enum_snapshots() If snapshot_array_size is smaller than GMT_TOKEN_SIZE, smb3_enum_snapshots() sets ret_data_len to sizeof(struct smb_snapshot_array) without verifying the actual length of the server's reply. Because SMB2_ioctl() places no lower bound on the server-supplied OutputCount and allocates retbuf to exactly that length, a short reply results in ret_data_len exceeding the size of retbuf. The subsequent copy_to_user() then reads past the end of retbuf, leaking adjacent slab memory to userspace. The subsequent clamp check is ineffective as it only reduces ret_data_len. Fix this by rejecting replies shorter than sizeof(struct smb_snapshot_array) with -EIO. Note that the bound is set to the 12-byte struct size rather than the 16-byte MIN_SNAPSHOT_ARRAY_SIZE defined in MS-SMB2 3.3.5.15.1, because 12 bytes is exactly what copy_to_user() attempts to read.

Metrics

EPSS Probability
0.21%

10.8th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= e02789a53d71334b067ad72eee5d4e88a0158083, < 15a221c734b9d044ab769e7e3606b2cab96fb65a; >= e02789a53d71334b067ad72eee5d4e88a0158083, < 74995ee8305a7c4d76ee70d6acd996a75eda3c03; >= e02789a53d71334b067ad72eee5d4e88a0158083, < 210f0f1f67817e7d2348b86b5115a9b85ef5c98b; >= e02789a53d71334b067ad72eee5d4e88a0158083, < 1cdf0d304d820fb13bf0faf532c3459600f9ea43; >= e02789a53d71334b067ad72eee5d4e88a0158083, < dbe452a905dfe2804647530a9ff3d7e3826ed04d; >= e02789a53d71334b067ad72eee5d4e88a0158083, < 4775c3b7a597907e0b97556c7986fda238a377ae; a94703ff8e3647f8a9a3a92a468450299a7b77e9; 82a856f527334ffd69aae26e7dd9e03b19c4a520; 25b981bfe192fd208ba04c81f4aa30ffb5141660; >= 4.9.125, < 4.10; >= 4.14.68, < 4.15; >= 4.18.6, < 4.19
LinuxLinux4.19

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-98169?
In the Linux kernel, the following vulnerability has been resolved: smb: client: fix potential OOB read in smb3_enum_snapshots() If snapshot_array_size is smaller than GMT_TOKEN_SIZE, smb3_enum_snapshots() sets ret_data_len to sizeof(struct smb_snapshot_array) without verifying the actual length of the server's reply. Because SMB2_ioctl() places no lower bound on the server-supplied OutputCount and allocates retbuf to exactly that length, a short reply results in ret_data_len exceeding the size of retbuf. The subsequent copy_to_user() then reads past the end of retbuf, leaking adjacent slab memory to userspace. The subsequent clamp check is ineffective as it only reduces ret_data_len. Fix this by rejecting replies shorter than sizeof(struct smb_snapshot_array) with -EIO. Note that the bound is set to the 12-byte struct size rather than the 16-byte MIN_SNAPSHOT_ARRAY_SIZE defined in MS-SMB2 3.3.5.15.1, because 12 bytes is exactly what copy_to_user() attempts to read.
How severe is CVE-2026-98169?
CVE-2026-98169 has a CVSS score of 7.1/10 (HIGH severity). The EPSS model estimates a 0.21% probability of exploitation in the next 30 days.
How do I fix CVE-2026-98169?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-98169?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST