dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2025-14252

HIGH · 7.8 CVSS v3.1 Published 2025-12-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
An Improper Access Control vulnerability in Advantech SUSI driver (susi.sys) allows attackers to read/write arbitrary memory, I/O ports, and MSRs, resulting in privilege escalation, arbitrary code execution, and information disclosure. This issue affects Advantech SUSI: 5.0.24335 and prior.

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 confidence

Improper Access Control in Advantech SUSI kernel driver (susi.sys) allows unvalidated callers to read/write arbitrary memory, I/O ports, and Model Specific Registers (MSRs), enabling privilege escalation from user mode to kernel mode, arbitrary code execution, and sensitive information disclosure.

MitigationApply vendor-supplied patch/update to Advantech SUSI driver version 5.0.24335 or prior; prior to patching, restrict or monitor access to the susi.sys driver and validate application whitelisting policies.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate the SUSI kernel driver file
    Search for susi.sys on the system using PowerShell: Get-ChildItem -Path C:\Windows\System32\drivers -Recurse -Filter "susi.sys" -ErrorAction SilentlyContinue | Select-Object FullName, Length, LastWriteTime
    Affected if The file susi.sys exists on the system, indicating the driver may be installed
  2. Determine the driver file version
    Right-click susi.sys in File Explorer, select Properties, then view the Details tab to see the Product Version, or use PowerShell: (Get-Item "C:\Windows\System32\drivers\susi.sys").VersionInfo | Select-Object ProductVersion, FileVersion
    Affected if The version is 5.0.24335 or prior, or if no version number is displayed (older/unpatched driver)
  3. Verify if the driver is loaded
    Open an elevated PowerShell prompt and run: Get-Process -Module -ErrorAction SilentlyContinue | Where-Object {$_.ModuleName -eq "susi.sys"} or check driver status with: sc.exe query susi
    Affected if The susi.sys driver is currently loaded and running on the system
  4. Check driver access permissions
    Use PowerShell with Sysinternals accesschk: accesschk.exe -kv "\Device\susi" or inspect driver device objects via registry at HKLM\SYSTEM\CurrentControlSet\Services\susi for Start and Type values
    Affected if The driver is accessible to unprivileged users (non-admin accounts can interact with the driver device)

A user is affected if susi.sys version 5.0.24335 or prior is installed and the driver is loaded or loadable on their Windows system.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied patch/update to Advantech SUSI driver version 5.0.24335 or prior; prior to patching, restrict or monitor access to the susi.sys driver and validate application whitelisting policies.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-14252 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-14252 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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