CVE-2026-63934: iio: gyro: itg3200: fix i2c read into the wrong stack location
High 7.1 EPSS 0.2% Linux kernel
In the Linux kernel, the following vulnerability has been resolved: iio: gyro: itg3200: fix i2c read into the wrong stack location itg3200_read_all_channels() takes `__be16 *buf' as a parameter and fills the i2c_msg destination as `(char *)&buf'. Since `buf' is the parameter (a pointer), `&buf' is the address of the local pointer slot on the stack of itg3200_read_all_channels(), not the address of the caller's scan buffer. The (char *) cast hides the type mismatch. i2c_transfer() therefore writes ITG3200_SCAN_ELEMENTS * sizeof(s16) = 8 bytes into the parameter's stack slot, which is discarded when the function returns. The caller's scan buffer in itg3200_trigger_handler() is never written to, so iio_push_to_buffers_with_timestamp() pushes uninitialised stack contents to userspace via /dev/iio:deviceX every scan -- both a functional bug (no actual gyroscope or temperature data is delivered through the triggered buffer) and an information leak. The non-buffered read_raw() path is unaffected: it goes through itg3200_read_reg_s16() which uses `&out' on a local s16 value, where that is correct. Drop the spurious `&' so the i2c read writes into the caller's buffer.
- CVE-2026-63934CVE identifier
- 7.1CVSS 3.1 base score (high)
- 0.2%EPSS: chance of exploitation in the next 30 days (higher than 5% of CVEs)
- 2026-07-19published
What do these terms mean? CVE · CVSS score · exploited (KEV) · EPSS · backported fix · all terms
What to do now
- Check whether you run Linux kernel and which version (commands below).
- Install the fixed version for your system: see “Patch it” below.
- Reboot into the new kernel (uname -r to confirm); live patching (kpatch, Ubuntu Livepatch, SUSE kGraft/klp) can defer the reboot for some CVEs
Affected and fixed versions
Affected:
- Linux Linux 9dbf091da080508e9f632d307f357beb79a0766b to before 90e809376b0f0d1ddec2eec954aecdd2a5b40b0e
- Linux Linux 9dbf091da080508e9f632d307f357beb79a0766b to before 8654b5e2617819ff4f7c78071dfd0275e971a9b6
- Linux Linux 9dbf091da080508e9f632d307f357beb79a0766b to before b64dd5f3b38911054cbcc570df617e3e8e75e562
- Linux Linux 9dbf091da080508e9f632d307f357beb79a0766b to before 31bbd4b87dd6701fa10e03ba7f6268e49e178d16
- Linux Linux 9dbf091da080508e9f632d307f357beb79a0766b to before 63203bd072b613c18c237b906b1c9d2dc4527337
- Linux Linux 9dbf091da080508e9f632d307f357beb79a0766b to before 15a0b3f33ffb6c78b3de6f69b026ceb09b973dd1
- Linux Linux 9dbf091da080508e9f632d307f357beb79a0766b to before cfc3283859cfdeacadf80d5e6880bdf871ffeaa6
- Linux Linux 9dbf091da080508e9f632d307f357beb79a0766b to before 6bdc3023d62ed5c7d591f0eb27a5adb37fb892ae
- Linux Linux 3.9
Patch it
Use the commands for your system. Distribution packages often keep an older version number with the fix backported, so compare with the fixed package versions in the table below, not only with the upstream version.
Debian
sudo apt update
sudo apt install --only-upgrade linux-image-amd64Ubuntu
sudo apt update
sudo apt install --only-upgrade linux-image-generic (or the installed flavour: linux-image-aws, -azure, -gcp, -virtual)RHEL, AlmaLinux, Rocky, Oracle
sudo dnf upgrade --refresh kernelFedora
sudo dnf upgrade --refresh kernelSUSE / openSUSE
sudo zypper refresh
sudo zypper update kernel-defaultAmazon Linux
sudo dnf upgrade --releasever=latest kernel kernel6.12Arch Linux
sudo pacman -SyuAlpine
apk update && apk upgrade linux-lts linux-virtFreeBSD
not LinuxGeneral update steps for every system are on the Linux and Unix & BSD pages; after updating, see which services to restart.
Fix status in Linux distributions
| Release | Package | Status | Fixed version / advisory |
|---|---|---|---|
| Debian 12 | linux | fixed | 6.1.176-1 |
| Debian 13 | linux | fixed | 6.12.94-1 |
| Debian testing | linux | fixed | 7.0.12-1 |
From the Debian security tracker, Ubuntu CVE tracker and Red Hat Security Data API, refreshed every few hours.
Sources
- https://git.kernel.org/stable/c/90e809376b0f0d1ddec2eec954aecdd2a5b40b0e
- https://git.kernel.org/stable/c/8654b5e2617819ff4f7c78071dfd0275e971a9b6
- https://git.kernel.org/stable/c/b64dd5f3b38911054cbcc570df617e3e8e75e562
- https://git.kernel.org/stable/c/31bbd4b87dd6701fa10e03ba7f6268e49e178d16
- https://git.kernel.org/stable/c/63203bd072b613c18c237b906b1c9d2dc4527337
- https://git.kernel.org/stable/c/15a0b3f33ffb6c78b3de6f69b026ceb09b973dd1
- https://git.kernel.org/stable/c/cfc3283859cfdeacadf80d5e6880bdf871ffeaa6
- https://git.kernel.org/stable/c/6bdc3023d62ed5c7d591f0eb27a5adb37fb892ae
- CVE-2026-63934 on CVE.org
- CVE-2026-63934 on NVD
Page generated automatically from official sources on 2026-11-03 18:05 UTC. Always confirm with your vendor's advisory.