Safeguard
Vulnerability Analysis•

CVE-2022-25478: High PCI Config Access in Realtek RtsPer Driver

CVE-2022-25478 exposes PCI configuration space in Realtek card reader drivers. Update RtsPer to 10.0.22000.21355 and RtsUer to 10.0.22000.31274 or later.

Safeguard Security Team
3 min read

CVE-2022-25478 is a high severity flaw in Realtek's RtsPer and RtsUer card reader drivers for Windows, scored 7.8. They provide read and write access to the device's PCI configuration space. Fixed versions are RtsPer 10.0.22000.21355 and RtsUer 10.0.22000.31274. Update through your device maker.

What's affected

The record says Realtek's RtsPer driver for the PCIe card reader (RtsPer.sys) before version 10.0.22000.21355, and the RtsUer driver for the USB card reader (RtsUer.sys) before 10.0.22000.31274, give read and write access to the PCI configuration space of the device.

The researcher's write-up says the driver exposes control codes for reading and writing the configuration space, and that many laptop makers were affected because Realtek card readers are widely used. The same write-up lists several related CVEs, including CVE-2022-25480, and says Realtek released a first fix in April 2022, with later issues needing further fixes.

NVD scores the flaw 7.8 with a local vector and low privileges. The record has no weakness class assigned. Realtek's advisory report is linked in the record as a PDF, but I could not read it as text, so I rely on the record and the researcher's account.

The record's kev flag is false and I found no report of exploitation.

How to check if you're exposed

On Windows, check the driver versions installed:

driverquery /v /fo list | findstr /i "RtsPer RtsUer"

Or read the file version directly:

powershell -Command "(Get-Item C:\Windows\System32\drivers\RtsPer.sys).VersionInfo.FileVersion"
powershell -Command "(Get-Item C:\Windows\System32\drivers\RtsUer.sys).VersionInfo.FileVersion"

If RtsPer.sys reports a version older than 10.0.22000.21355, or RtsUer.sys older than 10.0.22000.31274, the driver is in the affected range. Machines without a Realtek card reader will not have these files.

Driver updates normally come from your laptop or PC maker, who package the Realtek driver, so check their support page too.

What to do now

  1. Query managed Windows machines for RtsPer.sys and RtsUer.sys versions.
  2. Install updated drivers through Windows Update or your device maker's support page.
  3. Re-check the file version after the update, since older packages can remain installed.
  4. Limit local logon rights on shared machines until the driver is updated.

Why it matters

Drivers run in the kernel, and the card reader driver exposed a device interface that ordinary users could open. Raw access to a device's PCI configuration space is a powerful primitive, since that space controls how the device is mapped and behaves.

The researcher's article describes how a set of such driver flaws can combine into kernel memory access from a normal user account. That combination is the reason a local flaw rated 7.8 still deserves attention on shared or high value machines.

For fleet owners, the lesson is about inventory. Peripheral drivers installed by the device maker are easy to miss in patch programs that focus on the operating system.

Quick check

Is this a remote flaw?

No. NVD records a local vector, so an attacker needs to run code on the machine, usually as a standard user.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.