CVE-2025-38544rxrpc: Fix bug due to prealloc collision
- 5.5MediumCVSS base score
- 0.16%Exploitation in 30 daysEPSS · top 94% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 4 months later
· 4 months later
Published
- 15 months later
· 15 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Modified | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.16% · top 94% of all CVEs (14 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected 00e907127e6f86d0f9b122d9b4347a8aa09a8b61 – < 3838acfc347b803b66a2c8eb510da1c489d44ca1
- affected 00e907127e6f86d0f9b122d9b4347a8aa09a8b61 – < 432c5363cd6fe5a928bbc94524d28b05515684dd
- affected 00e907127e6f86d0f9b122d9b4347a8aa09a8b61 – < 5385ad53793de2ab11e396bdcdaa65bb04b4dad6
- affected 00e907127e6f86d0f9b122d9b4347a8aa09a8b61 – < d8ffb47a443919277cb093c3db1ec6c0a06880b1
- affected 00e907127e6f86d0f9b122d9b4347a8aa09a8b61 – < 69e4186773c6445b258fb45b6e1df18df831ec45
- affected 4.9
- unaffected < 4.9
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.99 – ≤ 6.6.*
- unaffected 6.12.39 – ≤ 6.12.*
- unaffected 6.15.7 – ≤ 6.15.*
- unaffected 6.16 – ≤ *
References
References5
- https://git.kernel.org/stable/c/3838acfc347b803b66a2c8eb510da1c489d44ca1 (opens in a new tab)
- https://git.kernel.org/stable/c/432c5363cd6fe5a928bbc94524d28b05515684dd (opens in a new tab)
- https://git.kernel.org/stable/c/5385ad53793de2ab11e396bdcdaa65bb04b4dad6 (opens in a new tab)
- https://git.kernel.org/stable/c/d8ffb47a443919277cb093c3db1ec6c0a06880b1 (opens in a new tab)
- https://git.kernel.org/stable/c/69e4186773c6445b258fb45b6e1df18df831ec45 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2025-27896 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2025-38544)Record last updated .