Microsoft Windows Kernel-Mode Driver Untrusted Pointer Dereference Vulnerability
Microsoft · Windows
The Windows Kernel-Mode Driver component of Microsoft Windows contains an untrusted pointer dereference flaw that allows privilege escalation. An attacker with local access and low-privilege credentials, requiring no user interaction, could exploit it to gain elevated privileges with full impact to confidentiality, integrity and availability.
Windows Kernel-Mode Driver Elevation of Privilege Vulnerability
- Exploited
- Yes, in CISA KEV
- Reports
- 0
- Tactics
- 2/15
How an attack unfolds
Based on MITRE ATT&CKA public catalogue of the techniques attackers use, maintained by MITRE. Patchfirst uses it to describe what attackers do with a vulnerability. mappings. Select a step to see the evidence.Exploitation timelineDated milestones for a CVE: when it was disclosed, when exploit code became public, when exploitation was confirmed, and when threat reports named it.
First seen exploited 6 months after disclosure. Public exploit code (Metasploit) was available the same day.
CISA KEV listing is when exploitation was confirmed, not necessarily the first attack.
MITRE ATT&CKA public catalogue of the techniques attackers use, maintained by MITRE. Patchfirst uses it to describe what attackers do with a vulnerability. techniques
2 TechniqueOne specific attacker behaviour in MITRE ATT&CK, such as T1190 “Exploit Public-Facing Application”. IDs with a dot, like T1059.004, are sub-techniques., grouped by TacticThe attacker’s goal at a stage of an attack in MITRE ATT&CK, such as Initial Access or Persistence. Each technique belongs to one or more tactics. in kill-chain order, 2 cited passages 2PersistenceTA0003
Kernel-mode driver context yields system-level code execution
Windows Kernel-Mode Driver Elevation of Privilege Vulnerability
Privilege EscalationTA0004
Local privilege escalation vulnerability in kernel driver
Windows Kernel-Mode Driver Elevation of Privilege Vulnerability
Detection
1 rule for this CVE · 40 general rules for its techniquesRules for this CVE
1Sigma ruleAn open, vendor-neutral detection rule for log data. Security teams convert Sigma rules into searches for their own SIEM. that reference CVE-2024-35250 directly.- Potential CVE-2024-35250 Exploitation Activitymediumexperimental
General rules for this CVE’s techniques
These detect the technique in general, not this specific vulnerability.
Exploitation for Privilege EscalationT106831 general rules
- Exploiting CVE-2019-1388criticalstable
- Audit CVE Eventcriticaltest
- HackTool - SysmonEOP Executioncriticaltest
- InstallerFileTakeOver LPE CVE-2021-41379 File Create Eventcriticaltest
- Possible Coin Miner CPU Priority Paramcriticaltest
- Potential CVE-2021-41379 Exploitation Attemptcriticaltest
- Potential SystemNightmare Exploitation Attemptcriticaltest
- Sudo Privilege Escalation CVE-2019-14287 - Builtincriticaltest
Create or Modify System ProcessT15439 general rules
- CodeIntegrity - Blocked Driver Load With Revoked Certificatehightest
- CodeIntegrity - Blocked Image/Driver Load For Policy Violationhightest
- KrbRelayUp Service Installationhightest
- PUA - Process Hacker Driver Loadhightest
- Service Installed By Unusual Client - Securityhightest
- Service Installed By Unusual Client - Systemhightest
- PUA - Process Hacker Executionmediumtest
- PUA - System Informer Driver Loadmediumtest
Sigma rules © SigmaHQ, Detection Rule License 1.1; linked, not reproduced.
What security researchers reported
Not named in any threat report yetAlso mentioned in 50 community threat pulses (AlienVault OTX)
Weaker evidencePulses are indicator collections that anyone can publish. A mention is not confirmation of exploitation.
- Actively_Exploited_Kev | Oct 30, 202629 Oct 2026
- Actively_Exploited_Kev | Oct 29, 202628 Oct 2026
- Actively_Exploited_Kev | Oct 28, 202627 Oct 2026
- Actively_Exploited_Kev | Oct 27, 202626 Oct 2026
- Actively_Exploited_Kev | Oct 24, 202623 Oct 2026
- Actively_Exploited_Kev | Oct 23, 202622 Oct 2026
- 44 more on OTX