CVE-2026-23066
What it is
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.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.1% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.1% in the next 30 days (EPSS).
- Severity: 7.8 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.1% · EPSS, next 30 days
- Weakness
- CWE-674
- Record status
- Modified
Affected
- Linux Kernel < 6.18.8
- Linux Kernel 6.19
Attack profile CVSS 3.1 · 7.8
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-23066.md and follow it. Check whether this project is affected by CVE-2026-23066. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/2c28769a51deb6022d7fbd499987e237a01dd63a
- https://git.kernel.org/stable/c/930114425065f7ace6e0c0630fab4af75e059ea8
References
- https://git.kernel.org/stable/c/0464bf75590da75b8413c3e758c04647b4cdb3c6
- https://git.kernel.org/stable/c/2c28769a51deb6022d7fbd499987e237a01dd63a
- https://git.kernel.org/stable/c/8fd3b5e297854a4da0f273169baf4b1b7b257b97
- https://git.kernel.org/stable/c/930114425065f7ace6e0c0630fab4af75e059ea8
- https://git.kernel.org/stable/c/c198628f3fca5c874d93874c233014d336e09f64
- https://git.kernel.org/stable/c/c6cebcb4e0b3140ec2ace45c020a9049527385d1
- https://git.kernel.org/stable/c/cf969bddd6e69c5777fa89dc88402204e72f312a
- https://cert-portal.siemens.com/productcert/html/ssa-784472.html