CVE-2026-63934

CVE CVE-2026-63934EUVD EUVD-2026-45707Published 2026-07-19T14:55:32.000Z

What the advisory describes

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.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

• Linux — Linux 3.9; 9dbf091da080508e9f632d307f357beb79a0766b <31bbd4b87dd6701fa10e03ba7f6268e49e178d16; 9dbf091da080508e9f632d307f357beb79a0766b <6bdc3023d62ed5c7d591f0eb27a5adb37fb892ae; 9dbf091da080508e9f632d307f357beb79a0766b <8654b5e2617819ff4f7c78071dfd0275e971a9b6; patch: 6.6.143; patch: 0; patch: 5.10.259; patch: 6.1.176; patch: 7.1; patch: 6.18.35; 9dbf091da080508e9f632d307f357beb79a0766b <b64dd5f3b38911054cbcc570df617e3e8e75e562; patch: 7.0.12; patch: 6.12.93; 9dbf091da080508e9f632d307f357beb79a0766b <15a0b3f33ffb6c78b3de6f69b026ceb09b973dd1; patch: 5.15.210; 9dbf091da080508e9f632d307f357beb79a0766b <63203bd072b613c18c237b906b1c9d2dc4527337; 9dbf091da080508e9f632d307f357beb79a0766b <90e809376b0f0d1ddec2eec954aecdd2a5b40b0e; 9dbf091da080508e9f632d307f357beb79a0766b <cfc3283859cfdeacadf80d5e6880bdf871ffeaa6

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

• Linux — Linux

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.