CVE-2022-49814 Details
Description
In the Linux kernel, the following vulnerability has been resolved: kcm: close race conditions on sk_receive_queue sk->sk_receive_queue is protected by skb queue lock, but for KCM sockets its RX path takes mux->rx_lock to protect more than just skb queue. However, kcm_recvmsg() still only grabs the skb queue lock, so race conditions still exist. We can teach kcm_recvmsg() to grab mux->rx_lock too but this would introduce a potential performance regression as struct kcm_mux can be shared by multiple KCM sockets. So we have to enforce skb queue lock in requeue_rx_msgs() and handle skb peek case carefully in kcm_wait_data(). Fortunately, skb_recv_datagram() already handles it nicely and is widely used by other sockets, we can just switch to skb_recv_datagram() after getting rid of the unnecessary sock lock in kcm_recvmsg() and kcm_splice_read(). Side note: SOCK_DONE is not used by KCM sockets, so it is safe to get rid of this check too. I ran the original syzbot reproducer for 30 min without seeing any issue.
A race condition vulnerability has been identified in the Linux kernel's KCM (Kernel Connection Multiplexor) sockets. The issue arises because the KCM socket's receive path uses a specific lock to protect its operations, but the corresponding message reception function only applies the lock for the socket's skb (socket buffer) queue. This discrepancy creates a window for race conditions. While it's possible to modify the reception function to include the missing lock, doing so could negatively impact performance, as the lock can be shared among multiple KCM sockets. The vulnerability can be addressed by adjusting the message reception process to properly manage the locks, ensuring that the skb queue is adequately protected without introducing performance penalties.
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.
No SSVC data is available for this CVE.
References 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.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/22f6b5d47396b4287662668ee3f5c1f766cb4259 | kernel.org | Patch |
| https://git.kernel.org/stable/c/4154b6afa2bd639214ff259d912faad984f7413a | kernel.org | Patch |
| https://git.kernel.org/stable/c/5121197ecc5db58c07da95eb1ff82b98b121a221 | kernel.org | Patch |
| https://git.kernel.org/stable/c/bf92e54597d842da127c59833b365d6faeeaf020 | kernel.org | Patch |
| https://git.kernel.org/stable/c/ce57d6474ae999a3b2d442314087473a646a65c7 | kernel.org | Patch |
| https://git.kernel.org/stable/c/d9ad4de92e184b19bcae4da10dac0275abf83931 | kernel.org | Patch |
| https://git.kernel.org/stable/c/f7b0e95071bb4be4b811af3f0bfc3e200eedeaa3 | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-362 | Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 4.6, < 4.14.300 >= 4.15, < 4.19.267 >= 4.20, < 5.4.225 >= 5.5, < 5.10.156 >= 5.11, < 5.15.80 >= 5.16, < 6.0.10 6.1 rc1 6.1 rc2 6.1 rc3 6.1 rc4 6.1 rc5 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Aug 4, 2026 | CVE Modified | kernel.org |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Nov 7, 2025 | Initial Analysis | [email protected] |
| May 1, 2025 | New CVE Received | kernel.org |