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-50829wifi: ath9k: hif_usb: Fix use-after-free in ath9k_hif_usb_reg_in_cb()

Description

In the Linux kernel, the following vulnerability has been resolved: wifi: ath9k: hif_usb: Fix use-after-free in ath9k_hif_usb_reg_in_cb() It is possible that skb is freed in ath9k_htc_rx_msg(), then usb_submit_urb() fails and we try to free skb again. It causes use-after-free bug. Moreover, if alloc_skb() fails, urb->context becomes NULL but rx_buf is not freed and there can be a memory leak. The patch removes unnecessary nskb and makes skb processing more clear: it is supposed that ath9k_htc_rx_msg() either frees old skb or passes its managing to another callback function. Found by Linux Verification Center (linuxtesting.org) with Syzkaller.

Timeline

  1. ID reserved

    By Linux

  2. Published

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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.

EPSS (exploitation in 30 days)
0.28% · top 79% of all CVEs (13 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 3deff76095c4ac4252e27c537db3041f619c23a2 – < 5e8751a977a49a6e00cce1a8da5ca16da83f9c8c
    • affected 3deff76095c4ac4252e27c537db3041f619c23a2 – < f127c2b4c967025e5c3a4ce7e13b79135d46a33d
    • affected 3deff76095c4ac4252e27c537db3041f619c23a2 – < 0c8dd2ea4b419da96ab4953e4967e9363e2f8a4f
    • affected 3deff76095c4ac4252e27c537db3041f619c23a2 – < 988bd27de2484faf17afe0408db2e3d9e5ac61fc
    • affected 3deff76095c4ac4252e27c537db3041f619c23a2 – < 98d9172822dc6f38138333941984bd759a89d419
    • affected 3deff76095c4ac4252e27c537db3041f619c23a2 – < 355f16f756aad0c95cdaa0c14a34ab4137d32815
    • affected 3deff76095c4ac4252e27c537db3041f619c23a2 – < 53b9bb1a00c4285ee7f58a11129dbea015db61bc
    • affected 3deff76095c4ac4252e27c537db3041f619c23a2 – < 71fc0ad671a62c494d2aec731baeabd3bfe6c95d
    • affected 3deff76095c4ac4252e27c537db3041f619c23a2 – < dd95f2239fc846795fc926787c3ae0ca701c9840
  • Linux · Linux

    • affected 3.0
    • unaffected < 3.0
    • unaffected 4.9.337 – ≤ 4.9.*
    • unaffected 4.14.303 – ≤ 4.14.*
    • unaffected 4.19.270 – ≤ 4.19.*
    • unaffected 5.4.229 – ≤ 5.4.*
    • unaffected 5.10.163 – ≤ 5.10.*
    • unaffected 5.15.86 – ≤ 5.15.*
    • unaffected 6.0.16 – ≤ 6.0.*
    • unaffected 6.1.2 – ≤ 6.1.*
    • unaffected 6.2 – ≤ *

References

References9

Sources

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

Badge for a README or a ticket

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

Record last updated .