CVE-2025-32776 json
OpenRazer Vulnerable to Out of Bounds Read
published last yr. modified 4mo ago also EUVD-2025-14704
- cvss
- 5.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 8%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- openrazer_project openrazer 3.10.2
- openrazer Debian 12 3.5.1+dfsg-2+deb12u1
- openrazer Debian 14, Debian 13 3.10.2+dfsg-1
debian advisories DEBIAN-CVE-2025-32776
Is CVE-2025-32776 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.19% chance of exploitation in the next 30 days, higher than 8% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
Affected products
- openrazer openrazer
Classification
- Weakness
-
- CWE-125 Out-of-bounds Read
References
- github.com /openrazer/openrazer/commit/57610511d2548eda66999eaed5aa4517e89d6d39
- github.com /openrazer/openrazer/commit/d869abd20995b4931795e1cde54d4ac84d9ca62f
- github.com /openrazer/openrazer/security/advisories/GHSA-835j-6976-46jx
- github.com /openrazer/openrazer/issues/2433
- lists.debian.org /debian-lts-announce/2025/04/msg00032.html
Sources
- CVE List CVE-2025-32776
- NVD CVE-2025-32776
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.