CVE-2026-64384
Description
A flaw was found in the Linux kernel's Server Message Block (SMB) client. This vulnerability occurs due to a double-free error when handling change notify replies. If a response attempt returns a replayable error and frees its buffer, and then SMB2_notify_init() fails, the same buffer can be freed again. This can lead to memory corruption and potentially a denial of service.
Statement
This vulnerability is rated as having Moderate severity for Red Hat Enterprise Linux because exploitation requires an established CIFS or SMB mount interacting with a malicious or faulty server under specific replay error conditions. Under standard deployments, systems that do not mount remote SMB shares or request directory change notifications are not exposed to this flaw. In the worst case, local denial of service through kernel crash or potential privilege escalation could occur if memory corruption is induced via a compromised remote file share.
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).
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 7 | N/A | 9.8 |
| Attack Vector | Local | N/A | Network |
| Attack Complexity | High | N/A | Low |
| Privileges Required | Low | N/A | None |
| 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:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Understanding the Weakness (CWE)
Availability,Integrity
Technical Impact: DoS: Crash, Exit, or Restart
Integrity
Technical Impact: Modify Memory; Modify Application Data
Depending on the type of resource and the expected API behavior, this could lead to memory corruption, data corruption, or execution path corruption.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.