CVE-2025-38514: rxrpc: Fix oops due to non-existence of prealloc backlog struct
In the Linux kernel, the following vulnerability has been resolved:
rxrpc: Fix oops due to non-existence of prealloc backlog struct
If an AFRXRPC service socket is opened and bound, but calls are preallocated, then rxrpcallocincomingcall() will oops because the rxrpcbacklog struct doesn't get allocated until the first preallocation is made.
Fix this by returning NULL from rxrpcallocincomingcall() if there is no backlog struct. This will cause the incoming call to be aborted.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Compensating control
Ensure any AF_RXRPC service socket is opened and bound with preallocated backlog struct created before handling calls, so that rxrpc_alloc_incoming_call() does not encounter a missing rxrpc_backlog preallocation.
Event History
Frequently Asked Questions
What is the severity of CVE-2025-38514?
CVE-2025-38514 is classified as a medium severity vulnerability due to the potential for system crashes.
How do I fix CVE-2025-38514?
To fix CVE-2025-38514, update your Linux kernel to the latest patched version that addresses this issue.
Who is affected by CVE-2025-38514?
CVE-2025-38514 affects systems running vulnerable versions of the Linux kernel with AF_RXRPC service sockets.
What type of vulnerability is CVE-2025-38514?
CVE-2025-38514 is a memory corruption vulnerability that can lead to system instability.
Will CVE-2025-38514 require a reboot to apply the fix?
Yes, applying the fix for CVE-2025-38514 will typically require a system reboot to take effect.