VulnerabilityPublished 19 Jul 2026

CVE-2026-63966: Linux kernel · iio: imu: adis16550: fix stack leak in trigger handler

Source GCVE Database

Not known to be exploited.

Data as of 26 Oct 2026, 14:05 UTC

Severity

Medium

Rated by Threat Radar · No CVSS score from NVD or the CNA

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
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-jr6w-9rm3-jj48

What to do

AI-suggested

A fix is available that zero-initializes the stack structure in the adis16550_trigger_handler function. Users should apply the official Linux kernel patches that address this issue once released.

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 a stack-allocated scan data array is not fully initialized before being partially overwritten, leaving some bytes uninitialized and potentially exposing sensitive stack data. The vulnerability has been fixed by zero-initializing the stack structure to prevent data leakage.

Impact

Uninitialized stack memory is leaked to userspace, potentially exposing sensitive kernel stack data. This could lead to information disclosure vulnerabilities, which might aid attackers in further exploitation or bypassing security mechanisms. No direct code execution or privilege escalation is described.

Summary

The Linux kernel's adis16550_trigger_handler function declares a scan data array on the stack without initializing it. The memcpy operation only fills the first 28 bytes, and a timestamp is written at offset 32, leaving bytes 28-31 uninitialized. These uninitialized bytes can leak stack data to userspace on every trigger event. The fix involves zero-initializing the stack structure to eliminate the leak.

References

Community reviews

Loading reviews…