CVE-2023-31346

Failure to initialize memory in SEV Firmware may allow a privileged attacker to access stale data from other guests.

Published: 2024-02-13 Last update: 2025-03-20 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2023-31346 is rated Low Risk (32.1/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.31%). 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-2023-31346

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.04% 0.31% +0.27%
2 2025-11-21 0.12% 0.04% -0.09%
3 2025-11-18 — 0.12% —

Full EPSS history (12 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2023-31346

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.0 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:H/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:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
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.5 4.0 [email protected]
6.0 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:H/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:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
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.5 4.0 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2023-31346

OS Trackers for CVE-2023-31346

vendor priority summary link
redhat medium — https://access.redhat.com/security/cve/CVE-2023-31346
suse medium CVE-2023-31346 severity moderate: SUSE including 40 source package names (iwl100-firmware-39.31.5.1-122.el8_10.1, iwl100-firmware-39.31.5.1-143.1.el9_4, …), 107 product×package rows across 39 product lines (SUSE CaaS Platform 4.0, SUSE Enterprise Storage 7.1, … (39 product lines)): Will Not Fix 69, Fixed 38. https://www.suse.com/security/cve/CVE-2023-31346/
ubuntu medium CVE-2023-31346 medium priority: Ubuntu including 1 source packages (linux-firmware), 11 status rows across 11 suites (bionic, focal, jammy, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): needs-triage 8, ignored 3. https://ubuntu.com/security/CVE-2023-31346

Affected software / configurations for CVE-2023-31346

Vendor Product Version Raw CPE
amd epyc_7773x_firmware < milanpi_1.0.0.c cpe:2.3:o:amd:epyc_7773x_firmware:*:*:*:*:*:*:*:*
amd epyc_7763_firmware < milanpi_1.0.0.c cpe:2.3:o:amd:epyc_7763_firmware:*:*:*:*:*:*:*:*
amd epyc_7713_firmware < milanpi_1.0.0.c cpe:2.3:o:amd:epyc_7713_firmware:*:*:*:*:*:*:*:*
amd epyc_7713p_firmware < milanpi_1.0.0.c cpe:2.3:o:amd:epyc_7713p_firmware:*:*:*:*:*:*:*:*
amd epyc_7663_firmware < milanpi_1.0.0.c cpe:2.3:o:amd:epyc_7663_firmware:*:*:*:*:*:*:*:*
amd epyc_7663p_firmware < milanpi_1.0.0.c cpe:2.3:o:amd:epyc_7663p_firmware:*:*:*:*:*:*:*:*
amd epyc_7643_firmware < milanpi_1.0.0.c cpe:2.3:o:amd:epyc_7643_firmware:*:*:*:*:*:*:*:*
amd epyc_7643p_firmware < milanpi_1.0.0.c cpe:2.3:o:amd:epyc_7643p_firmware:*:*:*:*:*:*:*:*
amd epyc_7573x_firmware < milanpi_1.0.0.c cpe:2.3:o:amd:epyc_7573x_firmware:*:*:*:*:*:*:*:*
amd epyc_75f3_firmware < milanpi_1.0.0.c cpe:2.3:o:amd:epyc_75f3_firmware:*:*:*:*:*:*:*:*
amd epyc_7543_firmware < milanpi_1.0.0.c cpe:2.3:o:amd:epyc_7543_firmware:*:*:*:*:*:*:*:*
amd epyc_7543p_firmware < milanpi_1.0.0.c cpe:2.3:o:amd:epyc_7543p_firmware:*:*:*:*:*:*:*:*
amd epyc_7513_firmware < milanpi_1.0.0.c cpe:2.3:o:amd:epyc_7513_firmware:*:*:*:*:*:*:*:*
amd epyc_7453_firmware < milanpi_1.0.0.c cpe:2.3:o:amd:epyc_7453_firmware:*:*:*:*:*:*:*:*
amd epyc_7473x_firmware < milanpi_1.0.0.c cpe:2.3:o:amd:epyc_7473x_firmware:*:*:*:*:*:*:*:*
amd epyc_74f3_firmware < milanpi_1.0.0.c cpe:2.3:o:amd:epyc_74f3_firmware:*:*:*:*:*:*:*:*
amd epyc_7443_firmware < milanpi_1.0.0.c cpe:2.3:o:amd:epyc_7443_firmware:*:*:*:*:*:*:*:*
amd epyc_7443p_firmware < milanpi_1.0.0.c cpe:2.3:o:amd:epyc_7443p_firmware:*:*:*:*:*:*:*:*
amd epyc_7413_firmware < milanpi_1.0.0.c cpe:2.3:o:amd:epyc_7413_firmware:*:*:*:*:*:*:*:*
amd epyc_7373x_firmware < milanpi_1.0.0.c cpe:2.3:o:amd:epyc_7373x_firmware:*:*:*:*:*:*:*:*
amd epyc_73f3_firmware < milanpi_1.0.0.c cpe:2.3:o:amd:epyc_73f3_firmware:*:*:*:*:*:*:*:*
amd epyc_7343_firmware < milanpi_1.0.0.c cpe:2.3:o:amd:epyc_7343_firmware:*:*:*:*:*:*:*:*
amd epyc_7313_firmware < milanpi_1.0.0.c cpe:2.3:o:amd:epyc_7313_firmware:*:*:*:*:*:*:*:*
amd epyc_7313p_firmware < milanpi_1.0.0.c cpe:2.3:o:amd:epyc_7313p_firmware:*:*:*:*:*:*:*:*
amd epyc_7303_firmware < milanpi_1.0.0.c cpe:2.3:o:amd:epyc_7303_firmware:*:*:*:*:*:*:*:*
amd epyc_7303p_firmware < milanpi_1.0.0.c cpe:2.3:o:amd:epyc_7303p_firmware:*:*:*:*:*:*:*:*
amd epyc_72f3_firmware < milanpi_1.0.0.c cpe:2.3:o:amd:epyc_72f3_firmware:*:*:*:*:*:*:*:*
amd epyc_7203_firmware < milanpi_1.0.0.c cpe:2.3:o:amd:epyc_7203_firmware:*:*:*:*:*:*:*:*
amd epyc_7203p_firmware < milanpi_1.0.0.c cpe:2.3:o:amd:epyc_7203p_firmware:*:*:*:*:*:*:*:*
amd epyc_8024p_firmware < genoapi_1.0.0.b cpe:2.3:o:amd:epyc_8024p_firmware:*:*:*:*:*:*:*:*
amd epyc_8024pn_firmware < genoapi_1.0.0.b cpe:2.3:o:amd:epyc_8024pn_firmware:*:*:*:*:*:*:*:*
amd epyc_8124p_firmware < genoapi_1.0.0.b cpe:2.3:o:amd:epyc_8124p_firmware:*:*:*:*:*:*:*:*
amd epyc_8124pn_firmware < genoapi_1.0.0.b cpe:2.3:o:amd:epyc_8124pn_firmware:*:*:*:*:*:*:*:*
amd epyc_8224p_firmware < genoapi_1.0.0.b cpe:2.3:o:amd:epyc_8224p_firmware:*:*:*:*:*:*:*:*
amd epyc_8224pn_firmware < genoapi_1.0.0.b cpe:2.3:o:amd:epyc_8224pn_firmware:*:*:*:*:*:*:*:*
amd epyc_8324p_firmware < genoapi_1.0.0.b cpe:2.3:o:amd:epyc_8324p_firmware:*:*:*:*:*:*:*:*
amd epyc_8324pn_firmware < genoapi_1.0.0.b cpe:2.3:o:amd:epyc_8324pn_firmware:*:*:*:*:*:*:*:*
amd epyc_8434p_firmware < genoapi_1.0.0.b cpe:2.3:o:amd:epyc_8434p_firmware:*:*:*:*:*:*:*:*
amd epyc_8434pn_firmware < genoapi_1.0.0.b cpe:2.3:o:amd:epyc_8434pn_firmware:*:*:*:*:*:*:*:*
amd epyc_8534p_firmware < genoapi_1.0.0.b cpe:2.3:o:amd:epyc_8534p_firmware:*:*:*:*:*:*:*:*
amd epyc_8534pn_firmware < genoapi_1.0.0.b cpe:2.3:o:amd:epyc_8534pn_firmware:*:*:*:*:*:*:*:*
amd epyc_9124_firmware < genoapi_1.0.0.b cpe:2.3:o:amd:epyc_9124_firmware:*:*:*:*:*:*:*:*
amd epyc_9224_firmware < genoapi_1.0.0.b cpe:2.3:o:amd:epyc_9224_firmware:*:*:*:*:*:*:*:*
amd epyc_9254_firmware < genoapi_1.0.0.b cpe:2.3:o:amd:epyc_9254_firmware:*:*:*:*:*:*:*:*
amd epyc_9334_firmware < genoapi_1.0.0.b cpe:2.3:o:amd:epyc_9334_firmware:*:*:*:*:*:*:*:*
amd epyc_9354_firmware < genoapi_1.0.0.b cpe:2.3:o:amd:epyc_9354_firmware:*:*:*:*:*:*:*:*
amd epyc_9354p_firmware < genoapi_1.0.0.b cpe:2.3:o:amd:epyc_9354p_firmware:*:*:*:*:*:*:*:*
amd epyc_9174f_firmware < genoapi_1.0.0.b cpe:2.3:o:amd:epyc_9174f_firmware:*:*:*:*:*:*:*:*
amd epyc_9184x_firmware < genoapi_1.0.0.b cpe:2.3:o:amd:epyc_9184x_firmware:*:*:*:*:*:*:*:*
amd epyc_9274f_firmware < genoapi_1.0.0.b cpe:2.3:o:amd:epyc_9274f_firmware:*:*:*:*:*:*:*:*
amd epyc_9374f_firmware < genoapi_1.0.0.b cpe:2.3:o:amd:epyc_9374f_firmware:*:*:*:*:*:*:*:*
amd epyc_9384x_firmware < genoapi_1.0.0.b cpe:2.3:o:amd:epyc_9384x_firmware:*:*:*:*:*:*:*:*
amd epyc_9474f_firmware < genoapi_1.0.0.b cpe:2.3:o:amd:epyc_9474f_firmware:*:*:*:*:*:*:*:*
amd epyc_9454_firmware < genoapi_1.0.0.b cpe:2.3:o:amd:epyc_9454_firmware:*:*:*:*:*:*:*:*
amd epyc_9454p_firmware < genoapi_1.0.0.b cpe:2.3:o:amd:epyc_9454p_firmware:*:*:*:*:*:*:*:*
amd epyc_9534_firmware < genoapi_1.0.0.b cpe:2.3:o:amd:epyc_9534_firmware:*:*:*:*:*:*:*:*
amd epyc_9554_firmware < genoapi_1.0.0.b cpe:2.3:o:amd:epyc_9554_firmware:*:*:*:*:*:*:*:*
amd epyc_9554p_firmware < genoapi_1.0.0.b cpe:2.3:o:amd:epyc_9554p_firmware:*:*:*:*:*:*:*:*
amd epyc_9634_firmware < genoapi_1.0.0.b cpe:2.3:o:amd:epyc_9634_firmware:*:*:*:*:*:*:*:*
amd epyc_9654_firmware < genoapi_1.0.0.b cpe:2.3:o:amd:epyc_9654_firmware:*:*:*:*:*:*:*:*
amd epyc_9654p_firmware < genoapi_1.0.0.b cpe:2.3:o:amd:epyc_9654p_firmware:*:*:*:*:*:*:*:*
amd epyc_9684x_firmware < genoapi_1.0.0.b cpe:2.3:o:amd:epyc_9684x_firmware:*:*:*:*:*:*:*:*

References for CVE-2023-31346

cvelogic Threat Intelligence