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-64399ksmbd: add permission checks for FSCTL_DUPLICATE_EXTENTS_TO_FILE

Description

In the Linux kernel, the following vulnerability has been resolved: ksmbd: add permission checks for FSCTL_DUPLICATE_EXTENTS_TO_FILE The FSCTL_DUPLICATE_EXTENTS_TO_FILE arm of smb2_ioctl() overwrites the destination file's data via vfs_clone_file_range() with neither the share-level KSMBD_TREE_CONN_FLAG_WRITABLE check nor a per-handle fp->daccess check that the other write-bearing arms carry. A client can overwrite destination data on a read-only share, or from a handle opened with only FILE_WRITE_ATTRIBUTES (which still yields an FMODE_WRITE filp). FILE_WRITE_ATTRIBUTES-only destination handle overwrote the file's data via the clone. Add both checks, matching the FSCTL_SET_SPARSE permission fix; require FILE_WRITE_DATA since this writes data.

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-64399, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Analyzed3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.49% · top 57% of all CVEs (18 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.8.

Affected products

  • Linux · Linux

    • affected eb817368f50c1cbe1bd07044124aad7db6330e3a – < bf460ad5958d506492de4524a656439da3f99c51
    • affected eb817368f50c1cbe1bd07044124aad7db6330e3a – < 620d133d469295ee7c017ca6aafac335f65c4a5a
    • affected eb817368f50c1cbe1bd07044124aad7db6330e3a – < 9b9cf7e65cbeaae1b6636144bacee611cdd7a5d6
    • affected eb817368f50c1cbe1bd07044124aad7db6330e3a – < baae7b39673ec21073a25e3d14f8feaada01d5df
    • affected eb817368f50c1cbe1bd07044124aad7db6330e3a – < c917e4522d251071dde9871b9142d8ea1186ebfe
    • affected eb817368f50c1cbe1bd07044124aad7db6330e3a – < 388e4139db27a9e3612c9d356b826f5b1ff6a9e3
  • Linux · Linux

    • affected 5.15
    • unaffected < 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

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .