# CVE-2025-32776: OpenRazer Vulnerable to Out of Bounds Read

> An attacker can trigger an out-of-bounds read in the OpenRazer kernel driver by writing crafted data, potentially leaking memory or causing a crash.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **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:** 15 Apr 2025
- **Updated:** 3 Nov 2025
- **Also known as:** DEBIAN-CVE-2025-32776, GHSA-835j-6976-46jx, UBUNTU-CVE-2025-32776

## What is CVE-2025-32776?

CVE-2025-32776 is a medium-severity memory corruption vulnerability in openrazer, published on 15 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

OpenRazer is an open source driver and user-space daemon to control Razer device lighting and other features on GNU/Linux. By writing specially crafted data to the `matrix_custom_frame` file, an attacker can cause the custom kernel driver to read more bytes than provided by user space. This data will be written into the RGB arguments which will be sent to the USB device. This issue has been patched in v3.10.2.

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

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


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

Upgrade to a fixed version.

## Is CVE-2025-32776 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-32776 is a medium-severity memory corruption vulnerability in openrazer, published on 15 Apr 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-32776 in the wild and no public exploit code.

Affected product: openrazer. 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-32776/ (Markdown: https://insights.sbomify.com/CVE-2025-32776/index.md)
```

## Sources

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

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