CVE-2025-38675
BaseFortify
Publication date: 2025-08-22
Last updated on: 2025-11-25
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | 6.16 |
| linux | linux_kernel | 6.16 |
| linux | linux_kernel | 6.16 |
| linux | linux_kernel | 6.16 |
| linux | linux_kernel | 6.16 |
| linux | linux_kernel | 6.16 |
| linux | linux_kernel | 6.16 |
| 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 in the Linux kernel involves the xfrm (IPsec) state management code. Specifically, the function xfrm_state_look_at can, during preemption, access state information for a different CPU than the one it started on. This leads to a situation where an uninitialized pointer (state_ptrs) is used in the 'acquire' block of code, which can cause incorrect behavior or potential misuse. The fix involves initializing state_ptrs earlier to prevent this issue.
How can this vulnerability impact me? :
The vulnerability can cause the Linux kernel's IPsec state management to behave incorrectly due to use of uninitialized pointers when CPU preemption occurs. This could potentially lead to system instability, crashes, or unexpected behavior in network security processing, impacting system reliability and security.