CVE-2025-8299
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.
NVD · uneditedRealtek rtl81xx SDK Wi-Fi Driver MgntActSet_TEREDO_SET_RS_PACKET Heap-based Buffer Overflow Local Privilege Escalation Vulnerability. This vulnerability allows local attackers to escalate privileges on affected installations of Realtek rtl81xx SDK Wi-Fi driver. An attacker must first obtain the ability to execute low-privileged code on the target system in order to exploit this vulnerability. The specific flaw exists within the MgntActSet_TEREDO_SET_RS_PACKET function. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a fixed-length heap-based buffer. An attacker can leverage this vulnerability to escalate privileges and execute arbitrary code in the context of SYSTEM. Was ZDI-CAN-25857.
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.
dbcve analysis · high confidenceA heap-based buffer overflow exists in the MgntActSet_TEREDO_SET_RS_PACKET function of the Realtek rtl81xx Wi-Fi driver SDK. The function fails to validate the length of user-supplied data before copying it into a fixed-size heap buffer, allowing an attacker with initial low-privileged code execution to overflow the buffer and achieve arbitrary code execution in SYSTEM context.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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.
NVD · CPE data< 1030.52.0325.2025CVSS 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.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
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.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Realtek rtl81xx driver presenceOpen Device Manager, expand Network adapters, and look for any Realtek USB Wi-Fi adapter entries (e.g., 802.11ac, 802.11n USB adapters) or check driver details for 'rtl81xx' or 'Realtek' Wi-Fi componentsAffected if A Realtek Wi-Fi USB adapter with the rtl81xx driver is installed on the system
-
Retrieve installed driver versionIn Device Manager, right-click the Realtek Wi-Fi adapter, select Properties, go to the Driver tab, and note the Driver Version string. Alternatively, run 'driverquery /v' or check the .sys file version in the driver directoryAffected if The driver version is earlier than 1030.52.0325.2025 (e.g., 1030.x.x.x below 1030.52.0325.2025, or any version with a different numbering scheme that is below this threshold)
-
Verify TEREDO tunneling interface statusOpen a command prompt and run 'netsh interface teredo show state' to check if the TEREDO interface is enabled or configured on the systemAffected if TEREDO tunneling is enabled and actively used, as the vulnerable function MgntActSet_TEREDO_SET_RS_PACKET processes TEREDO-related packets
-
Confirm low-privileged code execution capabilityReview system hardening status and check if non-privileged users have the ability to interact with the driver interface (e.g., through debugging tools, driver APIs, or signed driver exploitation tools)Affected if A low-privileged user or process can interact with the driver or trigger the vulnerable code path, which is required as the initial attack vector before privilege escalation
The system is affected if it has a Realtek rtl81xx Wi-Fi USB driver installed with a version earlier than 1030.52.0325.2025, TEREDO tunneling is in use, and an attacker could achieve initial low-privileged code execution to trigger the buffer overflow.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor data1030.52.0325.2025
Apply the vendor-supplied patch or updated Realtek rtl81xx driver once available. As an interim measure, restrict or monitor access to the affected driver interface and minimize the attack surface for local privilege escalation vectors.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-8299 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-8299 in production — separate from our analysis above.
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.
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.
- 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