RtsperApplication · Realtek

CVE-2022-25477

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

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 leaks driver logs that contain addresses of kernel mode objects, weakening KASLR.

Technical summary

dbcve analysis · high confidence

The Realtek RtsPer.sys (PCIe) and RtsUer.sys (USB) card reader drivers before versions 10.0.22000.21355 and 10.0.22000.31274 respectively leak kernel address information in driver-generated logs. This information disclosure allows local attackers to discover addresses of kernel mode objects, undermining KASLR protection and facilitating subsequent privilege escalation exploits.

MitigationUpdate Realtek card reader drivers (RtsPer.sys and RtsUer.sys) to versions 10.0.22000.21355 or later for PCIe readers and 10.0.22000.31274 or later for USB readers. Verify card reader functionality after update.

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

Affected products & versions

NVD · CPE data

RtsperApplication

Affected:< 10.0.22000.21355

RtsuerApplication

Affected:< 10.0.22000.31274

CVSS breakdown

From the vector

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

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

Am I affected?

dbcve checks

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

Identify if Realtek card reader drivers are installed

Open Device Manager, expand 'Memory technology devices' or 'Smart card readers', look for Realtek USB Card Reader or Realtek PCIe Card Reader entries. Alternatively, run 'driverquery /v | findstr -i rts' to list loaded Realtek drivers.

Affected if No Realtek card reader drivers are present, then the system is not affected by this specific vulnerability.
Locate the driver file version for RtsPer.sys (PCIe)

If a Realtek PCIe card reader is present, find RtsPer.sys in the Windows\System32\drivers\ folder. Right-click the file, select Properties, and view the File Version. Alternatively, run 'powershell (Get-Item C:\Windows\System32\drivers\RtsPer.sys).VersionInfo.FileVersion'

Affected if The installed version is lower than 10.0.22000.21355, indicating the system is vulnerable.
Locate the driver file version for RtsUer.sys (USB)

If a Realtek USB card reader is present, find RtsUer.sys in the Windows\System32\drivers\ folder. Right-click the file, select Properties, and view the File Version. Alternatively, run 'powershell (Get-Item C:\Windows\System32\drivers\RtsUer.sys).VersionInfo.FileVersion'

Affected if The installed version is lower than 10.0.22000.31274, indicating the system is vulnerable.
Query driver version via Windows Registry

Open Registry Editor and navigate to HKLM\SYSTEM\CurrentControlSet\Services\RtsPer or HKLM\SYSTEM\CurrentControlSet\Services\RtsUer. Check the ImagePath value to locate the driver file, then check the driver version as shown above.

Affected if Registry shows driver entries with versions below the safe thresholds.

The 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 these versions leak kernel addresses in driver logs.

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

Remediation

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 card reader drivers (RtsPer.sys and RtsUer.sys) to versions 10.0.22000.21355 or later for PCIe readers and 10.0.22000.31274 or later for USB readers. Verify card reader functionality after update.

Recommended fix High confidence

RtsPer.sys: 10.0.22000.21355 or later | RtsUer.sys: 10.0.22000.31274 or later

Identify which Realtek card reader driver is in use: RtsPer.sys (PCIe Card Reader) or RtsUer.sys (USB Card Reader)
Open Device Manager and expand 'Memory technology devices' or 'Smart card readers' to locate the Realtek card reader
Note the current driver version by right-clicking the device, selecting Properties, and viewing the Driver tab
Download the updated Realtek driver from the official Realtek website (www.realtek.com) or from your computer manufacturer if they provide customized drivers
Ensure the downloaded version is 10.0.22000.21355 or later for RtsPer, or 10.0.22000.31274 or later for RtsUer
Uninstall the current driver via Device Manager (right-click device > Uninstall device > check 'Delete the driver software for this device' if available)
Restart the system if prompted
Install the newly downloaded driver by running the installer or right-clicking the .inf file and selecting 'Install'

Caveat Driver updates typically do not introduce breaking changes; however, ensure backup of critical data before system restarts during uninstallation/installation

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

Fix this in Rtsper Scoped from the published advisory

Consultation2.0 h
Implementation2.0 h
Testing2.0 h
Review / QA1.0 h

7.0 hours of engineering $1,240

Get the upgrade done

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2022-25477 — 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

Primary sources

www.realtek.comVendor Advisory
gist.github.comThird Party Advisory
zwclose.github.io
nvd.nist.govNVD record

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2022-25477?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsUpgrade to 10.0.22000.21355 / 10.0.22000.31274 or later

Severity 5.5 Medium

Exploit likelihood EPSS, next 30 days 0.2%

Affects: Rtsper

Remediation

Need this fixed?

Fix this in Rtsper 7 hrs · Low

Typical engagement from $1,240

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2022-25477 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References