CVE-2025-43993
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 · uneditedDell Wireless 5932e and Qualcomm Snapdragon X62 Firmware and GNSS/GPS Driver, versions prior to 3.2.0.22 contain an Unquoted Search Path or Element vulnerability. A low privileged attacker with local access could potentially exploit this vulnerability, leading to Code Execution.
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 confidenceThis is an unquoted service path vulnerability in Dell Wireless 5932e and Qualcomm Snapdragon X62 firmware and GNSS/GPS drivers. A low-privileged local attacker could place a malicious executable in an unquoted path that gets executed by a higher-privilege service, achieving code execution.
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< 3.2.0.22< 3.2.0.22< 3.2.0.22< 3.2.0.22< 3.2.0.22< 3.2.0.22< 3.2.0.22< 3.2.0.22CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Dell device modelOpen System Properties (win+r, sysdm.cpl) or run 'systeminfo' in Command Prompt to confirm the exact Dell model number (e.g., Latitude 5350, Latitude 5450, Latitude 5550, Latitude 7030, Latitude 7350, Pro Rugged 13, Pro Rugged 14).Affected if The device model matches one of the affected products: Dell Pro Rugged 13 Ra13250, Pro Rugged 14 Rb14250, Latitude 5350, Latitude 5450, Latitude 5550, Latitude 7030 Rugged Extreme, Latitude 7350, or Latitude 7350 Detachable.
-
Check the Dell Wireless 5932e firmware versionOpen Device Manager, expand 'Network adapters', locate 'Dell Wireless 5932e', right-click and select Properties, then view the Driver version. Alternatively, run 'wmic path win32_pnpsigneddriver where "DeviceName like '%5932e%'" get DeviceName,DriverVersion' in Command Prompt.Affected if The firmware version is below 3.2.0.22.
-
Check the Qualcomm Snapdragon X62 firmware versionOpen Device Manager, expand 'Network adapters' or 'Modems', look for entries containing 'Snapdragon X62', right-click and view Driver version. On systems with Qualcomm drivers, check under 'Qualcomm Snapdragon X62' in Device Manager.Affected if The Qualcomm Snapdragon X62 driver/firmware version is below 3.2.0.22.
-
Check the GNSS/GPS driver versionOpen Device Manager, expand 'Location Sensors' or 'Human Interface Devices', look for 'GNSS' or 'GPS' driver entries (may appear under 'Dell GNSS Sensor' or 'Qualcomm GNSS'), right-click and view the Driver version.Affected if The GNSS/GPS driver version is below 3.2.0.22.
-
Verify the overall firmware version using Dell toolsRun 'DellSupportAssist' or access the Dell Update utility, navigate to the Firmware or BIOS section, and review the installed versions for Wireless, GNSS, and Snapdragon components. Compare each version number to 3.2.0.22.Affected if Any of the wireless, Snapdragon X62, or GNSS components report a version lower than 3.2.0.22.
A user is affected if they own one of the listed Dell devices AND any of the Dell Wireless 5932e, Qualcomm Snapdragon X62, or GNSS/GPS components are running a firmware or driver version below 3.2.0.22.
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.
dbcve · scoped3.2.0.22
Update the Dell Wireless 5932e and Qualcomm Snapdragon X62 firmware and GNSS/GPS drivers to version 3.2.0.22 or later to remediate the unquoted service path vulnerability.
Firmware version 3.2.0.22 for Dell Wireless 5932e and Qualcomm Snapdragon X62
- Identify the exact system model and current firmware version using Dell SupportAssist, Dell Command | Update, or BIOS information
- Navigate to Dell support website (www.dell.com) and enter the system Service Tag or model number
- Locate theDrivers & Downloadssection for the system
- Find the wireless/wireless network or GNSS/GPS driver/firmware category
- Download the firmware version 3.2.0.22 or later for Dell Wireless 5932e or Qualcomm Snapdragon X62
- Review the update documentation and ensure the system is connected to AC power
- Execute the firmware update utility as an administrator
- Allow the system to reboot as required by the update process
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-43993 — 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-43993 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