CVE-2022-25480 is a high severity out-of-bounds write in Realtek's RtsPer and RtsUer card reader drivers for Windows, scored 7.8. It writes to kernel memory beyond the request's system buffer. 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 (RtsPer.sys) before 10.0.22000.21355 and RtsUer driver (RtsUer.sys) before 10.0.22000.31274 allow writing to kernel memory beyond the SystemBuffer of the I/O request packet. SystemBuffer is the kernel buffer Windows allocates for a driver request that uses buffered I/O.
The researcher's article treats this alongside a family of related flaws in the same drivers, among them CVE-2022-25478 and later CVE-2024-40431 and CVE-2024-40432. The article states Realtek shipped a first fix in April 2022 and that follow-up issues required further updates, so the minimum safe version you aim for matters.
NVD scores the flaw 7.8, with a local vector, low privileges and high impact to confidentiality, integrity and availability. Realtek's advisory report is linked as a PDF in the record, but I could not extract text from it, so the version numbers above come from NVD's record.
No exploitation in the wild is reported in the record, and kev is false.
Weakness class per the record: CWE-787.
How to check if you're exposed
Read the installed driver versions on each Windows machine:
powershell -Command "(Get-Item C:\Windows\System32\drivers\RtsPer.sys).VersionInfo.FileVersion"
powershell -Command "(Get-Item C:\Windows\System32\drivers\RtsUer.sys).VersionInfo.FileVersion"
A missing file means the machine has no matching Realtek reader driver. A version below 10.0.22000.21355 for RtsPer, or below 10.0.22000.31274 for RtsUer, is in the affected range.
Do not stop at these thresholds. The researcher's article names later issues in the same driver family fixed in newer releases, so install the newest package your device maker offers.
What to do now
- Inventory RtsPer.sys and RtsUer.sys versions across managed Windows devices.
- Deploy updated drivers from Windows Update or the device maker's support page.
- Confirm the file version after install, and remove old driver packages from the driver store if your tooling allows.
- Treat shared machines and kiosks first, since the attacker needs local code execution.
Why it matters
The weakness is an out-of-bounds write (CWE-787). The driver accepted a request whose offsets let it write past the end of the buffer the operating system had provided. In the kernel, that kind of write can be turned into control of the machine by someone who started as a normal user.
Kernel drivers from peripheral vendors are a recurring source of local privilege escalation. They ship preinstalled by device makers, they are rarely audited by the buyer and they update slowly.
A healthy response is to track driver versions as an asset class and to use update channels that actually deliver vendor driver fixes, rather than assuming operating system updates cover them.
Quick check
What is the minimum fixed version?
According to the record, RtsPer 10.0.22000.21355 and RtsUer 10.0.22000.31274. Later flaws in the same drivers were fixed after that, so prefer the newest driver your maker offers.
Sources
- Safeguard Gold entry for CVE-2022-25480
- Researcher write-up: Vulnerabilities of Realtek SD card reader driver, part 1
Last reviewed: 19 October 2026.