CVE-2025-38544 Details
Description
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.
A vulnerability in the Linux kernel's AF_RXRPC implementation has been addressed. When userspace provides a server using AF_RXRPC, it must preallocate incoming calls and assign call IDs to manage related message sending and receiving. These call IDs, which are arbitrary numbers, can be used to reference prepared structures in userspace. However, two calls cannot be assigned the same call ID simultaneously. If an attempt is made to preallocate a call with an in-use ID, an EBADSLT error should be returned. The vulnerability arose because the error handling cleanup process would trigger assertions in the call cleanup function, leading to a collision. This issue has been resolved by properly managing the call state during the preallocation process.
Users can apply the available patch to address this vulnerability. The patch is included in the official Linux kernel stable tree.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/432c5363cd6fe5a928bbc94524d28b05515684dd | kernel.org | Patch |
| https://git.kernel.org/stable/c/5385ad53793de2ab11e396bdcdaa65bb04b4dad6 | kernel.org | Patch |
| https://git.kernel.org/stable/c/69e4186773c6445b258fb45b6e1df18df831ec45 | kernel.org | Patch |
| https://git.kernel.org/stable/c/d8ffb47a443919277cb093c3db1ec6c0a06880b1 | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-617 | Reachable Assertion | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 4.9, < 6.6.99 >= 6.7, < 6.12.39 >= 6.13, < 6.15.7 6.16 rc1 6.16 rc2 6.16 rc3 6.16 rc4 6.16 rc5 |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| Nov 18, 2025 | Initial Analysis | [email protected] |
| Aug 16, 2025 | New CVE Received | kernel.org |