CVE-2026-64495
CVE CVE-2026-64495EUVD EUVD-2026-48839Published 2026-07-25T08:51:52.000Z
What the advisory describes
In the Linux kernel, the following vulnerability has been resolved: iio: gyro: bmg160: bail out when bandwidth/filter is not in table bmg160_get_filter() walks bmg160_samp_freq_table[] looking for the entry matching the bw_bits value read from the chip: for (i = 0; i < ARRAY_SIZE(bmg160_samp_freq_table); ++i) { if (bmg160_samp_freq_table[i].bw_bits == bw_bits) break; } *val = bmg160_samp_freq_table[i].filter; If no entry matches, i ends up equal to the array size and the next line reads one slot past the end. bmg160_set_filter() has the same shape, driven by 'val' instead of bw_bits. smatch flags both: drivers/iio/gyro/bmg160_core.c:204 bmg160_get_filter() error: buffer overflow 'bmg160_samp_freq_table' 7 <= 7 drivers/iio/gyro/bmg160_core.c:222 bmg160_set_filter() error: buffer overflow 'bmg160_samp_freq_table' 7 <= 7 Return -EINVAL when no entry matches. The set_filter() path is reachable from userspace via the sysfs in_anglvel_filter_low_pass_3db_frequency interface, so userspace can trivially trigger the out-of-bounds read with a value that is not in bmg160_samp_freq_table[].filter.
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 patch: 6.18.39; 22b46c45fb9be8ec1fcb4d9b74810e6a20ff67cc <8320c77e67382d5d55d77043a5f60a867d408a2b; 22b46c45fb9be8ec1fcb4d9b74810e6a20ff67cc <77e56ebb1786f4296afd5fa46975a989b285ae65; patch: 7.2-rc1; 22b46c45fb9be8ec1fcb4d9b74810e6a20ff67cc <029481cddb98697716f4bf3021d035eaf2ca0e1f; patch: 5.10.261; patch: 7.1.4; 22b46c45fb9be8ec1fcb4d9b74810e6a20ff67cc <7bbf02b63961fc1768c9c654392c11f2077d4c59; 22b46c45fb9be8ec1fcb4d9b74810e6a20ff67cc <8d202515baea4e2e3be448d1590099af28f2346d; 22b46c45fb9be8ec1fcb4d9b74810e6a20ff67cc <1dc3a833be11e5d503038e3c701745fd0e03903c; 22b46c45fb9be8ec1fcb4d9b74810e6a20ff67cc <6c8675468862161d1c59130266852b66867d3861; patch: 6.1.178; patch: 0; patch: 6.6.145; patch: 5.15.212; patch: 6.12.96; 22b46c45fb9be8ec1fcb4d9b74810e6a20ff67cc <d85ee50f58dd83fe74f6d0bf8bd345c657b216e8; 3.18
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
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage 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.