Skip to main content
No exploitation reportedFix available

CVE-2022-23467

No exploitation reported by the sources we read.

  • Published2022-12-05
  • Fixed in3.5.1
  • WeaknessCWE-125

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

OpenRazer is an open source driver and user-space daemon to control Razer device lighting and other features on GNU/Linux. Using a modified USB device an attacker can leak stack addresses of the `razer_attr_read_dpi_stages`, potentially bypassing KASLR. To exploit this vulnerability an attacker would need to access to a users keyboard or mouse or would need to convince a user to use a modified device. The issue has been patched in v3.5.1. Users are advised to upgrade and should be reminded not to plug in unknown USB devices.

Timeline

dates in UTC
  1. 2022-12-0520:15CVE publishedNVD

Versions per branch

NVD
Openrazer project openrazer
BranchAffectedFixed in
3.5< 3.5.13.5.1

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As GitHub_M, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • openrazer
    Affected
    • = < 3.5.1no fix stated

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2022-12-05

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • openrazerUbuntu:26.10all versions · no fixed version listed
  • openrazerUbuntu:26.04:LTSall versions · no fixed version listed
  • openrazerUbuntu:25.10all versions · no fixed version listed
  • openrazerUbuntu:24.04:LTSall versions · no fixed version listed
  • openrazerUbuntu:22.04:LTSall versions · no fixed version listed
  • openrazerUbuntu:20.04:LTSall versions · no fixed version listed
  • openrazerDebian:14all versions · fixed in 3.5.1+dfsg-1
  • openrazerDebian:13all versions · fixed in 3.5.1+dfsg-1

10 more package ranges on OSV.dev

Full record on NVD

Fix

  1. Update Openrazer project openrazer to 3.5.1

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

  • CISA-ADPSSVC decisionnone2025-04-23
  • CNACVSS 3.14.4known since 2026-10-23
  • NVDCVSS 3.14.6read 2026-10-23
  • CNAweakness (CWE)CWE-125known since 2026-10-23
  • FIRST EPSSEPSS score0.4 %2026-11-08
  • OSVaffected packages—

Identifiers

  • EUVD-2022-28533same flawENISA EUVD · LicenseRef-ENISA-legal-notice
  • DLA-4136-1advisory covering several CVEsDebian · LicenseRef-unstated

Technical details

CVSS v3 Vector
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Published
2022-12-05
Last Modified
2026-06-17
NVD status
Modified

Frequently asked questions

What is CVE-2022-23467?

OpenRazer is an open source driver and user-space daemon to control Razer device lighting and other features on GNU/Linux. Using a modified USB device an attacker can leak stack addresses of the `razer_attr_read_dpi_stages`, potentially bypassing KASLR. To exploit this vulnerability an attacker would need to access to a users keyboard or mouse or would need to convince a user to use a modified device. The issue has been patched in v3.5.1. Users are advised to upgrade and should be reminded not to plug in unknown USB devices.

Is CVE-2022-23467 actively exploited?

Active exploitation of CVE-2022-23467 has not been confirmed. Its EPSS score was 0.4% on 2026-11-08, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2022-23467?

CVE-2022-23467 has a CVSS v3 base score of 4.6 (MEDIUM severity), with vector string CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N.

Running openrazer? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record