dbcve.org
RtsperApplication · Realtek

CVE-2022-25479

MEDIUM · 5.5 CVSS v3.1 Published 2024-07-02
Fix available
A fix is available. Upgrade to 10.0.22000.21355 / 10.0.22000.31274 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Vulnerability in Realtek RtsPer driver for PCIe Card Reader (RtsPer.sys) before 10.0.22000.21355 and Realtek RtsUer driver for USB Card Reader (RtsUer.sys) before 10.0.22000.31274 allows for the leakage of kernel memory from both the stack and the heap.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Kernel memory disclosure vulnerability in Realtek card reader drivers (RtsPer.sys for PCIe and RtsUer.sys for USB). The drivers leak kernel memory from both stack and heap, potentially exposing sensitive kernel data structures, addresses, and other information that could aid in privilege escalation or bypassing security mechanisms like KASLR.

MitigationUpdate Realtek RtsPer.sys to version 10.0.22000.21355 or later, and RtsUer.sys to version 10.0.22000.31274 or later. Apply through vendor patch management or driver update mechanisms.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
RtsperApplication
Affected:< 10.0.22000.21355
RtsuerApplication
Affected:< 10.0.22000.31274

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if RtsPer.sys driver is present
    Open PowerShell and run: Get-ChildItem -Path C:\Windows\System32\Drivers -Filter RtsPer.sys -ErrorAction SilentlyContinue | Select-Object FullName, Length
    Affected if The driver file exists on the system (driver is installed)
  2. Get installed version of RtsPer.sys
    In PowerShell, run: (Get-Item 'C:\Windows\System32\Drivers\RtsPer.sys').VersionInfo | Select-Object FileVersion, ProductVersion, FileDescription
    Affected if The returned version is lower than 10.0.22000.21355 or the driver does not exist
  3. Check if RtsUer.sys driver is present
    Open PowerShell and run: Get-ChildItem -Path C:\Windows\System32\Drivers -Filter RtsUer.sys -ErrorAction SilentlyContinue | Select-Object FullName, Length
    Affected if The driver file exists on the system (driver is installed)
  4. Get installed version of RtsUer.sys
    In PowerShell, run: (Get-Item 'C:\Windows\System32\Drivers\RtsUer.sys').VersionInfo | Select-Object FileVersion, ProductVersion, FileDescription
    Affected if The returned version is lower than 10.0.22000.31274 or the driver does not exist

A system is affected if either RtsPer.sys version is below 10.0.22000.21355 or RtsUer.sys version is below 10.0.22000.31274, as both drivers contain the kernel memory disclosure vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.0.22000.21355 / 10.0.22000.31274 or later
Fixed in 10.0.22000.2135510.0.22000.31274
Interim mitigation

Update Realtek RtsPer.sys to version 10.0.22000.21355 or later, and RtsUer.sys to version 10.0.22000.31274 or later. Apply through vendor patch management or driver update mechanisms.

Recommended fix High confidence

RtsPer: 10.0.22000.21355 or later; RtsUer: 10.0.22000.31274 or later

  1. Identify which Realtek card reader driver is installed on the system: RtsPer.sys (PCIe Card Reader) or RtsUer.sys (USB Card Reader)
  2. Check the current driver version by opening Device Manager, expanding 'Memory technology devices' or 'Smart card readers', right-clicking the Realtek device, selecting Properties, then viewing the Driver tab
  3. Navigate to the official Realtek website (www.realtek.com) and locate the download section for Card Reader drivers
  4. Download the latest RtsPer or RtsUer driver version depending on your device type, ensuring the version is 10.0.22000.21355 or higher for RtsPer, or 10.0.22000.31274 or higher for RtsUer
  5. Run the installer and follow the on-screen prompts to update the driver
  6. Restart the computer when prompted to complete the installation
  7. Verify the installed version matches or exceeds the fixed versions by checking the driver properties again

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Rtsper Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-25479 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-25479 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data