Skip to main content
Mallory
UnratedVulnerability

CVE-2024-35347: Microcode Signature Verification Bypass in AMD CPUs (CVE-2024-35347)

Updated 8 months 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-2024-35347CWE-347

CVE-2024-35347 is a vulnerability in AMD CPUs, specifically affecting the microcode signature verification process. The flaw allows systems to accept microcode updates that lack the critical microcode signing fix, leaving them exposed to potential exploitation. The vulnerability primarily impacts AMD Family 19h CPUs and is documented in AMD security bulletin AMD-SB-7033. The root cause is insufficient enforcement of microcode signature verification, which can only be fully remediated by applying a BIOS update that delivers the updated microcode with the signing fix. Without this update, systems remain vulnerable even if they receive microcode updates from the Linux firmware repository, as these do not address the underlying signature verification issue.

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.

Systems affected by this vulnerability are unable to receive secure microcode updates, leaving them exposed to future security risks that could be mitigated by proper microcode signature verification. This increases the attack surface for potential privilege escalation or code execution attacks at the hardware level. The operational impact is significant for system administrators, as many systems may never receive the necessary BIOS updates, resulting in persistent exposure.

Mitigation

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

For systems where a BIOS update is not immediately possible, administrators can apply the latest available microcode patches from the Linux firmware repository to receive some security improvements. However, these patches do not address the core signature verification issue. Administrators should prioritize BIOS updates and, where feasible, develop operational processes to manage BIOS configuration backup and restore to facilitate updates.

Remediation

Patch, then assume compromise.

The only complete remediation is to apply a BIOS update from the system or motherboard vendor that includes the latest AMD microcode with the microcode signing fix. This update ensures that future microcode updates are properly verified and applied, closing the vulnerability.

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-2024-35347 exploited in the wild?
As of Mar 19, 2026, Mallory has no reports of CVE-2024-35347 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2024-35347?
As of Mar 19, 2026, Mallory has found no public exploit for CVE-2024-35347.
Is there a patch for CVE-2024-35347?
The only complete remediation is to apply a BIOS update from the system or motherboard vendor that includes the latest AMD microcode with the microcode signing fix. This update ensures that future microcode updates are properly verified and applied, closing the vulnerability.
Activity feed

Recent activity

3 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

View more in app →

No news coverage yet. Advisories and community discussion only.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
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 activity3Community discussion across Reddit, Mastodon, and other social sources.