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-64381smb: client: Fix next buffer leak in receive_encrypted_standard()

Description

In the Linux kernel, the following vulnerability has been resolved: smb: client: Fix next buffer leak in receive_encrypted_standard() receive_encrypted_standard() allocates next_buffer before checking whether the number of compound PDUs already reached MAX_COMPOUND. If the limit check fails, the function returns immediately and the newly allocated next_buffer is not assigned to server->smallbuf/server->bigbuf, making it leaked. Move the MAX_COMPOUND check before allocating next_buffer.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 3 months 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

CVSS scores of CVE-2026-64381, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.13% · top 97% of all CVEs (14 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected b24df3e30cbf48255db866720fb71f14bf9d2f39 – < 94e4f672db029414b9888b5137a7559f1febf2d8
    • affected b24df3e30cbf48255db866720fb71f14bf9d2f39 – < 68fc0b6cc03ca58060c0f36454e169f5fe258974
    • affected b24df3e30cbf48255db866720fb71f14bf9d2f39 – < 07e0ab81df1790afa35732a4e8e07ff831b29008
    • affected b24df3e30cbf48255db866720fb71f14bf9d2f39 – < 9136a08dc29328edd9867f2545e73906ac9df93b
    • affected b24df3e30cbf48255db866720fb71f14bf9d2f39 – < 67097772df7791c53d608f04bd31c676ccf79b83
    • affected b24df3e30cbf48255db866720fb71f14bf9d2f39 – < 297243e365fc9fe2f8e9b7dd535a65d922cd108b
    • affected b24df3e30cbf48255db866720fb71f14bf9d2f39 – < 927d4805aea0a287d36dd4f826ee24d69a2afee3
    • affected b24df3e30cbf48255db866720fb71f14bf9d2f39 – < 1c6267a1d5cf4c73b656f8181b310cbbb3e4767b
  • Linux · Linux

    • affected 4.19
    • unaffected < 4.19
    • unaffected 5.10.261 – ≤ 5.10.*
    • unaffected 5.15.212 – ≤ 5.15.*
    • unaffected 6.1.178 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.96 – ≤ 6.12.*
    • unaffected 6.18.39 – ≤ 6.18.*
    • unaffected 7.1.4 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .