Skip to main content
VulnerabilityPublished

CVE-2026-99720: Linux kernel · hwmon: chipcap2: fix IRQ teardown ordering

Source GCVE Database

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

Not known to be exploited : upgrade to d2a66c515d7730fd453485ffb306c412f1f46d72 or a205f2113200c6357e0526c94caaa4c2aceb2fc7 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 d2a66c515d7730fd453485ffb306c412f1f46d72, a205f2113200c6357e0526c94caaa4c2aceb2fc7

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 d2a66c515d7730fd453485ffb306c412f1f46d72 or a205f2113200c6357e0526c94caaa4c2aceb2fc7.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 3af350929e752fe72f0457033d448bff9aac695a, < d2a66c515d7730fd453485ffb306c412f1f46d72
Fixed in
  • d2a66c515d7730fd453485ffb306c412f1f46d72
LinuxLinuxAffected
  • ≥ 3af350929e752fe72f0457033d448bff9aac695a, < a205f2113200c6357e0526c94caaa4c2aceb2fc7
Fixed in
  • a205f2113200c6357e0526c94caaa4c2aceb2fc7
LinuxLinuxAffected
  • =6.9
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: hwmon: chipcap2: fix IRQ teardown ordering The threaded IRQs are currently requested before the hwmon device is registered. Since devres releases resources in reverse order, the hwmon device is unregistered before the IRQs are freed during driver teardown. An IRQ may therefore still run after the hwmon device has been released and access the stale data->hwmon pointer. Separate IRQ discovery from IRQ registration so that the IRQ numbers and alarm visibility flags are initialized before registering the hwmon device while the IRQs are released before the hwmon device during devres cleanup.

References

Community reviews

Loading reviews…