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

> A local attacker can read uninitialized kernel stack memory via the adis16550 IMU trigger handler, potentially exposing sensitive data.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Jul 2026
- **Updated:** 19 Jul 2026
- **Also known as:** BELL-CVE-2026-63966, DEBIAN-CVE-2026-63966, GHSA-jr6w-9rm3-jj48, UBUNTU-CVE-2026-63966

## What is CVE-2026-63966?

CVE-2026-63966 is a vulnerability in Linux, published on 19 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2026-63966?


## How do I fix CVE-2026-63966?

Apply the vendor's patch.

## Is CVE-2026-63966 being exploited?

There is no known exploitation of CVE-2026-63966 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-63966 and fix it if it is affected.

What it is: CVE-2026-63966 is a vulnerability in Linux, published on 19 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-63966 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-63966/ (Markdown: https://insights.sbomify.com/CVE-2026-63966/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-63966
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-63966
- OSV: https://osv.dev/vulnerability/CVE-2026-63966

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-63966/
Summaries are generated and may contain mistakes; the official description above is the record.