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.

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.

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. Patch status is not yet confirmed in the provided data; check the vendor advisory for current remediation guidance.