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-21802net: hns3: fix oops when unload drivers paralleling

Description

In the Linux kernel, the following vulnerability has been resolved: net: hns3: fix oops when unload drivers paralleling When unload hclge driver, it tries to disable sriov first for each ae_dev node from hnae3_ae_dev_list. If user unloads hns3 driver at the time, because it removes all the ae_dev nodes, and it may cause oops. But we can't simply use hnae3_common_lock for this. Because in the process flow of pci_disable_sriov(), it will trigger the remove flow of VF, which will also take hnae3_common_lock. To fixes it, introduce a new mutex to protect the unload process.

Timeline

  1. ID reserved

    By Linux

  2. · 2 months later

    Published

  3. · 21 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-21802, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.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 (14 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.

Affected products

  • Linux · Linux

    • affected d36b15e3e7b5937cb1f6ac590a85facc3a320642 – < 622d92a67656e5c4d2d6ccac02d688ed995418c6
    • affected 0dd8a25f355b4df2d41c08df1716340854c7d4c5 – < 8c640dd3d900cc8988a39c007591f1deee776df4
    • affected 0dd8a25f355b4df2d41c08df1716340854c7d4c5 – < e876522659012ef2e73834a0b9f1cbe3f74d5fad
    • affected 0dd8a25f355b4df2d41c08df1716340854c7d4c5 – < b5a8bc47aa0a4aa8bca5466dfa2d12dbb5b3cd0c
    • affected 0dd8a25f355b4df2d41c08df1716340854c7d4c5 – < 82736bb83fb0221319c85c2e9917d0189cd84e1e
    • affected 0dd8a25f355b4df2d41c08df1716340854c7d4c5 – < cafe9a27e22736d4a01b3933e36225f9857c7988
    • affected 0dd8a25f355b4df2d41c08df1716340854c7d4c5 – < 92e5995773774a3e70257e9c95ea03518268bea5
    • affected b06ad258e01389ca3ff13bc180f3fcd6a608f1cd
    • affected c4b64011e458aa2b246cd4e42012cfd83d2d9a5c
    • affected 9b5a29f0acefa3eb1dbe2fa302b393eeff64d933
    • affected 5.10.76 – < 5.10.235
    • affected 4.19.214 – < 4.20
    • affected 5.4.156 – < 5.5
    • affected 5.14.15 – < 5.15
  • Linux · Linux

    • affected 5.15
    • unaffected < 5.15
    • unaffected 5.10.235 – ≤ 5.10.*
    • unaffected 5.15.179 – ≤ 5.15.*
    • unaffected 6.1.129 – ≤ 6.1.*
    • unaffected 6.6.76 – ≤ 6.6.*
    • unaffected 6.12.13 – ≤ 6.12.*
    • unaffected 6.13.2 – ≤ 6.13.*
    • unaffected 6.14 – ≤ *

References

References11

Sources

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

Badge for a README or a ticket

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

Record last updated .