Vulnerability in Kernel (CVE-2025-40107)

Summary

Vulnerability in Kernel (CVE-2025-40107). Risk of unauthorized operations or information disclosure. Exploitable via mcp251x. Mitigation: upgrade to 6.1.156, 6.6.111, 6.12.52, 6.16.12 or later.

Original description

The description as published by the source.

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.

Source: OSV.dev (Open Source Vulnerabilities) NVD OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2025-40107 has been found in Kernel.
Attackers can target a specific entry point like mcp251x over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade Kernel to 6.1.156, 6.6.111, 6.12.52, 6.16.12 or later.
If unsure, ask your IT team or search "Kernel CVE-2025-40107" on the vendor's site.

CVE-2025-40107 (Kernel)
Attack surface: mcp251x / hi311x / hi3110_open / hi3110_can_probe
Patched: 6.1.156, 6.6.111, 6.12.52, 6.16.12 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (unclassified) exists in Kernel. Attackers reach the vulnerable code path via mcp251x.

📍 Affected scope

Check the vendor advisory for the affected versions of Kernel. Attack surface: mcp251x / hi311x / hi3110_open / hi3110_can_probe.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 6.1.156, 6.6.111, 6.12.52, 6.16.12.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Kernel' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
grep -r 'Kernel' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で Kernel を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade Kernel to 6.1.156, 6.6.111, 6.12.52, 6.16.12
```
ステージング環境で 6.1.156, 6.6.111, 6.12.52, 6.16.12 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Linux Kernel

[{"type":"ECOSYSTEM","events":[{"introduced":"4.12.0"},{"fixed":"6.1.156"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.2.0"},{"fixed":"6.6.111"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.12.52"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.13.0"},{"fixed":"6.16.12"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

BellSoft Alpaquita BELL-CVE-2025-40107 linux-lts Fixed in: 6.1.156-r0
Debian DEBIAN-CVE-2025-40107 linux
Ubuntu UBUNTU-CVE-2025-40107 linux