CVE-2023-25174 is a medium severity (CVSS 6.7) improper access control flaw in Intel Chipset Device Software. It needs local access and an authenticated user. Intel Chipset Device Software before version 10.1.19444.8378 is affected, so update to 10.1.19444.8378 or later and read Intel advisory SA-00928.
What's affected
The NVD record says Intel Chipset Device Software before version 10.1.19444.8378 is affected. That means 10.1.19444.8378 is the first version without the flaw, based on the record wording. The advisory is Intel SA-00928, linked from the record. Intel's site refused my automated fetch of that page, so I could not read its table of affected and fixed builds. Check it directly before you close the ticket.
The weakness class is CWE-284, improper access control. The CVSS vector in the record is local attack vector, high attack complexity, low privileges required and user interaction required. Confidentiality, integrity and availability impact are all rated high, which is what pushes the score to 6.7 despite the narrow conditions.
I could not read a second severity figure, so I have no conflict to report.
How to check if you're exposed
This is a Windows driver package, so the check is an inventory of installed versions. From PowerShell:
Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*,
HKLM:\Software\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\* |
Where-Object DisplayName -like "*Chipset*" |
Select-Object DisplayName, DisplayVersion
Any Intel Chipset Device Software entry below 10.1.19444.8378 needs the update. If you manage a fleet, pull the same data from your endpoint management tool instead of running it host by host. Laptops and workstations from the big OEMs often ship their own packaged copy of the chipset software, so the version shown may follow the OEM's numbering. In that case use the OEM's support page for the fixed build.
To see which of your own applications pull in affected components, run the free in-browser dependency scan at gold.safeguard.sh/scan.
What to do now
- Open Intel advisory SA-00928 and confirm the fixed version for your platform.
- Inventory the installed chipset software version on every Windows endpoint.
- Deploy Intel Chipset Device Software 10.1.19444.8378 or later, or the equivalent OEM package.
- Re-run the inventory after rollout and record the exceptions.
- Limit local administrator rights where you can, since the flaw needs a logged in user.
Why it matters
Improper access control means a component lets a caller do something the design did not intend. Here the caller is a local, already authenticated user, and the outcome is escalation of privilege. That is not a remote entry point, so it ranks below the bugs that expose a service to the internet.
It still matters in shared environments. Developer workstations, build agents, kiosks and terminal servers all have several users on one machine, and driver level bugs are a common way to move from a normal account to a stronger one. The record does not list it in CISA KEV, so there is no sign of known exploitation in that source.
Quick check
Does this need network access?
No. The record rates the attack vector as local, so an attacker needs an account on the machine first.
Which version fixes it?
The record says versions before 10.1.19444.8378 are affected. Confirm the exact fixed build in Intel SA-00928.
Sources
Last reviewed: 19 October 2026.