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-40107can: hi311x: fix null pointer dereference when resuming from sleep before interface was enabled

Description

In the Linux kernel, the following vulnerability has been resolved: can: hi311x: fix null pointer dereference when resuming from sleep before interface was enabled This issue is similar to the vulnerability in the `mcp251x` driver, which was fixed in commit 03c427147b2d ("can: mcp251x: fix resume from sleep before interface was brought up"). In the `hi311x` driver, when the device resumes from sleep, the driver schedules `priv->restart_work`. However, if the network interface was not previously enabled, the `priv->wq` (workqueue) is not allocated and initialized, leading to a null pointer dereference. To fix this, we move the allocation and initialization of the workqueue from the `hi3110_open` function to the `hi3110_can_probe` function. This ensures that the workqueue is properly initialized before it is used during device resume. And added logic to destroy the workqueue in the error handling paths of `hi3110_can_probe` and in the `hi3110_can_remove` function to prevent resource leaks.

Timeline

  1. ID reserved

    By Linux

  2. · 7 months later

    Published

  3. · 6 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.20% · top 90% 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 57e83fb9b7468c75cb65cde1d23043553c346c6d – < d1fc4c041459e2d4856c1b2501486ba4f0cbf96b
    • affected 57e83fb9b7468c75cb65cde1d23043553c346c6d – < e93af787187e585933570563c643337fa731584a
    • affected 57e83fb9b7468c75cb65cde1d23043553c346c6d – < 1d2ef21f02baff0c109ad78b9e835fb4acb14533
    • affected 57e83fb9b7468c75cb65cde1d23043553c346c6d – < fd00cf38fd437c979f0e5905e3ebdfc3f55a4b96
    • affected 57e83fb9b7468c75cb65cde1d23043553c346c6d – < 6b696808472197b77b888f50bc789a3bae077743
  • Linux · Linux

    • affected 4.12
    • unaffected < 4.12
    • unaffected 6.1.156 – ≤ 6.1.*
    • unaffected 6.6.111 – ≤ 6.6.*
    • unaffected 6.12.52 – ≤ 6.12.*
    • unaffected 6.16.12 – ≤ 6.16.*
    • unaffected 6.17 – ≤ *

References

References5

Sources

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

Badge for a README or a ticket

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

Record last updated .