Local denial of service via coarse UEFI permissions
Published Feb 12, 2025 · Updated Nov 3, 2025
Access-control weakness in UEFI firmware for Intel processors allows local users to interrupt affected systems through authenticated access. Intel identifies insufficiently granular firmware access control but does not disclose the affected routine, protected resource, or operation that crosses the intended permission boundary. Low-privileged local access and an additional attack condition are required; successful exploitation disrupts availability in both the vulnerable and subsequent systems.
Summary
What happened
Access-control weakness in UEFI firmware for Intel processors allows local users to interrupt affected systems through authenticated access. Intel identifies insufficiently granular firmware access control but does not disclose the affected routine, protected resource, or operation that crosses the intended permission boundary. Low-privileged local access and an additional attack condition are required; successful exploitation disrupts availability in both the vulnerable and subsequent systems.
The record
- CVE
- CVE-2024-39279
- Published
- Feb 12, 2025
- Updated
- Nov 3, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-1220
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 12, 2025CVE publishedPublication date reported by the CVE source.
- Nov 3, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo