boxscore/security
CVE · referencelatest edition

Reference page — cumulative record through Wednesday, August 19, 2026 UTC. Reference pages update as the archive grows; only dated daily editions are immutable pages of record.

CVE-2022-49814MEDIUM
Linux Linux — kcm: close race conditions on sk_receive_queue
  AV  AC  PR  UI  S  C  I  A   CVSS    EPSS   %ile   KEV
   L   H   L   N  U  N  N  H    4.7   .0016    5.4     —
AFFECTED
  Product  Versions                                    Fixed
  Linux    ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 –  —
  Linux    4.6 –                                       4.14.300
TIMELINE
  May 1   Reserved by Linux
  May 1   Published (CNA: Linux)
  Aug 4   RESCORED — CVE-2022-49814 (Linux). CVSS 7.8 → 4.7 (NVD).
CWE-362 · CNA: Linux · CVSS v3.1 · 7 references · NVD status: Modified

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.

Lifecycle

Complete event history — 3 events, chronological
DateEventDetail
May 1, 2025ReservedReserved by Linux
May 1, 2025PublishedPublished (CNA: Linux)
August 4, 2026RESCOREDRESCORED — CVE-2022-49814 (Linux). CVSS 7.8 → 4.7 (NVD).

Affected

Affected products and packages — 2 rows
VendorProduct / PackageEcosystemVersion introducedFixed
LinuxLinuxab7ac4eb9832e32a09f4e8042705484d2fb0aad3
LinuxLinux4.64.14.300

Weaknesses

CWE-362

References (7)

Related

Authoritative record: CVE-2022-49814 at cve.org

Vendors: linux

Weaknesses: CWE-362

About this page

This is a reference page, not a dated page of record. It assembles the complete lifecycle of CVE-2022-49814 from the CVE Program record, NVD enrichment, the CISA KEV catalog, EPSS, and OSV advisories. The box score's numbers (CVSS, EPSS, KEV status) are current as of Wednesday, August 19, 2026 UTC and are re-derived as the archive grows; only dated daily editions are immutable pages of record. The authoritative source for this identifier is cve.org.