CVE-2026-63934
Last modified
CVE-2026-63934 is a high-severity vulnerability rated 7.1/10 on the CVSS scale. 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. EPSS estimates a 0.21% chance of exploitation in the next 30 days.
Description
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 3.9, < 5.10.259 | — |
| Linux | Linux Kernel | >= 5.11, < 5.15.210 | — |
| Linux | Linux Kernel | >= 5.16, < 6.1.176 | — |
| Linux | Linux Kernel | >= 6.2, < 6.6.143 | — |
| Linux | Linux Kernel | >= 6.7, < 6.12.93 | — |
| Linux | Linux Kernel | >= 6.13, < 6.18.35 | — |
| Linux | Linux Kernel | >= 6.19, < 7.0.12 | — |
| Linux | Linux Kernel | 7.1 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-63934?
How severe is CVE-2026-63934?
How do I fix CVE-2026-63934?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-63929In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-6393The BetterDocs plugin for WordPress is vulnerable to Missing…4.3
- CVE-2026-63930In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-63931In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-63932In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-63933In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-63935In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-63936In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-63937In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-63938In the Linux kernel, the following vulnerability has been re…9.3
- CVE-2026-63939In the Linux kernel, the following vulnerability has been re…9.3
- CVE-2026-6394The Nexa Blocks – Gutenberg Blocks, Page Builder for Gutenbe…5.4
Are you affected by CVE-2026-63934?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
