CVE-2026-98169
What it is
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.
At a glance
- Exploitability
- Can be exploited over the network without logging in, but needs a user to act. High risk of service disruption.
- Exploit odds
- 0.4% chance of exploitation in the next 30 days (EPSS).
- Fix
- No patch or advisory is linked yet. Look at mitigations or restrict exposure.
Timeline
- ReservedThe CVE id was reserved by its CNA
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.4% in the next 30 days (EPSS).
- Severity: 7.1 HIGH (CVSS).
- Fix: none linked yet, which raises it.
Details
- Published
- Last modified
- Exploit probability
- 0.4% · EPSS, next 30 days
- Record status
- Received
Attack profile CVSS 3.1 · 7.1
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-98169.md and follow it. Check whether this project is affected by CVE-2026-98169. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
References
- https://git.kernel.org/stable/c/15a221c734b9d044ab769e7e3606b2cab96fb65a
- https://git.kernel.org/stable/c/1cdf0d304d820fb13bf0faf532c3459600f9ea43
- https://git.kernel.org/stable/c/210f0f1f67817e7d2348b86b5115a9b85ef5c98b
- https://git.kernel.org/stable/c/4775c3b7a597907e0b97556c7986fda238a377ae
- https://git.kernel.org/stable/c/5edf5b398d49b881c0df79d6e4f6df251236c533
- https://git.kernel.org/stable/c/67ef1d6da00f4f39eb5fcebe7a44fe494b645059
- https://git.kernel.org/stable/c/74995ee8305a7c4d76ee70d6acd996a75eda3c03
- https://git.kernel.org/stable/c/dbe452a905dfe2804647530a9ff3d7e3826ed04d