Skip to main content
VulnerabilityPublished Updated

CVE-2026-98169: Linux kernel · smb: client: fix potential OOB read in smb3_enum_snapshots()

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-98169· High 7.1

Not known to be exploited · CVSS 7.1 High · fixed in dbe452a905dfe2804647530a9ff3d7e3826ed04d : patch Linux kernel soon.

Data as of 30 Oct 2026, 16:33 UTC

CVSS 3.1 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Linux)CVSS 3.17.1
Patch
Available – fixed in dbe452a905dfe2804647530a9ff3d7e3826ed04d, 74995ee8305a7c4d76ee70d6acd996a75eda3c03, 4775c3b7a597907e0b97556c7986fda238a377ae +8
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • >=4.9.125 <4.10
  • >=4.14.68 <4.15
  • >=4.18.6 <4.19
Fixed in
  • dbe452a905dfe2804647530a9ff3d7e3826ed04d
  • 74995ee8305a7c4d76ee70d6acd996a75eda3c03
  • 4775c3b7a597907e0b97556c7986fda238a377ae
  • 210f0f1f67817e7d2348b86b5115a9b85ef5c98b
  • 67ef1d6da00f4f39eb5fcebe7a44fe494b645059
  • 15a221c734b9d044ab769e7e3606b2cab96fb65a
  • 5edf5b398d49b881c0df79d6e4f6df251236c533
  • 4.19
  • 4.15
  • 4.10
  • 1cdf0d304d820fb13bf0faf532c3459600f9ea43
LinuxLinuxAffected
  • =4.19
Fixed in–

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.

References

Community reviews

Loading reviews…