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-98167smb: client: fix server->total_read for compound encrypted PDUs

Description

In the Linux kernel, the following vulnerability has been resolved: smb: client: fix server->total_read for compound encrypted PDUs In receive_encrypted_standard(), server->total_read is left at the full decrypted frame size when walking sub-PDUs of a compound encrypted frame. As a result, cifs_handle_standard() passes this full size to smb2_check_message(), causing the PDU length guards to incorrectly validate the entire compound frame instead of the current sub-PDU. This allows truncated non-last sub-PDUs to bypass length validation, leading to out-of-bounds reads in smb2_get_data_area_len(). Fix this by setting server->total_read to the true length of the current sub-PDU: next_cmd for non-last sub-PDUs, and the remaining pdu_length for the last one.

Timeline

  1. ID reserved

    By Linux

  2. · 11 days later

    Published

  3. · 13 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.22% · top 87% of all CVEs (15 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 b24df3e30cbf48255db866720fb71f14bf9d2f39 – < 8703539d22fdbc13dd2db090ee199c3a427b8ea0
    • affected b24df3e30cbf48255db866720fb71f14bf9d2f39 – < e78fc1d240b27349b45a0f1c3e3c2c401d7e230d
    • affected b24df3e30cbf48255db866720fb71f14bf9d2f39 – < a46eb242e9eef3a3897d166748b23303c516e870
    • affected b24df3e30cbf48255db866720fb71f14bf9d2f39 – < ebb8a075fdc7af3d196a4f158a0e18dbc394c0e3
    • affected b24df3e30cbf48255db866720fb71f14bf9d2f39 – < 282b72f9a7ef31296c48366db4128882999cc048
    • affected b24df3e30cbf48255db866720fb71f14bf9d2f39 – < f73726b83e4756fdaa099e1bc1143293bd57ad79
  • Linux · Linux

    • affected 4.19
    • unaffected < 4.19
    • unaffected 6.1.189 – ≤ 6.1.*
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.112 – ≤ 6.12.*
    • unaffected 6.18.54 – ≤ 6.18.*
    • unaffected 7.2.8 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .