CVE-2025-38028
BaseFortify
Publication date: 2025-06-18
Last updated on: 2025-11-14
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 6.15 |
| linux | linux_kernel | 6.15 |
| linux | linux_kernel | 6.15 |
| linux | linux_kernel | 6.15 |
| linux | linux_kernel | 6.15 |
| linux | linux_kernel | 6.15 |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-362 | The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a race condition in the Linux kernel's NFS/localio subsystem, specifically in the function nfs_local_open_fh(). After releasing a lock (clp->cl_uuid.lock), another CPU could access and free a data structure (struct nfsd_file) that was just added, leading to potential use-after-free issues. The fix involves taking an RCU read lock before dropping the spin lock to prevent this race condition.
How can this vulnerability impact me? :
This race condition could lead to use-after-free scenarios, which may cause system instability, crashes, or potentially allow attackers to execute arbitrary code or cause denial of service by exploiting the freed memory.