Skip to content
TrackCVE
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2022-49957

kcm: fix strp_init() order and cleanup

Medium5.5EPSS 0.27%
Published
Updated
Reserved
Assigned by
Linux

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 11 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

CVSS scores of CVE-2022-49957, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.27% · top 81% of all CVEs (7 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Weakness

Affected products

  • Linux · Linux

    • affected 44890e9ff771ef11777b2d1ebf8589255eb12502 – < 473f394953216614087f4179e55cdf0cf616a13b
    • affected e5571240236c5652f3e079b1d5866716a7ad819c – < a8a0c321319ad64a5427d6172cd9c23b4d6ca1e8
    • affected e5571240236c5652f3e079b1d5866716a7ad819c – < 0946ff31d1a8778787bf6708beb20f38715267cc
    • affected e5571240236c5652f3e079b1d5866716a7ad819c – < 1b6666964ca1de93a7bf06e122bcf3616dbd33a9
    • affected e5571240236c5652f3e079b1d5866716a7ad819c – < 55fb8c3baa8071c5d533a9ad48624e44e2a04ef5
    • affected e5571240236c5652f3e079b1d5866716a7ad819c – < f865976baa85915c7672f351b74d5974b93215f6
    • affected e5571240236c5652f3e079b1d5866716a7ad819c – < 8fc29ff3910f3af08a7c40a75d436b5720efe2bf
    • affected 085cbbda4b4cc7dd2ba63806346881c2c2e10107
    • affected 383250363daf01eb7aa3728c09ef8a4f6d8a3252
    • affected 19042316b9e12c93bf334a04d4dd7a4e846c7311
    • affected 4.14.22 – < 4.14.293
    • affected 4.9.84 – < 4.10
    • affected 4.9.100 – < 4.10
  • Linux · Linux

    • affected 4.15
    • unaffected < 4.15
    • unaffected 4.14.293 – ≤ 4.14.*
    • unaffected 4.19.258 – ≤ 4.19.*
    • unaffected 5.4.213 – ≤ 5.4.*
    • unaffected 5.10.142 – ≤ 5.10.*
    • unaffected 5.15.66 – ≤ 5.15.*
    • unaffected 5.19.8 – ≤ 5.19.*
    • unaffected 6.0 – ≤ *

References (7)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2022-49957 badge
[![CVE-2022-49957](https://trackcve.app/badge/CVE-2022-49957.svg)](https://trackcve.app/cve/CVE-2022-49957)

Record last updated .