CVE-2022-25479: Vulnerability in Realtek RtsPer driver for PCIe Card Reader (RtsPer.sys) before 10.0.22000.21355 and Realte...
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.
Security readout for executives and security teams
Plain-English summary
This CVE affects Realtek Windows card-reader drivers. A local, low-privileged user could cause the driver to leak kernel memory from stack and heap areas. The CVSS score is medium, but the availability impact is rated high. There is no source-provided evidence of active exploitation.
Executive priority
Treat as a managed endpoint hygiene issue, not an emergency. Prioritize broad driver inventory and updates, especially shared workstations, kiosks, labs, and environments where local users have limited trust.
Technical view
RtsPer.sys before 10.0.22000.21355 and RtsUer.sys before 10.0.22000.31274 are reported vulnerable. CVSS 3.1 is 6.1: local attack vector, low complexity, low privileges, no user interaction, low confidentiality impact, no integrity impact, high availability impact. CWE is listed as CWE-401.
Likely exposure
Exposure is most likely on Windows endpoints containing Realtek PCIe or USB card-reader drivers RtsPer.sys or RtsUer.sys below the fixed versions. The source bundle does not enumerate specific OEM devices, operating-system builds, or distribution channels.
Exploitation context
The CVE is not listed in CISA KEV, and the provided sources do not claim active exploitation. Public researcher material is referenced, so defenders should assume technical details are available, but avoid inferring real-world exploitation without additional evidence.
Researcher notes
The record describes kernel memory disclosure from both stack and heap in Realtek card-reader drivers. Public references include Realtek advisory material and researcher writeups. The provided data does not identify active exploitation, affected OEM models, or detection indicators.
Mitigation direction
Inventory endpoints for RtsPer.sys and RtsUer.sys.
Update RtsPer.sys to 10.0.22000.21355 or later.
Update RtsUer.sys to 10.0.22000.31274 or later.
Check Realtek and OEM guidance for approved driver packages.
Prioritize systems where untrusted local users can run code.
Validation and detection
Confirm driver file versions meet or exceed the fixed versions.
Verify Realtek PCIe or USB card-reader drivers are actually present.
Review endpoint management data for outdated driver packages.
Track remediation exceptions for devices lacking vendor-approved updates.
Monitor vendor advisories for revised affected-product information.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-401: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-401 · source CWE mapping
Missing Release of Memory after Effective Lifetime
Missing Release of Memory after Effective Lifetime represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.