Time-of-check time-of-use race condition for the Intel(R) VTune(TM) Profiler software within Ring 1: Device Drivers may allow an…
Affects Intel VTune Profiler software before 2026.0.0, specifically its Ring 1 device driver component. CVSS scores it 8.5 (high); no vendor rating is given. Fixed in 2026.0.0.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 2026.0.0
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affected component is Ring 1: Device Drivers in Intel VTune Profiler software. Intel VTune Profiler software before version 2026.0.0 is affected.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 14/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Intel VTune Profiler has a time-of-check time-of-use race condition in its Ring 1 device driver component that can allow privilege escalation. An attacker who is locally logged in with a low-privilege account can exploit it without any user interaction, gaining high confidentiality, integrity, and availability impact on the affected system.
Read the original description
Time-of-check time-of-use race condition for the Intel(R) VTune(TM) Profiler software within Ring 1: Device Drivers may allow an escalation of privilege. Unprivileged software adversary with an authenticated user combined with a low complexity attack may enable escalation of privilege. This result may potentially occur via local access when attack requirements are not present without special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (high), integrity (high) and availability (high) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure5/25Specific setups only
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.5/10CVSS 8.5
- No patch0/5No signal
What would change the score
- Would score about 64 if added to CISA KEV
- Would score about 59 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Affected component is Ring 1: Device Drivers in Intel VTune Profiler software. Intel VTune Profiler software before version 2026.0.0 is affected.Upgrade to a fixed version: 2026.0.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-32670 (Time-of-check time-of-use race condition for the Intel(R) VTune(TM) Profiler software within Ring 1: Device Drivers may allow an…), using the cve.now data below. Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only. What cve.now has for CVE-2026-32670 (entry last updated 2026-11-10): Affected: - n/a Intel(R) VTune(TM) Profiler software: version range not reported Fixed versions: 2026.0.0. Conditions (all must be true for the bug to be hit): - Affected component is Ring 1: Device Drivers in Intel VTune Profiler software. (source: https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01477.html) - Intel VTune Profiler software before version 2026.0.0 is affected. (source: https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01477.html) Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. Attacker needs: local access, low-privilege login, no user action. CISA KEV: CVE-2026-32670 is not listed as of cve.now's last read. This KEV status is for CVE-2026-32670 only. If you also check another CVE, look up its own KEV status; never assume it from this one. How to check: - Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory. Verify against the linked advisories before concluding, and cite the date you read each one: - https://intel.com/content/www/us/en/security-center/advisory/intel-sa-01477.html - https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01477.html Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing. Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action. Entry: https://cve.now/CVE-2026-32670 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-32670.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- n/a Intel(R) VTune(TM) Profiler software
Version range not reported
Evidence 3
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Link
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-32670
Is CVE-2026-32670 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A time-of-check time-of-use race condition is a timing flaw where a value is verified and then used later, and it can change in between. In this Intel VTune Profiler device driver component, that gap may let a local user with no special privileges escalate their privileges.Source: intel.com
Am I affected, and how do I check?
Intel VTune Profiler software versions before 2026.0.0 are affected, in the Ring 1 device driver component. To check, look at the installed VTune Profiler version in the product's about or version information.Source: intel.com
How do I fix CVE-2026-32670?
Intel recommends updating Intel VTune Profiler software to version 2026.0.0 or later.Source: intel.com