CVE-2026-99670

Source
https://cve.org/CVERecord?id=CVE-2026-99670
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99670.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2026-99670
Published
2026-11-20T05:50:19Z
Modified
2026-11-20T07:01:11Z
Summary
can: dev: can_fill_info(): don't wake up controller if interface is down
Details

In the Linux kernel, the following vulnerability has been resolved:

can: dev: can_fill_info(): don't wake up controller if interface is down

If the interface is down, the CAN controller might be powered down and its clocks gated. Don't call do_get_berr_counter() to read the bus error counters if the interface is down, and adjust can_get_size() to match.

This removes one trigger for a synchronous external abort seen on i.MX8QXP when "ip link show" is run on a flexcan interface that was never brought up. The underlying cause is platform-specific: on i.MX8QXP the CAN clocks are gated through the SCU LPCG and the subsystem shares the IMX_SC_R_CAN_0 power domain, and there is a window after pm_runtime_resume_and_get() returns where the clock has not reached the module yet. This patch avoids the netlink query path while the interface is down, but does not root-cause the LPCG window itself.

As a result, IFLA_CAN_BERR_COUNTER is no longer reported for down interfaces. Userspace must treat the attribute as optional.

The issue was triggered on an i.MX8QXP board by running "ip link show" without ever bringing the interface up:

Internal error: synchronous external abort: 0000000096000210

pc : flexcan_read_le+0x0/0x18
lr : flexcan_get_berr_counter+0x4c/0x8c
Call trace:
 flexcan_read_le+0x0/0x18
 flexcan_get_berr_counter+0x4c/0x8c
 can_fill_info+0x1f8/0x434
 rtnl_fill_ifinfo+0x8fc/0xbb4
 rtnl_dump_ifinfo+0x364/0x448

This is the same class of problem fixed for m_can in commit 91a55c72a821 ("can: m_can: m_can_get_berr_counter(): don't wake up controller if interface is down").

Database specific
{
    "cna_assigner": "Linux",
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99670.json"
}
References

Affected packages

Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

Affected ranges

Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
ec56acfef2af184ca485ffeba16adbd56c110c94
Fixed
d2fd689214afa0a983f4f0833075f167b9f4eddf
Fixed
07521636bb0cfeccb44125a7fc39ee97c36d2e37
Fixed
0a6f6dcf4c9c03c74de17453bef21697cbff4dc3
Fixed
75332c410c8190d61499001c5516af977ca426c3

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99670.json"

Linux / Kernel

Package

Name
Kernel

Affected ranges

Type
ECOSYSTEM
Events
Introduced
3.18.0
Fixed
6.12.118
Type
ECOSYSTEM
Events
Introduced
6.13.0
Fixed
6.18.64
Type
ECOSYSTEM
Events
Introduced
6.19.0
Fixed
7.3.5

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99670.json"