CVE-2026-23066
Last modified
CVE-2026-23066 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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. EPSS estimates a 0.13% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 4.11, < 6.18.8 | — |
| Linux | Linux Kernel | 6.19 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2026-23066?
How severe is CVE-2026-23066?
How do I fix CVE-2026-23066?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-23060In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23061In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23062In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23063In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23064In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23065In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23067In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23068In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-23069In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23070In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23071In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2026-23072In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2026-23066?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
