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-31612ksmbd: validate EaNameLength in smb2_get_ea()

Description

In the Linux kernel, the following vulnerability has been resolved: ksmbd: validate EaNameLength in smb2_get_ea() smb2_get_ea() reads ea_req->EaNameLength from the client request and passes it directly to strncmp() as the comparison length without verifying that the length of the name really is the size of the input buffer received. Fix this up by properly checking the size of the name based on the value received and the overall size of the request, to prevent a later strncmp() call to use the length as a "trusted" size of the buffer. Without this check, uninitialized heap values might be slowly leaked to the client.

Timeline

  1. ID reserved

    By Linux

  2. · 46 days later

    Published

  3. · 6 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-31612, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NVDNVD · Modified3.1High7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS (exploitation in 30 days)
0.43% · top 62% of all CVEs (19 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < 859f11e1bc81a4d32bb3ceeae54bcd296ac675d3
    • affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < 4b73376feecb3b61172fe5b4ff42bbbb8531669d
    • affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < 551dfb15b182abad4600eaf7b37e6eb7000d5b1b
    • affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < 3363a770b193f555f29d76ddf4ced3305c0ccf6d
    • affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < 243b206bcb5a7137e8bddd57b2eec81e1ebd3859
    • affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < dfc6878d14acafffbe670bf2576620757a10a3d8
    • affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < 66751841212c2cc196577453c37f7774ff363f02
  • Linux · Linux

    • affected 5.15
    • unaffected < 5.15
    • unaffected 6.1.175 – ≤ 6.1.*
    • unaffected 6.6.136 – ≤ 6.6.*
    • unaffected 6.12.83 – ≤ 6.12.*
    • unaffected 6.18.24 – ≤ 6.18.*
    • unaffected 6.19.14 – ≤ 6.19.*
    • unaffected 7.0.1 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .