CVE-2025-37802
Description
A flaw was found in the Linux kernel's ksmbd Server Message Block (SMB) server daemon. An attacker interacting with the SMB service can trigger an improper locking sequence where the kernel attempts a blocking operation while in a sleeping state. This issue can result in scheduler warnings, thread stalls, and a potential Denial of Service (DoS).
Statement
This vulnerability is rated as Moderate severity because triggering it requires interaction with the in-kernel SMB server daemon and results in scheduler warnings or potential thread stalls without compromising confidentiality or integrity. Red Hat Enterprise Linux products are not affected by this flaw because the vulnerable ksmbd code is not present or enabled in supported enterprise kernels. Typical enterprise deployments rely instead on user-space Samba implementations, leaving default environments unaffected.
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 | 5.5 | 7.5 |
| Attack Vector | Local | Local | Network |
| Attack Complexity | Low | Low | Low |
| Privileges Required | Low | Low | None |
| User Interaction | None | None | None |
| Scope | Unchanged | Unchanged | Unchanged |
| Confidentiality | None | None | None |
| Integrity Impact | None | None | None |
| Availability Impact | High | High | High |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Understanding the Weakness (CWE)
Availability
Technical Impact: DoS: Resource Consumption (CPU)
Inconsistent locking discipline can lead to deadlock.
Integrity
Technical Impact: Modify Memory; Modify Application Data
This can lead to data or memory corruption.
Other
Technical Impact: Varies by Context; Unexpected State
This can lead to unexpected resource state changes and behaviors.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.