CVE-2025-39719: iio: imu: bno055: fix OOB access of hw_xlate array
In the Linux kernel, the following vulnerability has been resolved:
iio: imu: bno055: fix OOB access of hwxlate array
Fix a potential out-of-bounds array access of the hwxlate array in bno055.c.
In bno055getregmask(), hwxlate was iterated over the length of the vals array instead of the length of the hwxlate array. In the case of bno055gyrscale, the vals array is larger than the hwxlate 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 hwxlate array.
By adding a new hwxlatelen field to the bno055sysfsattr, we can be sure we are iterating over the correct length.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.107-1Fixed in 6.12.113-1Fixed in 7.2.12-1Fixed in 7.2.13-1
Event History
Frequently Asked Questions
What is the severity of CVE-2025-39719?
CVE-2025-39719 is classified as a medium severity vulnerability due to the potential for out-of-bounds memory access.
How do I fix CVE-2025-39719?
To fix CVE-2025-39719, you should update the Linux kernel to the latest stable version that includes the patch for this vulnerability.
What impact does CVE-2025-39719 have on affected systems?
CVE-2025-39719 can lead to undefined behavior, which may result in crashes or potential system compromise.
Which versions of the Linux kernel are affected by CVE-2025-39719?
CVE-2025-39719 affects various versions of the Linux kernel prior to the patch being applied for the bno055 driver.
Is CVE-2025-39719 exploitative in nature?
Yes, CVE-2025-39719 can be exploited if an attacker can interact with the affected component, leading to potential code execution.