CVE-2025-38514
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-08-16

Last updated on: 2025-11-03

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix oops due to non-existence of prealloc backlog struct If an AF_RXRPC service socket is opened and bound, but calls are preallocated, then rxrpc_alloc_incoming_call() will oops because the rxrpc_backlog struct doesn't get allocated until the first preallocation is made. Fix this by returning NULL from rxrpc_alloc_incoming_call() if there is no backlog struct. This will cause the incoming call to be aborted.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-08-16
Last Modified
2025-11-03
Generated
2026-05-27
AI Q&A
2025-08-16
EPSS Evaluated
2026-05-25
NVD
CVE-2025-38514
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
linux kernel 6.1.153
linux kernel 5.10.244
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability occurs in the Linux kernel's rxrpc component. When an AF_RXRPC service socket is opened and bound but calls are preallocated, the function rxrpc_alloc_incoming_call() can cause a kernel oops (crash) because the rxrpc_backlog structure is not allocated until the first preallocation is made. The fix involves returning NULL from rxrpc_alloc_incoming_call() if the backlog struct does not exist, which aborts the incoming call and prevents the crash.


How can this vulnerability impact me? :

This vulnerability can cause the Linux kernel to crash (kernel oops) when handling certain AF_RXRPC service socket calls under specific conditions. This could lead to system instability or denial of service if exploited or triggered unintentionally.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart