INTEL PERFORMANCE COUNTER MONITOR (PCM) · CVE-2026-50109 · Package
FIX → commit d626ea0 (April 30, 2026) or later ✓ verified
Intel Performance Counter Monitor has an out-of-bounds write reachable from Ring 3 user applications. An unauthenticated attacker with network access can cause a denial of service.
first public Nov 10, 2026 · 2 sources
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Anyone running Intel Performance Counter Monitor (Intel PCM) built from source older than commit d626ea0 of April 30, 2026, on Linux or Windows. Intel rates it as a network-reachable, unauthenticated denial of service (out-of-bounds write); it needs no user interaction. Intel does not say which PCM component listens on the network, so check hosts where PCM tools or its exporter are reachable from other machines. Teams that do not use PCM, or only run an updated build, can skip it.
Who cares denial-of-service, intel-pcm, linux, windows
Out-of-bounds write for some Intel(R) Performance Counter Monitor (Intel(R) PCM) within Ring 3: User Applications may allow a denial of service. Unprivileged software adversary with an unauthenticated user combined with a low complexity attack may enable denial of service. This result may potentially occur via network access when attack requirements are present without special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (none), integrity (low) and availability (high) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.
This page as .md · .json · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
Upgrade to commit d626ea0 (April 30, 2026) or later