CVE-2023-53218
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-09-15

Last updated on: 2025-12-03

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: rxrpc: Make it so that a waiting process can be aborted When sendmsg() creates an rxrpc call, it queues it to wait for a connection and channel to be assigned and then waits before it can start shovelling data as the encrypted DATA packet content includes a summary of the connection parameters. However, sendmsg() may get interrupted before a connection gets assigned and further sendmsg() calls will fail with EBUSY until an assignment is made. Fix this so that the call can at least be aborted without failing on EBUSY. We have to be careful here as sendmsg() mustn't be allowed to start the call timer if the call doesn't yet have a connection assigned as an oops may follow shortly thereafter.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-09-15
Last Modified
2025-12-03
Generated
2026-05-07
AI Q&A
2025-09-15
EPSS Evaluated
2026-05-05
NVD
CVE-2023-53218
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
linux linux_kernel From 4.11 (inc) to 6.2.16 (exc)
linux linux_kernel From 6.3 (inc) to 6.3.3 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-NVD-CWE-noinfo
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability in the Linux kernel's rxrpc subsystem involves the sendmsg() function, which creates an rxrpc call and waits for a connection and channel to be assigned before sending encrypted data. If sendmsg() is interrupted before the connection is assigned, subsequent sendmsg() calls fail with an EBUSY error until the connection is assigned. The fix allows the waiting process to be aborted properly without causing EBUSY errors or kernel crashes.


How can this vulnerability impact me? :

This vulnerability can cause sendmsg() calls to fail with EBUSY errors if interrupted before a connection is assigned, potentially leading to application errors or delays in communication. Additionally, if not fixed, it could cause kernel crashes (oops) due to improper handling of call timers, affecting system stability.


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