Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2022-49814: kcm: close race conditions on sk_receive_queue

Noroxi assessment

Priority: Monitor (action score 18/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: Linux Linux 22f6b5d47396b4287662668ee3f5c1f766cb4259, 4154b6afa2bd639214ff259d912faad984f7413a, 5121197ecc5db58c07da95eb1ff82b98b121a221.
  • Severity is disputed: the assigning authority (CNA) scores it 7.8, NVD 4.7.

Low priority for now. Upgrade to Linux Linux 22f6b5d47396b4287662668ee3f5c1f766cb4259, 4154b6afa2bd639214ff259d912faad984f7413a, 5121197ecc5db58c07da95eb1ff82b98b121a221 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 4.7 · v3.1—No exploit Fix available
Published
May 1, 2025
Updated
Aug 5, 2026
EPSS
0.1% · 5th percentile

Report tools

JSON

Action score

18

Monitor

Low priority for now.

CVSS
18 / 40 · 4.7 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CNA vs NVD score

NVD
4.7
CNA · Linux
7.8
3.1 point gap

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2022-49814

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel4.6 and later · before 4.14.300
  • linux linux kernel4.15 and later · before 4.19.267
  • linux linux kernel4.20 and later · before 5.4.225
  • linux linux kernel5.5 and later · before 5.10.156
  • linux linux kernel5.11 and later · before 5.15.80
  • linux linux kernel5.16 and later · before 6.0.10
  • linux linux kernel6.1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 4.6affected
    • ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 and later · before 22f6b5d47396b4287662668ee3f5c1f766cb4259affected · git
    • ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 and later · before d9ad4de92e184b19bcae4da10dac0275abf83931affected · git
    • ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 and later · before ce57d6474ae999a3b2d442314087473a646a65c7affected · git
    • ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 and later · before 4154b6afa2bd639214ff259d912faad984f7413aaffected · git
    • ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 and later · before f7b0e95071bb4be4b811af3f0bfc3e200eedeaa3affected · git
    • ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 and later · before bf92e54597d842da127c59833b365d6faeeaf020affected · git
    • ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 and later · before 5121197ecc5db58c07da95eb1ff82b98b121a221affected · git
    • before 4.6not affected · semver
    • 4.14.300 and later · up to and including 4.14.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.0.10-16.0.10-1
SUSE:Linux Enterprise Live Patching 12 SP5kernel-defaultbefore 4.12.14-122.266.14.12.14-122.266.1
SUSE:Linux Enterprise Live Patching 12 SP5kgraft-patch-SLE12-SP5_Update_70before 1-8.5.11-8.5.1
SUSE:Linux Enterprise Server 12 SP5-LTSSkernel-sourcebefore 4.12.14-122.266.14.12.14-122.266.1
SUSE:Linux Enterprise Server 12 SP5-LTSSkernel-symsbefore 4.12.14-122.266.14.12.14-122.266.1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2022-49808May 1, 2025 · net: dsa: don't leak tagger-owned storage on switch driver unbind
    22Monitor
  • ← EarlierCVE-2022-49809May 1, 2025 · net/x25: Fix skb leak in x25_lapb_receive_frame()
    22Monitor
  • Later →CVE-2022-49815May 1, 2025 · erofs: fix missing xas_retry() in fscache mode
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux22f6b5d47396b4287662668ee3f5c1f766cb4259Vendor (CNA)
Linux Linux4154b6afa2bd639214ff259d912faad984f7413aVendor (CNA)
Linux Linux5121197ecc5db58c07da95eb1ff82b98b121a221Vendor (CNA)
Linux Linuxbf92e54597d842da127c59833b365d6faeeaf020Vendor (CNA)
Linux Linuxce57d6474ae999a3b2d442314087473a646a65c7Vendor (CNA)
Linux Linuxd9ad4de92e184b19bcae4da10dac0275abf83931Vendor (CNA)
Linux Linuxf7b0e95071bb4be4b811af3f0bfc3e200eedeaa3Vendor (CNA)
debian:linux6.0.10-1 · Debian:12Package registry (OSV)
suse:kernel-default4.12.14-122.266.1 · SUSE:Linux Enterprise Live Patching 12 SP5Package registry (OSV)
suse:kernel-source4.12.14-122.266.1 · SUSE:Linux Enterprise Server 12 SP5-LTSSPackage registry (OSV)
suse:kernel-syms4.12.14-122.266.1 · SUSE:Linux Enterprise Server 12 SP5-LTSSPackage registry (OSV)
suse:kgraft-patch-SLE12-SP5_Update_701-8.5.1 · SUSE:Linux Enterprise Live Patching 12 SP5Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

CVSS vector

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (6 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records