CVE-2026-64396
Description
A flaw was found in ksmbd, a component of the Linux kernel. A local attacker could exploit a use-after-free vulnerability in the SMB2_LOCK deferred-lock cancellation mechanism. This flaw occurs when a file lock is freed prematurely while still being referenced, potentially leading to a system crash (denial of service) or arbitrary code execution.
Statement
An Important severity use-after-free flaw was found in the Linux kernel's ksmbd SMB server subsystem, in the SMB2_LOCK deferred-lock cancellation path. When a blocking byte-range lock request is deferred (FILE_LOCK_DEFERRED), ksmbd registers asynchronous work on the connection's async_requests list. If the lock waiter is woken while a concurrent cancellation is in progress, the cleanup path frees the file lock (struct file_lock) without first dequeuing the work, and the cancel callback smb2_remove_blocked_lock() can then dereference the already-freed lock, resulting in a slab-use-after-free. A remote attacker with an authenticated SMB session (low privileges) could race SMB2 lock and cancellation requests to trigger this flaw, causing a kernel crash (denial of service) or potentially arbitrary code execution. Red Hat rates this flaw with a CVSS 3.1 score of 7.5 (AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H), lower than the upstream CVEORG score of 8.8 (AC:L), because successful exploitation requires winning a race between the deferred lock wake-up and a concurrent cancellation, making reliable exploitation, particularly for code execution, difficult. No Red Hat products are affected by this flaw: the vulnerable code is not present in the shipped kernel and kernel-rt packages of Red Hat Enterprise Linux or Red Hat In-Vehicle OS.
Mitigation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 7.5 | N/A | 8.8 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | High | N/A | Low |
| Privileges Required | Low | N/A | Low |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | High | N/A | High |
| Integrity Impact | High | N/A | High |
| Availability Impact | High | N/A | High |
Vector
Red Hat: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
cve.org: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Understanding the Weakness (CWE)
Confidentiality
Technical Impact: Read Memory
If the expired pointer is used in a read operation, an attacker might be able to control data read in by the application.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
If the expired pointer references a memory location that is not accessible to the product, or points to a location that is "malformed" (such as NULL) or larger than expected by a read or write operation, then a crash may occur.
Integrity,Confidentiality,Availability
Technical Impact: Execute Unauthorized Code or Commands
If the expired pointer is used in a function call, or points to unexpected data in a write operation, then code execution may be possible.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.