Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2022-49968ieee802154/adf7242: defer destroy_workqueue call

Description

In the Linux kernel, the following vulnerability has been resolved: ieee802154/adf7242: defer destroy_workqueue call There is a possible race condition (use-after-free) like below (FREE) | (USE) adf7242_remove | adf7242_channel cancel_delayed_work_sync | destroy_workqueue (1) | adf7242_cmd_rx | mod_delayed_work (2) | The root cause for this race is that the upper layer (ieee802154) is unaware of this detaching event and the function adf7242_channel can be called without any checks. To fix this, we can add a flag write at the beginning of adf7242_remove and add flag check in adf7242_channel. Or we can just defer the destructive operation like other commit 3e0588c291d6 ("hamradio: defer ax25 kfree after unregister_netdev") which let the ieee802154_unregister_hw() to handle the synchronization. This patch takes the second option. runs")

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 14 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-49968, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High8.0CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1Medium4.7CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.23% · top 87% of all CVEs (12 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 58e9683d14752debc6f22daf6b23e031787df31f – < dede80aaf01f4b6e8657d23726cb4a3da226ec4c
    • affected 58e9683d14752debc6f22daf6b23e031787df31f – < bed12d7531df1417fc92c691999ff95e03835008
    • affected 58e9683d14752debc6f22daf6b23e031787df31f – < 23a29932715ca43bceb2eae1bdb770995afe7271
    • affected 58e9683d14752debc6f22daf6b23e031787df31f – < 9f8558c5c642c62c450c98c99b7d18a709fff485
    • affected 58e9683d14752debc6f22daf6b23e031787df31f – < 15f3b89bd521d5770d36a61fc04a77c293138ba6
    • affected 58e9683d14752debc6f22daf6b23e031787df31f – < afe7116f6d3b888778ed6d95e3cf724767b9aedf
    • affected a2363e2d88bf50022ee643c49ee5d4f7e8c915ea
    • affected 4.17.19 – < 4.18
  • Linux · Linux

    • affected 4.18
    • unaffected < 4.18
    • 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

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .