CVE-2024-36350: AMD EPYC™ 9005 Series Processors vulnerability

Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.

Generated by VEDAS. Scores as of 2026-11-17 06:13 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.

What it is

A transient execution vulnerability in some AMD processors may allow an attacker to infer data from previous stores, potentially resulting in the leakage of privileged information.

Description quoted from the CVE record (assigned by AMD, published 2025-07-08).

Weakness: CWE-1421 Exposure of Sensitive Information in Shared Microarchitectural Structures during Transient Execution

How it can be exploited

Exploitable with local access with high attack complexity needing low privileges and no user interaction. Impact: confidentiality high, integrity none, availability none. CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N

CISA assessment (SSVC): CISA has no evidence of exploitation. Automatable: no. Technical impact: partial.

Public exploit evidence (Exploit Observer)

Exploit Observer has no public exploit code naming this CVE. Check Exploit Observer for anything new.

Live scores

EPSS
0.005
low predicted chance of attack
VEDAS
0.670
likely exploited
On CISA KEV
Not listed
Detection rule
Out of scope (local)
EPSS (chance of attack)
100.1CVE-2024-36350 EPSS over time2026-112026-11-17
VEDAS (exploit evidence)
100.5CVE-2024-36350 VEDAS over time2026-112026-11-17

Thin horizontal line: the “likely exploited” threshold (EPSS 0.10, VEDAS 0.5). Shaded “no data” areas are periods when cve-scores did not publish.

Who is affected

ProductAffectedNot affected
AMD EPYC™ 9005 Series ProcessorsNot statedTurinPI_1.0.0.B is not affected
AMD EPYC™ 8005 Series ProcessorsNot statedTurinPI_1.0.0.B is not affected
AMD EPYC™ 4005 Series ProcessorsNot statedComboAM5PI 1.3.0.1d is not affected
AMD Ryzen™ 9000HX Series ProcessorsNot statedFireRangeFL1 PI-1.0.0.0i is not affected
AMD Ryzen™ AI 300 Series ProcessorsNot statedStrixKrackanPI-FP8_1.1.0.0h is not affected; StrixKrackanPI-FP8_1.1.0.2g is not affected
AMD Ryzen™ 9000 Series Desktop ProcessorsNot statedComboAM5PI 1.2.0.3l is not affected; ComboAM5PI 1.3.0.1d is not affected
AMD Ryzen™ AI Max 400 Series ProcessorsNot statedGorgonHaloPI-FP11_1.0.0.0a is not affected
AMD Ryzen™ AI Max 300 Series ProcessorsNot statedStrixHalo PI-FP11_1.0.0.2d is not affected
AMD Ryzen™ AI400 Series Desktop ProcessorsNot statedComboAM5PI 1.3.0.1d is not affected
AMD Ryzen™ AI Z2 ExtremeNot statedGorgonPI-FP8_1.0.0.2e is not affected
AMD Ryzen™ Threadripper™ PRO 9000 WX-Series ProcessorsNot statedShimadaPeakPI-SP6 1.0.0.1h is not affected
AMD Ryzen™ AI 400 Series ProcessorsNot statedGorgonPI-FP8_1.0.0.2e is not affected
AMD EPYC™ Embedded 4005 Series ProcessorsNot statedEmbeddedAM5PI_1.0.0.9 is not affected
AMD EPYC™ Embedded 9005 Series ProcessorsNot statedEmbeddedTurinPI_SP5_1005 is not affected
AMD Ryzen™ Embedded 9000 Series ProcessorsNot statedEmbeddedAM5PI_1.0.0.9 is not affected
AMD Ryzen™ Embedded P100 Series ProcessorsNot statedEmbeddedP100 PI 1000 is not affected
AMD EPYC™ Embedded 2005 Series ProcessorsNot statedEmbeddedFireRangeFL1_1.0.0.5 is not affected

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

How to fix it

No fixed version or vendor advisory is listed in the CVE record yet. Watch the vendor’s security page.

How to detect it

This bug needs local access to exploit. VEDAS signatures cover remotely exploitable bugs for now, so there is no network rule or remote check for it. Patch it and watch your endpoint telemetry for unusual local activity.

Advisories on this CVE

References

Other references

Other databases

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.

Supporting partners