LiveActive security incident?Get immediate response
CVE Record

CVE-2022-49957: kcm: fix strp_init() order and cleanup

In the Linux kernel, the following vulnerability has been resolved: kcm: fix strp_init() order and cleanup strp_init() is called just a few lines above this csk->sk_user_data check, it also initializes strp->work etc., therefore, it is unnecessary to call strp_done() to cancel the freshly initialized work. And if sk_user_data is already used by KCM, psock->strp should not be touched, particularly strp->work state, so we need to move strp_init() after the csk->sk_user_data check. This also makes a lockdep warning reported by syzbot go away.

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

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel KCM networking bug fixed by moving initialization after a user-data ownership check. Public data describes a syzbot lockdep warning, not a data theft path or active exploitation. Business urgency depends on whether affected kernels are deployed and when normal kernel patch cycles occur.

Executive priority

Treat this as routine kernel hygiene unless local evidence shows exposed KCM use on high-value systems. There is no provided evidence of active exploitation or a scored severity, but kernel fixes should still enter normal patch governance.

Technical view

The KCM code called strp_init() before checking whether sk_user_data was already owned by KCM. The fix moves strp_init() after that check and avoids touching psock->strp when ownership is already established, clearing a syzbot-reported lockdep warning.

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions listed in the CVE record, especially where KCM networking code is present or enabled. The bundle does not identify affected distributions, packaged kernel versions, cloud images, or appliances.

Exploitation context

The source bundle does not report active exploitation, public exploit availability, or CISA KEV listing. The described trigger comes from syzbot and lockdep behavior, so real-world attacker impact is not established in the provided evidence.

Researcher notes

Evidence is sparse: no CVSS, CWE, exploit status, or distribution-specific mapping is provided. The core issue is initialization order and state cleanup in KCM stream parser handling, with syzbot/lockdep as the reported signal.

Mitigation direction

  • Update affected Linux kernels through distribution or vendor-supported kernel packages.
  • Confirm the update includes one of the referenced upstream stable fixes.
  • Monitor Linux distribution advisories for backported fixes and package-specific status.
  • Prioritize internet-facing or multi-tenant Linux systems if KCM is enabled.

Validation and detection

  • Inventory Linux kernel versions across servers, containers, appliances, and cloud images.
  • Compare kernel builds against vendor advisories and the referenced stable commits.
  • Check whether KCM support is built, loaded, or required in your environment.
  • Review vulnerability scanner findings for CVE-2022-49957 against actual kernel package metadata.
Prepared
Confidence
medium
Sources
9

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-49957 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
8Source 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
LinuxLinux44890e9ff771ef11777b2d1ebf8589255eb12502, e5571240236c5652f3e079b1d5866716a7ad819c, e5571240236c5652f3e079b1d5866716a7ad819c, e5571240236c5652f3e079b1d5866716a7ad819c, e5571240236c5652f3e079b1d5866716a7ad819c, e5571240236c5652f3e079b1d5866716a7ad819c, e5571240236c5652f3e079b1d5866716a7ad819c, 085cbbda4b4cc7dd2ba63806346881c2c2e10107, 383250363daf01eb7aa3728c09ef8a4f6d8a3252, 19042316b9e12c93bf334a04d4dd7a4e846c7311, 4.14.22, 4.9.84, 4.9.100unaffected
LinuxLinux4.15, 0, 4.14.293, 4.19.258, 5.4.213, 5.10.142, 5.15.66, 5.19.8, 6.0affected
Weakness

CWE details

No CWE listed

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