CVE-2024-36357

A transient execution vulnerability in some AMD processors may allow an attacker to infer data in the L1D cache, potentially resulting in the leakage of sensitive information across privileged boundaries.

Published: 2025-07-08 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-36357 is rated Low Risk (30/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.30%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2024-36357

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.10% 0.30% +0.20%
2 2026-05-04 0.01% 0.10% +0.09%
3 2025-07-09 — 0.01% —

Full EPSS history (3 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-36357

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.6 3.1 MEDIUM
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 1.1 4.0 [email protected]

Weakness enumeration for CVE-2024-36357

OS Trackers for CVE-2024-36357

vendor priority summary link
alpine medium CVE-2024-36357: 1 source package rows (xen); 5 state rows across 5 repos (3.19-main, 3.20-main, 3.21-main, 3.22-main, edge-main); fixed 5, open 0. https://security.alpinelinux.org/vuln/CVE-2024-36357
debian end-of-life CVE-2024-36357 end-of-life priority: Debian including 4 source packages (amd64-microcode, linux, linux-6.1, xen), 16 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 12, open 4. https://security-tracker.debian.org/tracker/CVE-2024-36357
redhat medium — https://access.redhat.com/security/cve/CVE-2024-36357
ubuntu medium CVE-2024-36357 medium priority: Ubuntu including 160 source packages (amd64-microcode, linux, …), 1569 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 1144, ignored 173, released 139, needed 83, not-affected 20, needs-triage 9, pending 1. https://ubuntu.com/security/CVE-2024-36357

Affected software / configurations for CVE-2024-36357

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2024-36357

cvelogic Threat Intelligence