CVE-2025-38544
BaseFortify
Publication date: 2025-08-16
Last updated on: 2025-11-18
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 | From 5.15.160 (inc) to 5.16 (inc) |
| 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 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-617 | The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability involves a bug in the Linux kernel's rxrpc subsystem related to preallocating call IDs for incoming calls when using AF_RXRPC in userspace. The issue arises because the kernel allows call IDs to be reused only after a call ends, but due to improper state handling during error cleanup, assertions fail because calls are neither marked complete nor released properly. This can cause unexpected behavior or crashes when userspace attempts to preallocate calls with call IDs that are already in use.
How can this vulnerability impact me? :
This vulnerability can lead to kernel instability or crashes when userspace applications using AF_RXRPC attempt to preallocate calls with call IDs that are already in use. This may disrupt services relying on rxrpc communication, potentially causing denial of service or unexpected behavior in affected systems.