CVE-2023-25777 is a high severity (CVSS 7.9) improper access control flaw in Intel Thunderbolt DCH drivers for Windows. An authenticated local user could escalate privileges. Versions before 88 are affected, so update the driver to version 88 or later and read Intel advisory SA-00851.
What's affected
The record says Intel Thunderbolt DCH drivers for Windows before version 88 are affected. The reference is Intel advisory SA-00851. Intel's site denied my automated request, so the fixed version here is the one in the NVD wording and you should confirm it in the advisory.
The weakness is CWE-284, improper access control. The vector in the record is local, low complexity, low privileges, no user interaction, with a changed scope. The changed scope is why the score reaches 7.9 even though the confidentiality and integrity impacts are rated only low: the availability impact is high and the effect can cross a security boundary.
Only Windows systems with Thunderbolt hardware and this driver are relevant. Machines without Thunderbolt ports usually do not carry it. There is no second severity source I could read, so no conflict to flag.
How to check if you're exposed
List signed drivers whose name mentions Thunderbolt and read their versions:
Get-CimInstance Win32_PnPSignedDriver |
Where-Object DeviceName -like "*Thunderbolt*" |
Select-Object DeviceName, DriverVersion, Manufacturer
The advisory speaks of version 88, which may not match the longer version string Windows shows for the driver file. Map one to the other using the advisory or the OEM release notes. Laptop makers often deliver this driver in their own bundles, which can lag the Intel release. If the OEM bundle is older than Intel's fixed package, ask the OEM for an update date.
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
- Read SA-00851 and note the mapping between driver package and fixed version.
- Find Windows machines with a Thunderbolt DCH driver using your endpoint inventory.
- Install driver version 88 or later, from Intel or from the OEM.
- Reboot where required, then confirm the driver version reported by the machine.
- Track machines whose OEM has not yet shipped a fixed package.
Why it matters
Drivers run in a trusted part of the operating system. If a driver does not properly check who is calling it, a regular user can reach functions meant for the system. That is the pattern behind most local privilege escalation bugs in drivers.
The risk is highest where many people share a machine, or where an attacker already has code running as a standard user. It is not a remote bug by itself. The record does not mark the CVE as known exploited in CISA KEV.
Quick check
Which versions are affected?
The record says Intel Thunderbolt DCH drivers for Windows before version 88. Confirm in SA-00851.
Can someone use it over the network?
The record vector is local, so the attacker needs access to the machine first.
Sources
Last reviewed: 19 October 2026.