CVE-2025-32776 | OpenRazer Vulnerable to Out of Bounds Read

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.

Published: 2025-04-15 Last update: 2026-04-15 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2025-32776 is rated Low Risk (27.1/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.05%). Mandatory action: Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-32776

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-24 0.11% 0.05% -0.07%
2 2026-02-09 0.01% 0.11% +0.10%
3 2025-04-16 0.01%

Full EPSS history (3 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-32776

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.5 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
1.8 3.6 [email protected]

Weakness enumeration for CVE-2025-32776

OS Trackers for CVE-2025-32776

vendor priority summary link
alpine medium CVE-2025-32776: 1 source package rows (openrazer); 8 state rows across 2 repos (3.22-community, edge-community); fixed 0, open 8. https://security.alpinelinux.org/vuln/CVE-2025-32776
debian not yet assigned CVE-2025-32776 not yet assigned priority: Debian including 1 source packages (openrazer), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2025-32776
ubuntu medium CVE-2025-32776 medium priority: Ubuntu including 1 source packages (openrazer), 7 status rows across 7 suites (focal, jammy, noble, oracular, plucky, questing, upstream): needs-triage 5, ignored 2. https://ubuntu.com/security/CVE-2025-32776

Affected software / configurations for CVE-2025-32776

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-32776

cvelogic Threat Intelligence