Use of Uninitialized Resource Affecting kernel-rt-debug package, versions *
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-CENTOS10-KERNELRTDEBUG-18144522
- published22 Jul 2026
- disclosed19 Jul 2026
Introduced: 19 Jul 2026
NewCVE-2026-63966 (opens in a new tab)How to fix?
There is no fixed version for Centos:10 kernel-rt-debug.
NVD Description
Note: Versions mentioned in the description apply only to the upstream kernel-rt-debug package and not the kernel-rt-debug package as distributed by Centos.
See How to fix? for Centos:10 relevant fixed versions and status.
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.
References
- https://bugzilla.redhat.com/show_bug.cgi?id=2502459
- https://access.redhat.com/security/cve/CVE-2026-63966
- https://git.kernel.org/stable/c/474f8928d50b09f7dcf507049f08732640b88b49
- https://git.kernel.org/stable/c/c2c255444392872cbbf46d640cb3a938e8000309
- https://git.kernel.org/stable/c/ce582b22dd2ff15ac99101c22ec1559d1febe2ff