iio: imu: bno055: fix OOB access of hw_xlate array
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 399b883ec828e436f1a721bf8551b4da8727e65b, Kernel 4808ca3aa30ae857454d0b41d2d0bf161a312b45, Kernel 50e823a23816b792daf6e8405f8d6045952bb90e and 2 more.
In the Linux kernel, the following vulnerability has been resolved: iio: imu: bno055: fix OOB access of hw_xlate array Fix a potential out-of-bounds array access of the hw_xlate array in bno055.c. In bno055_get_regmask(), hw_xlate was iterated over the length of the vals array instead of the length of the hw_xlate array. In the case of bno055_gyr_scale, the vals array is larger than the hw_xlate array, so this could result in an out-of-bounds access. In practice, this shouldn't happen though because a match should always be found which breaks out of the for loop before it iterates beyond the end of the hw_xlate array. By adding a new hw_xlate_len field to the bno055_sysfs_attr, we can be sure we are iterating over the correct length.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.1, >=4aefe1c2bd0cb0223130671d459cd16efa3d3462 <399b883ec828e436f1a721bf8551b4da8727e65b, >=4aefe1c2bd0cb0223130671d459cd16efa3d3462 <4808ca3aa30ae857454d0b41d2d0bf161a312b45, >=4aefe1c2bd0cb0223130671d459cd16efa3d3462 <50e823a23816b792daf6e8405f8d6045952bb90e, >=4aefe1c2bd0cb0223130671d459cd16efa3d3462 <5c2b601922c064f7be70ae8621277f18d1ffec59, >=4aefe1c2bd0cb0223130671d459cd16efa3d3462 <a0691ab6334f1769acc64ea9e319414a682ff45d | 399b883ec828e436f1a721bf8551b4da8727e65b, 4808ca3aa30ae857454d0b41d2d0bf161a312b45, 50e823a23816b792daf6e8405f8d6045952bb90e, 5c2b601922c064f7be70ae8621277f18d1ffec59, a0691ab6334f1769acc64ea9e319414a682ff45d |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket