CVE-2026-63966: Linux kernel · iio: imu: adis16550: fix stack leak in trigger handler
Affects Linux kernelSource GCVE Database
Not known to be exploited.
Data as of 30 Oct 2026, 20:25 UTC
Rated Low by Threat Radar's AI analysis · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- EPSS
- 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Exploitation evidence
Disclosed: evidence found.
CVE published 19 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 30 Oct 2026.
What to do
AI-suggested
A fix has been implemented in the Linux kernel to zero-initialize the stack structure in the adis16550_trigger_handler() function, preventing stack data leakage. Users should apply the official kernel update containing this fix once available.
Description
A vulnerability in the Linux kernel's iio imu adis16550 driver causes uninitialized stack data to leak to userspace during trigger handling. The issue arises because the scan data array on the stack is not fully initialized before being partially overwritten, leaving some bytes uninitialized and exposing stack data on every trigger. This has been fixed by zero-initializing the stack structure.