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-64257smb: client: reject overlapping data areas in SMB2 responses

Description

In the Linux kernel, the following vulnerability has been resolved: smb: client: reject overlapping data areas in SMB2 responses Commit 53b7c271f06b ("smb: client: restrict implied bcc[0] exemption to responses without data area") restricted the implied bcc[0] length exception to responses without a data area. However, the overlap handling in __smb2_calc_size() clears data_length, which can make an invalid response appear to have no data area and so qualify for the exception. Track data area overlap separately and reject such responses before applying the length compatibility exceptions.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

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

CVSS scores of CVE-2026-64257, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1Critical9.1CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
NVDNVD · Analyzed3.1Critical9.1CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
EPSS (exploitation in 30 days)
0.66% · top 48% of all CVEs (17 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 31c6312608c60b72a1feb99a5afb680645a3e8a3 – < 445ece263131780dee273d727a4d6f11934feec7
    • affected 573e502d14714d2947e22e7eff40ec20a6a44a42 – < 36bfa52459e45c0d5b668de2f1c91f6dc5c67775
    • affected 419ec1b604d7fb60c10aec2dc062371f9fcd4940 – < 4a9d2657d3e05f6ed09c148cb127b4e58702275f
    • affected ceb875a375dedbf51c9425c1d13a2d7a8435c08c – < fdafa1e68dc75045b7b617e6e7d2854950804d83
    • affected 6e9d10f62773b99bd927940fd9cbdfe7207e23ff – < 57cba95f0e97c6f6e45e6731da30aff091bd7460
    • affected 53b7c271f06be4dd5cfc8c6ef552a8355c891a7f – < 8986c932905ea508d66da421eb2eb6e676ace1fe
    • affected 8d0bbc78046d264bbf6a574ea6f9072258a43e35
    • affected b6a381c01e2ac98a48e32ac0f2a45bbadd9e26b0
    • affected 5.10.261 – < 5.11
    • affected 5.15.212 – < 5.16
  • Linux · Linux

    All versions: unaffected

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .