CVE-2022-50291
kcm: annotate data-races around kcm->rx_psock
- Published
- Updated
- Reserved
- Assigned by
- Linux
Description
In the Linux kernel, the following vulnerability has been resolved: kcm: annotate data-races around kcm->rx_psock kcm->rx_psock can be read locklessly in kcm_rfree(). Annotate the read and writes accordingly. We do the same for kcm->rx_wait in the following patch. syzbot reported: BUG: KCSAN: data-race in kcm_rfree / unreserve_rx_kcm write to 0xffff888123d827b8 of 8 bytes by task 2758 on cpu 1: unreserve_rx_kcm+0x72/0x1f0 net/kcm/kcmsock.c:313 kcm_rcv_strparser+0x2b5/0x3a0 net/kcm/kcmsock.c:373 __strp_recv+0x64c/0xd20 net/strparser/strparser.c:301 strp_recv+0x6d/0x80 net/strparser/strparser.c:335 tcp_read_sock+0x13e/0x5a0 net/ipv4/tcp.c:1703 strp_read_sock net/strparser/strparser.c:358 [inline] do_strp_work net/strparser/strparser.c:406 [inline] strp_work+0xe8/0x180 net/strparser/strparser.c:415 process_one_work+0x3d3/0x720 kernel/workqueue.c:2289 worker_thread+0x618/0xa70 kernel/workqueue.c:2436 kthread+0x1a9/0x1e0 kernel/kthread.c:376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306 read to 0xffff888123d827b8 of 8 bytes by task 5859 on cpu 0: kcm_rfree+0x14c/0x220 net/kcm/kcmsock.c:181 skb_release_head_state+0x8e/0x160 net/core/skbuff.c:841 skb_release_all net/core/skbuff.c:852 [inline] __kfree_skb net/core/skbuff.c:868 [inline] kfree_skb_reason+0x5c/0x260 net/core/skbuff.c:891 kfree_skb include/linux/skbuff.h:1216 [inline] kcm_recvmsg+0x226/0x2b0 net/kcm/kcmsock.c:1161 ____sys_recvmsg+0x16c/0x2e0 ___sys_recvmsg net/socket.c:2743 [inline] do_recvmmsg+0x2f1/0x710 net/socket.c:2837 __sys_recvmmsg net/socket.c:2916 [inline] __do_sys_recvmmsg net/socket.c:2939 [inline] __se_sys_recvmmsg net/socket.c:2932 [inline] __x64_sys_recvmmsg+0xde/0x160 net/socket.c:2932 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x2b/0x70 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd value changed: 0xffff88812971ce00 -> 0x0000000000000000 Reported by Kernel Concurrency Sanitizer on: CPU: 0 PID: 5859 Comm: syz-executor.3 Not tainted 6.0.0-syzkaller-12189-g19d17ab7c68b-dirty #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022
Timeline
ID reserved
By Linux
Published
- 8 months later
· 8 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 |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.16% · top 95% of all CVEs (7 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 – < 13dba69e18d04c8eec7596369f2a0596b0260275
- affected ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 – < bf46af730e58d340f6f740bc69a07c5f6b85c655
- affected ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 – < 1b8a5692ab25db4ef1c2cc8e5d21f7a65dc3d079
- affected ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 – < e94395e916b48a5b912a0a04570981b5b091acb0
- affected ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 – < c325f92d8d9b223d5842609ca067e898e9d34566
- affected ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 – < 342d918cf9a45df9cf11bbe7162b851adefd178f
- affected ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 – < 12a0eb340c9a22e0f8c00d2c0c1a60695ead926a
- affected ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 – < 15e4dabda11b0fa31d510a915d1a580f47dfc92e
- affected 4.6
- unaffected < 4.6
- unaffected 4.9.332 – ≤ 4.9.*
- unaffected 4.14.298 – ≤ 4.14.*
- unaffected 4.19.264 – ≤ 4.19.*
- unaffected 5.4.223 – ≤ 5.4.*
- unaffected 5.10.153 – ≤ 5.10.*
- unaffected 5.15.77 – ≤ 5.15.*
- unaffected 6.0.7 – ≤ 6.0.*
- unaffected 6.1 – ≤ *
References (8)
- https://git.kernel.org/stable/c/13dba69e18d04c8eec7596369f2a0596b0260275 (opens in a new tab)
- https://git.kernel.org/stable/c/bf46af730e58d340f6f740bc69a07c5f6b85c655 (opens in a new tab)
- https://git.kernel.org/stable/c/1b8a5692ab25db4ef1c2cc8e5d21f7a65dc3d079 (opens in a new tab)
- https://git.kernel.org/stable/c/e94395e916b48a5b912a0a04570981b5b091acb0 (opens in a new tab)
- https://git.kernel.org/stable/c/c325f92d8d9b223d5842609ca067e898e9d34566 (opens in a new tab)
- https://git.kernel.org/stable/c/342d918cf9a45df9cf11bbe7162b851adefd178f (opens in a new tab)
- https://git.kernel.org/stable/c/12a0eb340c9a22e0f8c00d2c0c1a60695ead926a (opens in a new tab)
- https://git.kernel.org/stable/c/15e4dabda11b0fa31d510a915d1a580f47dfc92e (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)
- 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://trackcve.app/cve/CVE-2022-50291)Record last updated .