CVE-2022-49814kcm: close race conditions on sk_receive_queue
- 7.8HighCVSS base score
- 0.17%Exploitation in 30 daysEPSS · top 94% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
Published
- 15 months later
· 15 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Modified | 3.1 | Medium4.7 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.17% · top 94% of all CVEs (18 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 – < 22f6b5d47396b4287662668ee3f5c1f766cb4259
- affected ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 – < d9ad4de92e184b19bcae4da10dac0275abf83931
- affected ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 – < ce57d6474ae999a3b2d442314087473a646a65c7
- affected ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 – < 4154b6afa2bd639214ff259d912faad984f7413a
- affected ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 – < f7b0e95071bb4be4b811af3f0bfc3e200eedeaa3
- affected ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 – < bf92e54597d842da127c59833b365d6faeeaf020
- affected ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 – < 5121197ecc5db58c07da95eb1ff82b98b121a221
- affected 4.6
- unaffected < 4.6
- unaffected 4.14.300 – ≤ 4.14.*
- unaffected 4.19.267 – ≤ 4.19.*
- unaffected 5.4.225 – ≤ 5.4.*
- unaffected 5.10.156 – ≤ 5.10.*
- unaffected 5.15.80 – ≤ 5.15.*
- unaffected 6.0.10 – ≤ 6.0.*
- unaffected 6.1 – ≤ *
References
References7
- https://git.kernel.org/stable/c/22f6b5d47396b4287662668ee3f5c1f766cb4259 (opens in a new tab)
- https://git.kernel.org/stable/c/d9ad4de92e184b19bcae4da10dac0275abf83931 (opens in a new tab)
- https://git.kernel.org/stable/c/ce57d6474ae999a3b2d442314087473a646a65c7 (opens in a new tab)
- https://git.kernel.org/stable/c/4154b6afa2bd639214ff259d912faad984f7413a (opens in a new tab)
- https://git.kernel.org/stable/c/f7b0e95071bb4be4b811af3f0bfc3e200eedeaa3 (opens in a new tab)
- https://git.kernel.org/stable/c/bf92e54597d842da127c59833b365d6faeeaf020 (opens in a new tab)
- https://git.kernel.org/stable/c/5121197ecc5db58c07da95eb1ff82b98b121a221 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2025-12951 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2022-49814)Record last updated .