Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 11 days later

    Published

  3. · 15 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (16 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 848d78e3625f15de09d34a562dc49a98b78a62f3 – < aa00eead258e4fe8158a3a3e2d65facf06274abd
    • affected 48ca7139ab7f0bbed95ff7a901ea497017769657 – < 3d67f155fe5813cfb02a551a9a12d6ea06a902e9
    • affected 56e84c64fc257a95728ee73165456b025c48d408 – < d1152c96a3002e3df6b9a5b007cecaa7b19b4f79
    • affected 56e84c64fc257a95728ee73165456b025c48d408 – < 8dc5db3a0e583ea8d31d0613cefd99e93e095c3c
    • affected 56e84c64fc257a95728ee73165456b025c48d408 – < 5f0306e731e2f46e91419eae57eee3a241c055e0
    • affected c13b779d26b3702fba8f7d5fe757aba5bda85fd0
    • affected 6.6.94 – < 6.6.160
    • affected 6.12.34 – < 6.12.112
    • affected 6.15.3 – < 6.16
  • Linux · Linux

    • affected 6.16
    • unaffected < 6.16
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.112 – ≤ 6.12.*
    • unaffected 6.18.54 – ≤ 6.18.*
    • unaffected 7.2.8 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-98168 badge
[![CVE-2026-98168](https://cveledger.app/badge/CVE-2026-98168.svg)](https://cveledger.app/cve/CVE-2026-98168)

Record last updated .