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-99114ksmbd: initialize FileSystemControlFlags in FS_CONTROL_INFORMATION

Description

In the Linux kernel, the following vulnerability has been resolved: ksmbd: initialize FileSystemControlFlags in FS_CONTROL_INFORMATION smb2_get_info_filesystem() reports 48 bytes for FS_CONTROL_INFORMATION, that is the whole of struct smb2_fs_control_info, but never assigns FileSystemControlFlags. Those four bytes go to the client as they are found in the response buffer. The buffer is zeroed on allocation, so a standalone request leaks nothing. A compound request can leak: the offset of the next response is advanced by the length pinned for the previous one, so a reply that was written into the buffer and then dropped in favour of the short error response of smb2_set_err_rsp() stays there, and the next reply is laid over it with only the header cleared. ksmbd does not implement quota tracking, so report no control flags.

Timeline

  1. ID reserved

    By Linux

  2. · 33 days later

    Published

  3. · 2 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.17% · top 93% of all CVEs (13 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 – < 995456b5e703e128904a6cbc8b3347eb3d04c72c
    • affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < c78aea8984c84767e87f677477e4784deb8adfde
    • affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < e8b82184a1982894820a91a72ac9857ddd5dffbf
    • affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < 370459776468fc68c97008360108f381e3120953
    • affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < d8c450ad0d08980b39b08d435efa921086c8b227
    • affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < 03bb4338c3a7c3fc4decf699a35753f0891aab2a
    • affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < c0cd3fc6824122014da2b3b0cb7ddeaa2946ec8e
  • Linux · Linux

    • affected 5.15
    • unaffected < 5.15
    • unaffected 5.15.224 – ≤ 5.15.*
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.161 – ≤ 6.6.*
    • unaffected 6.12.115 – ≤ 6.12.*
    • unaffected 6.18.59 – ≤ 6.18.*
    • unaffected 7.2.13 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References7

Sources

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

Badge for a README or a ticket

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

Record last updated .