CVE-2026-90171
Description
A flaw was found in the SMB Direct (smbdirect) component of the Linux kernel. This vulnerability arises from an improper handling of child sockets during the shutdown process, where memory is released prematurely while still in use. A remote attacker could potentially exploit this timing issue to trigger a use-after-free condition. This could lead to system instability, crashes, or a denial of service.
Statement
A moderate-impact use-after-free flaw was found in the Linux kernel's ksmbd SMB Direct (RDMA) transport. During SMB Direct listener shutdown, smbdirect_socket_destroy() releases the listener's pending and ready child sockets while still holding the listener's handler lock and before the listener's own rdma_destroy_id() completes. Releasing a child socket drops its last reference and destroys its cm_id, which allows _cma_cancel_listens(), invoked from the listener's _destroy_id(), to traverse an already-freed child id_priv; KASAN confirmed this as a slab use-after-free during listener shutdown. A remote system with access to the RDMA fabric can supply the pending child connection needed to set up this teardown ordering, but the demonstrated trigger path also requires an administrative action on the local host to stop the ksmbd listener, so successful exploitation results in a kernel crash and denial of service, with no impact on confidentiality or integrity. Red Hat therefore rated this flaw Moderate with a local attack vector (CVSS 3.1 score 5.5, AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H), which is lower than the remote attack vector suggested in the upstream CVE description. The flaw affects Red Hat products that ship the vulnerable Linux kernel ksmbd SMB Direct code; other Red Hat products evaluated for this flaw are not affected.
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 | 5.5 | N/A | N/A |
| Attack Vector | Local | N/A | N/A |
| Attack Complexity | Low | N/A | N/A |
| Privileges Required | Low | N/A | N/A |
| User Interaction | None | N/A | N/A |
| Scope | Unchanged | N/A | N/A |
| Confidentiality | None | N/A | N/A |
| Integrity Impact | None | N/A | N/A |
| Availability Impact | High | N/A | N/A |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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.