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-68457ksmbd: use opener credentials for FSCTL mutations

Description

In the Linux kernel, the following vulnerability has been resolved: ksmbd: use opener credentials for FSCTL mutations SET_SPARSE, SET_ZERO_DATA and SET_COMPRESSION operate on an open SMB handle but call VFS xattr, fallocate or fileattr helpers with the current ksmbd worker credentials. Those helpers can revalidate inode permissions, ownership and LSM policy independently of the SMB handle access mask. Run each operation with the credentials captured in the target file when the handle was opened. Keep credential handling local to these single-file FSCTLs rather than applying session credentials to the complete IOCTL handler, which also contains handle-less and multi-handle operations.

Timeline

  1. ID reserved

    By Linux

  2. · 16 days later

    Published

  3. · 3 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-68457, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1Critical9.1CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
NVDNVD · Received3.1Critical9.1CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
EPSS (exploitation in 30 days)
0.70% · top 46% 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 e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < a8c18434e1f0d9f7989170bdb0490c0160baf065
    • affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < 1e112c47ec5dd1942e2d4ca6e8e9b712238e20c2
    • affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < fb1cae6302d58414ddf029e3f642711bd30243f7
    • affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < e205f3e7e8c31a47cd11efb6cf663a527177e432
    • affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < cfb2c6f71d61ed807c9d7a7af331d406f1f31877
    • affected e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 – < c6394bcaf254c5baf9aff43376020be5db6d3316
  • Linux · Linux

    • affected 5.15
    • unaffected < 5.15
    • unaffected 6.1.178 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.97 – ≤ 6.12.*
    • unaffected 6.18.40 – ≤ 6.18.*
    • unaffected 7.1.5 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .