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-2025-38420wifi: carl9170: do not ping device which has failed to load firmware

Description

In the Linux kernel, the following vulnerability has been resolved: wifi: carl9170: do not ping device which has failed to load firmware Syzkaller reports [1, 2] crashes caused by an attempts to ping the device which has failed to load firmware. Since such a device doesn't pass 'ieee80211_register_hw()', an internal workqueue managed by 'ieee80211_queue_work()' is not yet created and an attempt to queue work on it causes null-ptr-deref. [1] https://syzkaller.appspot.com/bug?extid=9a4aec827829942045ff [2] https://syzkaller.appspot.com/bug?extid=0d8afba53e8fb2633217

Timeline

  1. ID reserved

    By Linux

  2. · 3 months later

    Published

  3. · 16 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-2025-38420, 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.21% · top 89% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected e4a668c59080f862af3ecc28b359533027cbe434 – < 0140d3d37f0f1759d1fdedd854c7875a86e15f8d
    • affected e4a668c59080f862af3ecc28b359533027cbe434 – < 8a3734a6f4c05fd24605148f21fb2066690d61b3
    • affected e4a668c59080f862af3ecc28b359533027cbe434 – < 527fad1ae32ffa2d4853a1425fe1c8dbb8c9744c
    • affected e4a668c59080f862af3ecc28b359533027cbe434 – < bfeede26e97ce4a15a0b961118de4a0e28c9907a
    • affected e4a668c59080f862af3ecc28b359533027cbe434 – < 4e9ab5c48ad5153cc908dd29abad0cd2a92951e4
    • affected e4a668c59080f862af3ecc28b359533027cbe434 – < 301268dbaac8e9013719e162a000202eac8054be
    • affected e4a668c59080f862af3ecc28b359533027cbe434 – < 11ef72b3312752c2ff92f3c1e64912be3228ed36
    • affected e4a668c59080f862af3ecc28b359533027cbe434 – < 15d25307692312cec4b57052da73387f91a2e870
  • Linux · Linux

    • affected 2.6.38
    • unaffected < 2.6.38
    • unaffected 5.4.295 – ≤ 5.4.*
    • unaffected 5.10.239 – ≤ 5.10.*
    • unaffected 5.15.186 – ≤ 5.15.*
    • unaffected 6.1.142 – ≤ 6.1.*
    • unaffected 6.6.95 – ≤ 6.6.*
    • unaffected 6.12.35 – ≤ 6.12.*
    • unaffected 6.15.4 – ≤ 6.15.*
    • unaffected 6.16 – ≤ *

References

References10

Sources

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

Badge for a README or a ticket

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

Record last updated .