LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50265: kcm: annotate data-races around kcm->rx_wait

In the Linux kernel, the following vulnerability has been resolved: kcm: annotate data-races around kcm->rx_wait kcm->rx_psock can be read locklessly in kcm_rfree(). Annotate the read and writes accordingly. syzbot reported: BUG: KCSAN: data-race in kcm_rcv_strparser / kcm_rfree write to 0xffff88810784e3d0 of 1 bytes by task 1823 on cpu 1: reserve_rx_kcm net/kcm/kcmsock.c:283 [inline] kcm_rcv_strparser+0x250/0x3a0 net/kcm/kcmsock.c:363 __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 0xffff88810784e3d0 of 1 bytes by task 17869 on cpu 0: kcm_rfree+0x121/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: 0x01 -> 0x00 Reported by Kernel Concurrency Sanitizer on: CPU: 0 PID: 17869 Comm: syz-executor.2 Not tainted 6.1.0-rc1-syzkaller-00010-gbb1a1146467a-dirty #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2022-50265 is a Linux kernel KCM networking bug reported by syzbot/KCSAN as a data race. The public record does not provide a CVSS score, impact statement, or evidence of exploitation. Treat it as a kernel maintenance and exposure-management issue until vendor guidance clarifies severity.

Executive priority

Medium operational priority, with urgency driven by asset criticality and vendor guidance. There is no supplied evidence of exploitation or rated severity, but kernel concurrency defects should not remain untracked on production or multi-tenant systems.

Technical view

The issue involves lockless access around KCM receive state, reported as a KCSAN data race between kcm_rcv_strparser and kcm_rfree in net/kcm/kcmsock.c. The resolution annotates concurrent reads and writes. The source bundle references multiple Linux stable commits carrying the fix.

Likely exposure

Systems running Linux kernels with KCM code in the affected version set may be exposed. The bundle lists Linux as affected but provides no CPEs, distribution advisories, or configuration prerequisites, so fleet exposure must be verified against actual kernel builds and vendor backports.

Exploitation context

No active exploitation is supported by the supplied sources. The CVE is not listed as KEV in the bundle, and the available description is a sanitizer-reported concurrency defect rather than a public exploit report.

Researcher notes

The record is sparse: no CVSS, CWE, CPEs, exploit status, or detailed impact are provided. Focus validation on whether the relevant stable commit or vendor backport is present, and avoid inferring memory corruption or privilege impact from the sanitizer trace alone.

Mitigation direction

  • Apply Linux kernel updates containing the referenced stable fixes.
  • Check OS vendor advisories for backported fixes in distribution kernels.
  • Prioritize externally exposed or multi-tenant Linux systems after vendor severity is known.
  • Avoid assuming mitigation details not stated by your kernel vendor.

Validation and detection

  • Inventory running kernel versions across Linux assets.
  • Map each kernel to vendor advisory status or referenced stable commits.
  • Confirm patched hosts booted into the updated kernel.
  • Track any vendor severity, exploitability, or mitigation updates.
Prepared
Confidence
medium
Sources
10

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-50265 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
9Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxab7ac4eb9832e32a09f4e8042705484d2fb0aad3, ab7ac4eb9832e32a09f4e8042705484d2fb0aad3, ab7ac4eb9832e32a09f4e8042705484d2fb0aad3, ab7ac4eb9832e32a09f4e8042705484d2fb0aad3, ab7ac4eb9832e32a09f4e8042705484d2fb0aad3, ab7ac4eb9832e32a09f4e8042705484d2fb0aad3, ab7ac4eb9832e32a09f4e8042705484d2fb0aad3, ab7ac4eb9832e32a09f4e8042705484d2fb0aad3unaffected
LinuxLinux4.6, 0, 4.9.332, 4.14.298, 4.19.264, 5.4.223, 5.10.153, 5.15.77, 6.0.7, 6.1affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.