Skip to main content
VulnerabilityPublished Updated

CVE-2026-98168: Linux kernel · smb: client: fix reparse buffer bounds in cifs_query_reparse_point()

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in d1152c96a3002e3df6b9a5b007cecaa7b19b4f79 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 12:55 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS
0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in d1152c96a3002e3df6b9a5b007cecaa7b19b4f79, aa00eead258e4fe8158a3a3e2d65facf06274abd, 8dc5db3a0e583ea8d31d0613cefd99e93e095c3c +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • >=6.6.94 <6.6.160
  • >=6.12.34 <6.12.112
  • >=6.15.3 <6.16
Fixed in
  • d1152c96a3002e3df6b9a5b007cecaa7b19b4f79
  • aa00eead258e4fe8158a3a3e2d65facf06274abd
  • 8dc5db3a0e583ea8d31d0613cefd99e93e095c3c
  • 6.16
  • 6.12.112
  • 6.6.160
  • 5f0306e731e2f46e91419eae57eee3a241c055e0
  • 3d67f155fe5813cfb02a551a9a12d6ea06a902e9
LinuxLinuxAffected
  • =6.16
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: smb: client: fix reparse buffer bounds in cifs_query_reparse_point() In cifs_query_reparse_point(), the start >= end check before casting to struct reparse_data_buffer * only ensures the start pointer is within the response. It fails to verify that there is enough space remaining for the fixed 8-byte header of the structure. If a server provides a DataOffset that leaves less than 8 bytes remaining, the check passes, but subsequent reads of ReparseTag and ReparseDataLength will occur out-of-bounds. Fix this by ensuring the remaining space is at least the size of the reparse_data_buffer structure before accessing its fields.

References

Community reviews

Loading reviews…