CVE-2026-63966

iio: imu: adis16550: fix stack leak in trigger handler

Published Jul 19, 2026 CVSS 3.1 · 5.5 Medium EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The ADIS16550 inertial‑measurement‑unit driver in the Linux kernel uses a 32‑byte stack array in its trigger handler without fully initializing it. The memcpy call copies only the first 28 bytes of sensor data, and a subsequent timestamp write writes to offset 32, leaving bytes 28‑31 uninitialized. These four bytes are copied into the buffer delivered to user space, leaking whatever data happened to reside on that stack region with each trigger. This uninitialized memory use allows a local user to read up to four bytes of potentially sensitive stack data in every sensor trigger, constituting an information‑disclosure flaw (CWE‑908). Additionally, the failure to zero‑initialize the buffer leads to a memory‑leak condition (CWE‑401) that could expose more stack data over time.

Affected Systems

Any Linux kernel build that includes the ADIS16550 IIO driver before the patch commit is vulnerable. Distributions shipping affected kernels for embedded or local platforms that expose the IIO device to user processes can be impacted.

Risk and Exploitability

The CVSS score of 5.5 indicates a moderate severity information‑disclosure vulnerability. The EPSS score is below 1 % and the vulnerability is not listed in the CISA KEV catalog, indicating a very low probability of exploitation. An attacker must have local read access to the ADIS16550 IIO device interface; remote exploitation is not feasible. Though only four bytes are leaked per trigger, repeated or malicious reads could accumulate sensitive stack information, raising the potential impact over time.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the running kernel to a version that includes the patch which zeroes the stack buffer in the ADIS16550 trigger handler.
  • If a kernel upgrade cannot be performed immediately, disable the ADIS16550 sensor or its IIO trigger through sysfs or device‑tree configuration to prevent uninitialized data from reaching userspace.
  • Apply a local patch that zeroes the 32‑byte stack array before it is used, recompile the driver, and reload it into the running kernel.
  • When disabling the sensor is not possible, restrict access to the ADIS16550 IIO device file to privileged users only, limiting the risk of data leakage.

Generated by OpenCVE AI on October 30, 2026 at 18:47 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Ubuntu USN Ubuntu USN USN-8593-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8603-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-8618-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8663-1 Linux kernel (NVIDIA) vulnerabilities
Ubuntu USN Ubuntu USN USN-8664-1 Linux kernel (NVIDIA BaseOS) vulnerabilities
Ubuntu USN Ubuntu USN USN-8728-1 Linux kernel (GCP) vulnerabilities
Ubuntu USN Ubuntu USN USN-8728-2 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-8728-3 Linux kernel (Oracle) vulnerabilities
History
Type Values Removed Values Added
Weaknesses CWE-401
CPEs cpe:2.3:o:linux:linux_kernel:6.15:-:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.15:rc6:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.15:rc7:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:7.1:rc1:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:7.1:rc2:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:7.1:rc3:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:7.1:rc4:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:7.1:rc5:*:*:*:*:*:*
Metrics cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

Type Values Removed Values Added
Weaknesses CWE-200
CWE-457
Type Values Removed Values Added
Weaknesses CWE-200
CWE-457
Type Values Removed Values Added
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.
Title iio: imu: adis16550: fix stack leak in trigger handler
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses
  • CWE-401

    Missing Release of Memory after Effective Lifetime

  • CWE-908

    Use of Uninitialized Resource

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Jul 19, 2026, 2:55 PM
Reserved
Jul 19, 2026, 7:54 AM
Status
Analyzed
Published
Jul 19, 2026, 4:17 PM
Modified
Oct 30, 2026, 5:25 PM
Severity
Public date
Jul 19, 2026, 12:00 AM