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-68130ksmbd: defer destroy_previous_session() until after NTLM authentication

Description

In the Linux kernel, the following vulnerability has been resolved: ksmbd: defer destroy_previous_session() until after NTLM authentication In ntlm_authenticate(), destroy_previous_session() is called using a user pointer resolved from the client-supplied NTLM blob username field before the NTLMv2 response is validated. An authenticated attacker can set the NTLM blob username to match a victim account and set PreviousSessionId to the victim's session ID; destroy_previous_session() destroys the victim's session while ksmbd_decode_ntlmssp_auth_blob() subsequently rejects the request with -EPERM. Move destroy_previous_session() and the prev_id assignment to after ksmbd_decode_ntlmssp_auth_blob() returns success and use sess->user rather than the pre-authentication lookup result. This matches the ordering already used by krb5_authenticate(), where destroy_previous_session() is called only after ksmbd_krb5_authenticate() returns success.

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 88% 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 e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < ab0230257ebdf48b07eaa679a8c92bc842fe3498
    • affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < 370b0ec8822b69c9073265e16b7daaa8201c9a4f
    • affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < 5c833074b549e5db125436a6f681af682261f785
    • affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < 243f1614ef2aca2d62a744575f1c24b07cd42757
    • affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < 18705cace0619fd2123737dcd028147774f38181
    • affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < 0ff12308c8a6c16ab68f0a487ffa93d69001dc18
    • affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < c74801ee524f477c174a1899782b6c3b6918d407
  • Linux · Linux

    • affected 5.15
    • unaffected < 5.15
    • unaffected 5.15.217 – ≤ 5.15.*
    • unaffected 6.1.183 – ≤ 6.1.*
    • unaffected 6.6.148 – ≤ 6.6.*
    • unaffected 6.12.101 – ≤ 6.12.*
    • unaffected 6.18.42 – ≤ 6.18.*
    • unaffected 7.1.6 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References7

Sources

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

Badge for a README or a ticket

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

Record last updated .