# CVE-2025-39719: iio: imu: bno055: fix OOB access of hw_xlate array

> Out-of-bounds array access in the BNO055 IMU driver could lead to memory corruption or system crashes.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Sep 2025
- **Updated:** 12 May 2026
- **Also known as:** AZL-67022, BELL-CVE-2025-39719, DEBIAN-CVE-2025-39719, GHSA-v6h8-r25q-3mjf, ROOT-OS-DEBIAN-12-CVE-2025-39719, ROOT-OS-DEBIAN-13-CVE-2025-39719, ROOT-OS-UBUNTU-2404-CVE-2025-39719, UBUNTU-CVE-2025-39719

## What is CVE-2025-39719?

CVE-2025-39719 is a high-severity memory corruption vulnerability in Debian Debian Linux, published on 5 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2025-39719?

It affects 2 products.


Products: Debian Debian Linux, Linux kernel.

## How do I fix CVE-2025-39719?

Apply the vendor's patch.

## Is CVE-2025-39719 being exploited?

There is no known exploitation of CVE-2025-39719 in the wild and no public exploit code.

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-39719 and fix it if it is affected.

What it is: CVE-2025-39719 is a high-severity memory corruption vulnerability in Debian Debian Linux, published on 5 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-39719 in the wild and no public exploit code.

Affected product: Debian Debian Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-39719/ (Markdown: https://insights.sbomify.com/CVE-2025-39719/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-39719
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-39719
- OSV: https://osv.dev/vulnerability/CVE-2025-39719

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-39719/
Summaries are generated and may contain mistakes; the official description above is the record.