Skip to main content

Linux Kernel CVE-2026-64399

| EUVDEUVD-2026-48943 CRITICAL
2026-07-25 Linux GHSA-mrp6-592v-c3fh
9.8
CVSS 3.1 · Vendor: Linux
Share

Severity by source

Vendor (Linux) PRIMARY
9.8 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vuln.today AI
6.5 MEDIUM

Reachable over SMB but only after authentication (PR:L), no race so AC:L; impact is unauthorized data overwrite (I:H) with no disclosure (C:N) and no direct availability loss (A:N).

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
SUSE
6.5 HIGH
AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

Primary rating from Vendor (Linux).

CVSS VectorVendor: Linux

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

6
Metadata Corrected
Sep 16, 2026 - 09:40 vuln.today
tag: Information Disclosure removed
Analysis Generated
Jul 27, 2026 - 05:47 vuln.today
CVSS changed
Jul 27, 2026 - 05:22 NVD
9.8 (CRITICAL)
Patch available
Jul 25, 2026 - 11:18 EUVD
CVE Published
Jul 25, 2026 - 08:50 cve.org
UNKNOWN (no severity yet)
CVE Published
Jul 25, 2026 - 08:50 cve.org
CRITICAL 9.8

DescriptionCVE.org

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.

AnalysisAI

Improper authorization in the Linux kernel's ksmbd (in-kernel SMB3 server) lets an authenticated SMB client overwrite destination file data it should not be able to write. The FSCTL_DUPLICATE_EXTENTS_TO_FILE branch of smb2_ioctl() performs a server-side block clone via vfs_clone_file_range() but omits the share-level writable check and the per-handle access check that every other write-bearing ioctl arm enforces, so data can be overwritten on a read-only share or through a handle opened with only FILE_WRITE_ATTRIBUTES. This is an integrity/authorization bug (not memory corruption); there is no public exploit identified at time of analysis and EPSS is low (0.21%).

Technical ContextAI

ksmbd is the Linux kernel's native SMB3 file-server module (fs/smb/server). SMB clients invoke server-side operations through the SMB2 IOCTL command; the FSCTL_DUPLICATE_EXTENTS_TO_FILE code performs a reflink/copy-on-write clone of source extents into a destination file using the VFS vfs_clone_file_range() helper, which writes data into the destination. The other write-bearing FSCTL arms guard this with two gates: KSMBD_TREE_CONN_FLAG_WRITABLE (the share was mounted/exported writable) and a per-handle fp->daccess check confirming the open granted write-data rights. The duplicate-extents arm had neither, so a handle opened with only FILE_WRITE_ATTRIBUTES - which still produces an FMODE_WRITE file pointer at the VFS layer - was accepted as sufficient to clone-overwrite data. This is a classic missing-authorization / incorrect-permission-assignment root cause (CWE-284/CWE-863); the input CWE is listed as N/A. The CPE data identifies the affected component only generically as cpe:2.3:a:linux:linux, i.e. the mainline kernel tree containing the ksmbd server.

RemediationAI

Vendor-released patch: upgrade to Linux 6.1.178, 6.6.145, 6.12.96, 6.18.39, 7.1.4, or 7.2-rc1 (or your distribution's equivalent - Ubuntu users apply the kernel updates in USN-8726-1 and USN-8727-1). The fix adds the missing KSMBD_TREE_CONN_FLAG_WRITABLE and fp->daccess checks and requires FILE_WRITE_DATA on the destination handle, mirroring the earlier FSCTL_SET_SPARSE permission fix. If you cannot patch immediately, the concrete compensating control is to stop exposing ksmbd to untrusted clients: restrict share access to trusted authenticated users, or unload/disable the ksmbd module and serve SMB via user-space Samba instead (trade-off: loss of ksmbd's performance, and a service migration). Tightening network exposure of TCP/445 to trusted management networks reduces the attacker population but does not fix the authorization gap for legitimate share users.

Vendor StatusVendor

SUSE

Severity: Important
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 16.0 Affected

Share

CVE-2026-64399 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy