# CVE-2022-25479: Information disclosure in n/a

> A vulnerability in Realtek card reader drivers allows attackers to leak kernel memory from the stack and heap, potentially exposing sensitive data.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Jul 2024
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-7vph-xj83-rw6v

## What is CVE-2022-25479?

CVE-2022-25479 is a medium-severity vulnerability in n/a, published on 2 Jul 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-401 (Missing Release of Memory after Effective Lifetime)

## Which versions are affected by CVE-2022-25479?

It affects 2 products.


Products: Realtek Rtsper, Realtek Rtsuer.

## How do I fix CVE-2022-25479?

No fix has been published for CVE-2022-25479 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-25479 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-25479 exists.

Public exploit code:

- CVE-2024-40431+CVE-2022-25479 chain for EOP(DATA ONLY ATTACK)  (github_poc): https://github.com/SpiralBL0CK/CVE-2024-40431-CVE-2022-25479-EOP-CHAIN

## Other vulnerabilities in n/a

- [CVE-2022-25478](https://insights.sbomify.com/CVE-2022-25478/): Security feature bypass in n/a (high 7.8)
- [CVE-2022-25480](https://insights.sbomify.com/CVE-2022-25480/): Memory corruption in n/a (high 7.8)
- [CVE-2022-25477](https://insights.sbomify.com/CVE-2022-25477/): Information disclosure in n/a (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-25479 and fix it if it is affected.

What it is: CVE-2022-25479 is a medium-severity vulnerability in n/a, published on 2 Jul 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-25479 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-25479/ (Markdown: https://insights.sbomify.com/CVE-2022-25479/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-25479
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-25479
- OSV: https://osv.dev/vulnerability/CVE-2022-25479

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-25479/
Summaries are generated and may contain mistakes; the official description above is the record.