Answer in brief
CVE-2025-38544 records a Medium severity (CVSS 5.5) vulnerability in rxrpc: Fix bug due to prealloc collision. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.16:rc1:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.16:rc2:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.16:rc3:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.16:rc4:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.16:rc5:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=00e907127e6f86d0f9b122d9b4347a8aa09a8b61 <3838acfc347b803b66a2c8eb510da1c489d44ca1 || >=00e907127e6f86d0f9b122d9b4347a8aa09a8b61 <432c5363cd6fe5a928bbc94524d28b05515684dd || >=00e907127e6f86d0f9b122d9b4347a8aa09a8b61 <5385ad53793de2ab11e396bdcdaa65bb04b4dad6 || >=00e907127e6f86d0f9b122d9b4347a8aa09a8b61 <d8ffb47a443919277cb093c3db1ec6c0a06880b1 || >=00e907127e6f86d0f9b122d9b4347a8aa09a8b61 <69e4186773c6445b258fb45b6e1df18df831ec45 | 3838acfc347b803b66a2c8eb510da1c489d44ca1, 432c5363cd6fe5a928bbc94524d28b05515684dd, 5385ad53793de2ab11e396bdcdaa65bb04b4dad6, d8ffb47a443919277cb093c3db1ec6c0a06880b1, 69e4186773c6445b258fb45b6e1df18df831ec45 |
| Linux/Linuxgeneric | 4.9 | Not reported |
Published upstream
Aug 16, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 30, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 30, 2026
In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix bug due to prealloc collision When userspace is using AF_RXRPC to provide a server, it has to preallocate incoming calls and assign to them call IDs that will be used to thread related recvmsg() and sendmsg() together. The preallocated call IDs will automatically be attached to calls as they come in until the pool is empty. To the kernel, the call IDs are just arbitrary numbers, but userspace can use the call ID to hold a pointer to prepared structs. In any case, the user isn't permitted to create two calls with the same call ID (call IDs become available again when the call ends) and EBADSLT should result from sendmsg() if an attempt is made to preallocate a call with an in-use call ID. However, the cleanup in the error handling will trigger both assertions in rxrpc_cleanup_call() because the call isn't marked complete and isn't marked as having been released. Fix this by setting the call state in rxrpc_service_prealloc_one() and then marking it as being released before calling the cleanup function.
Quoted source text, attributed separately from HOL analysis.