CVE-2026-23066 Details
Description
In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix recvmsg() unconditional requeue If rxrpc_recvmsg() fails because MSG_DONTWAIT was specified but the call at the front of the recvmsg queue already has its mutex locked, it requeues the call - whether or not the call is already queued. The call may be on the queue because MSG_PEEK was also passed and so the call was not dequeued or because the I/O thread requeued it. The unconditional requeue may then corrupt the recvmsg queue, leading to things like UAFs or refcount underruns. Fix this by only requeuing the call if it isn't already on the queue - and moving it to the front if it is already queued. If we don't queue it, we have to put the ref we obtained by dequeuing it. Also, MSG_PEEK doesn't dequeue the call so shouldn't call rxrpc_notify_socket() for the call if we didn't use up all the data on the queue, so fix that also.
A vulnerability in the Linux kernel's RXRPC implementation has been addressed. The issue arose in the recvmsg function, where an unconditional requeue of messages could corrupt the reception queue. This corruption could lead to use-after-free vulnerabilities or reference count underruns. The problem occurred when RXRPC received a message with the MSG_DONTWAIT flag, but the front of the reception queue had its mutex locked. In such cases, RXRPC would requeue the message, regardless of whether it was already queued. This behavior could disrupt the queue management, especially if the MSG_PEEK flag was also used, preventing proper dequeuing. The vulnerability has been fixed by ensuring that messages are only requeued if they are not already in the queue, and by moving them to the front if they are. Additionally, the handling of MSG_PEEK has been corrected to avoid unnecessary notifications when not all data has been processed.
Users can upgrade to the latest version of the Linux kernel to address this vulnerability.
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.
CISA-ADP
Assessed Oct 16, 2026References 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.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-674 | Uncontrolled Recursion | [email protected] |
| CWE-362 | Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') | CISA-ADP |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 4.11, < 6.18.8 6.19 rc1 6.19 rc2 6.19 rc3 6.19 rc4 6.19 rc5 6.19 rc6 |
CPE
Remediation
| |
Change History
10 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Oct 19, 2026 | CVE Modified | CISA-ADP |
| Oct 16, 2026 | CVE Modified | CISA-ADP |
| Oct 15, 2026 | CVE Modified | kernel.org |
| Oct 15, 2026 | CVE Modified | siemens-SADP |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Jun 1, 2026 | CVE Modified | kernel.org |
| Apr 3, 2026 | CVE Modified | kernel.org |
| Mar 25, 2026 | CVE Modified | kernel.org |
| Mar 13, 2026 | Initial Analysis | [email protected] |
| Feb 4, 2026 | New CVE Received | kernel.org |