Skip to main content
VulnerabilityPublished

CVE-2026-99670: Linux kernel · can: dev: can_fill_info(): don't wake up controller if interface is down

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-99670· Medium

Not known to be exploited · fixed in d2fd689214afa0a983f4f0833075f167b9f4eddf : update Linux kernel when convenient.

Data as of 20 Nov 2026, 07:34 UTC

Severity
Medium

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in d2fd689214afa0a983f4f0833075f167b9f4eddf, 07521636bb0cfeccb44125a7fc39ee97c36d2e37, 75332c410c8190d61499001c5516af977ca426c3 +1

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade Linux kernel to d2fd689214afa0a983f4f0833075f167b9f4eddf, 07521636bb0cfeccb44125a7fc39ee97c36d2e37, 75332c410c8190d61499001c5516af977ca426c3 or 0a6f6dcf4c9c03c74de17453bef21697cbff4dc3.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ ec56acfef2af184ca485ffeba16adbd56c110c94, < d2fd689214afa0a983f4f0833075f167b9f4eddf
Fixed in
  • d2fd689214afa0a983f4f0833075f167b9f4eddf
LinuxLinuxAffected
  • ≥ ec56acfef2af184ca485ffeba16adbd56c110c94, < 07521636bb0cfeccb44125a7fc39ee97c36d2e37
Fixed in
  • 07521636bb0cfeccb44125a7fc39ee97c36d2e37
LinuxLinuxAffected
  • ≥ ec56acfef2af184ca485ffeba16adbd56c110c94, < 75332c410c8190d61499001c5516af977ca426c3
Fixed in
  • 75332c410c8190d61499001c5516af977ca426c3
LinuxLinuxAffected
  • ≥ ec56acfef2af184ca485ffeba16adbd56c110c94, < 0a6f6dcf4c9c03c74de17453bef21697cbff4dc3
Fixed in
  • 0a6f6dcf4c9c03c74de17453bef21697cbff4dc3
LinuxLinuxAffected
  • =3.18
Fixed in–

Description

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").

References

Community reviews

Loading reviews…