Skip to main content
Mallory
UnratedVulnerability

CVE-2014-8273: Chipset BIOS Write-Protection Bypass via Race Condition

Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS-Not scored
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2014-8273CWE-362
Also known asBIOS Write Protection Race Condition in Intel Chipsets (CVE-2014-8273)

CVE-2014-8273 is a chipset race condition in BIOS write-protection enforcement. When an attempt is made to enable BIOS writes despite an active lock bit, an interrupt handler detects the attempt and resets the write-enable bit to zero. The delay before the reset creates a timing window in which an attacker can issue BIOS writes, bypassing the intended protection and potentially modifying firmware to establish persistence.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation compromises BIOS firmware integrity by permitting unauthorized writes despite the BIOS lock protection. This can enable installation of malicious firmware or bootkit components and establish firmware-level persistence.

Mitigation

If you can’t patch tonight, do this now.

Ensure platform firmware protections, including BIOS write protection and lock configuration, are enabled and correctly enforced. Apply chipset, BIOS, and platform-firmware updates supplied by the system or motherboard vendor that address the write-enable enforcement race. Restrict firmware-update capability to authorized administrative and physical contexts, and use hardware-backed firmware integrity and measured/verified boot controls where available.

Remediation

Patch, then assume compromise.

Apply vendor-provided firmware, chipset, BIOS, or platform updates that correct the race condition in BIOS write-protection enforcement. Ensure platform firmware and related low-level components are updated to versions that eliminate the timing window and properly synchronize or atomically enforce BIOS lock and write-enable handling. Where available, follow OEM and chipset-vendor guidance for secure firmware update procedures and validation of BIOS write-protection behavior after patching.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2014-8273 exploited in the wild?
As of Oct 17, 2026, Mallory has no reports of CVE-2014-8273 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2014-8273?
As of Oct 17, 2026, Mallory has found no public exploit for CVE-2014-8273.
Is there a patch for CVE-2014-8273?
Apply vendor-provided firmware, chipset, BIOS, or platform updates that correct the race condition in BIOS write-protection enforcement. Ensure platform firmware and related low-level components are updated to versions that eliminate the timing window and properly synchronize or atomically enforce BIOS lock and write-enable handling.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity1Community discussion across Reddit, Mastodon, and other social sources.