CVE-2025-40107

can: hi311x: fix null pointer dereference when resuming from sleep before interface was enabled

N/A
Published: November 3, 2025 at 12:15 PM UTC
Updated: October 19, 2026 at 09:10 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.1257e83fb9b7468c75cb65cde1d23043553c346c6d
Vendor states this is fixed in 1d2ef21f02baff0c109ad78b9e835fb4acb14533 (fixed)
Vendor states this is fixed in 6b696808472197b77b888f50bc789a3bae077743 (fixed)
Vendor states this is fixed in d1fc4c041459e2d4856c1b2501486ba4f0cbf96b (fixed)
Vendor states this is fixed in e93af787187e585933570563c643337fa731584a (fixed)
Vendor states this is fixed in fd00cf38fd437c979f0e5905e3ebdfc3f55a4b96 (fixed)
Vendor states this is fixed in 4.12 (unaffected)
Vendor states this is fixed in 6.1.156 (unaffected)
Vendor states this is fixed in 6.12.52 (unaffected)
Vendor states this is fixed in 6.16.12 (unaffected)
Vendor states this is fixed in 6.17 (unaffected)
Vendor states this is fixed in 6.6.111 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusDEFERRED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card