CVE-2025-60419
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 · uneditedAn issue was discovered in the NDIS Usermode IO driver (RtkIOAC60.sys, version 6.0.5600.16348) allowing local authenticated attackers to send a crafted IOCTL request to the driver to cause a denial of service.
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 · moderate confidenceA vulnerability in the NDIS Usermode IO driver (RtkIOAC60.sys version 6.0.5600.16348) allows local authenticated attackers to send a crafted IOCTL (I/O Control) request to the driver, causing a denial of service. The vulnerability stems from insufficient input validation in the IOCTL handler, allowing malformed requests to crash the driver or the system.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/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.
-
Locate the RtkIOAC60.sys driver fileSearch for RtkIOAC60.sys in system driver directories such as C:\Windows\System32\drivers\ and C:\Windows\System32\DriverStore\Affected if The file exists on the system - the driver is installed and could be vulnerable
-
Verify the driver file versionRight-click the RtkIOAC60.sys file, select Properties, and check the File Version field under the Details tab. Alternatively, run: powershell "(Get-Item 'C:\Windows\System32\drivers\RtkIOAC60.sys').VersionInfo.FileVersion"Affected if The version is 6.0.5600.16348 exactly, indicating this is the vulnerable driver version
-
Determine if the driver is loadedOpen Command Prompt as Administrator and run: sc query RtkIOAC60 or check Device Manager under Network adapters or System devices for a Realtek or NDIS IO driverAffected if The driver shows as RUNNING or STARTED - the vulnerable code is active and processing IOCTL requests
-
Check for suspicious IOCTL activityEnable ETW tracing or use a kernel debugger to monitor IOCTL codes sent to RtkIOAC60.sys. Look for unexpected or repeated IOCTL requests from user-mode applicationsAffected if Unusual IOCTL patterns are observed, indicating possible exploitation attempts
-
Identify authenticated local usersReview local user accounts and group memberships on the system using Computer Management > Local Users and GroupsAffected if Untrusted or unauthorized local users have access to log into the system, as the attacker needs authenticated access
The system is affected if RtkIOAC60.sys version 6.0.5600.16348 is installed and running, allowing a local authenticated user to send malicious IOCTL requests and cause a denial of service.
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 dataApply the vendor patch for RtkIOAC60.sys when available, or disable/remove the driver if unnecessary. Restrict user access to systems with this driver and monitor for suspicious IOCTL activity.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-60419 — 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-60419 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