VulnerabilityPublished 18 Oct 2026Updated 21 Oct 2026

CVE-2026-98670: Linux kernel · iio: adc: xilinx-xadc: free IRQ before cancelling the unmask worker on unbind

Source GCVE Database

Authoritative record:CVE-2026-98670· Medium

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

Data as of 26 Oct 2026, 17:16 UTC

Severity

Medium

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS: 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in a29d385ad7b340c952a3935af2b33488db1eb3a6, a5fe2d1b55faba6d00fd87ad491b6cb603046304, 012451d72c12293918617ff98cc737bedad21910 +3

Exploitation evidence

Disclosed: evidence found.
CVE published 18 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-pfxr-v75f-fxq3

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected >=5.10.200 <5.11	Fixed in a29d385ad7b340c952a3935af2b33488db1eb3a6 a5fe2d1b55faba6d00fd87ad491b6cb603046304 012451d72c12293918617ff98cc737bedad21910 49ea8a359e362bfbb32a647c8eb7962fbb37234e 5.11 0f3f427076240e75ff265e61645627a71ca4918c
LinuxLinux	Affected =5.12	Fixed in–

AI-suggested

A fix is available in the Linux kernel that changes the order of resource teardown to free the IRQ before cancelling the unmask worker. Users should update to the fixed kernel version containing this patch. No additional mitigation is indicated.

Description

A vulnerability in the Linux kernel's iio adc xilinx-xadc driver was resolved by changing the order of resource management to free IRQ before cancelling the unmask worker on unbind. This prevents the IRQ handler from queuing work after the associated data structure has been freed, which could cause use-after-free conditions.

Impact

If unpatched, the vulnerability could allow the IRQ handler to queue work referencing freed memory, potentially leading to use-after-free conditions. This could cause kernel instability or crashes. No direct exploit or active attacks are reported.

Summary

The Linux kernel's iio adc xilinx-xadc driver had a flaw where the IRQ handler could queue delayed work after the xadc structure was freed during device unbind. The fix involved registering the devm callback that frees the IRQ before requesting the IRQ, ensuring the IRQ is freed first during teardown. This prevents the handler from re-arming work after the workqueue is cleared, eliminating a potential use-after-free scenario. The issue was identified via an in-house static analysis tool.

References

Community reviews

Loading reviews…