# CVE-2025-40107: can: hi311x: fix null pointer dereference when resuming from sleep before interface was enabled

> A null pointer dereference in the Linux kernel hi311x CAN driver causes a denial of service when resuming from sleep before the interface is enabled.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Nov 2025
- **Updated:** 11 May 2026
- **Also known as:** AZL-69586, BELL-CVE-2025-40107, DEBIAN-CVE-2025-40107, GHSA-394x-fq64-jqf6, ROOT-OS-DEBIAN-11-CVE-2025-40107, ROOT-OS-DEBIAN-12-CVE-2025-40107, ROOT-OS-DEBIAN-13-CVE-2025-40107, ROOT-OS-UBUNTU-2204-CVE-2025-40107, ROOT-OS-UBUNTU-2404-CVE-2025-40107, UBUNTU-CVE-2025-40107

## What is CVE-2025-40107?

CVE-2025-40107 is a vulnerability in Linux, published on 3 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2025-40107?


## How do I fix CVE-2025-40107?

Apply the vendor's patch.

## Is CVE-2025-40107 being exploited?

There is no known exploitation of CVE-2025-40107 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-40107 and fix it if it is affected.

What it is: CVE-2025-40107 is a vulnerability in Linux, published on 3 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-40107 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-40107/ (Markdown: https://insights.sbomify.com/CVE-2025-40107/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-40107
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-40107
- OSV: https://osv.dev/vulnerability/CVE-2025-40107

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-40107/
Summaries are generated and may contain mistakes; the official description above is the record.