Skip to content
Noroxi
CVE-2023-31346· NVD / CVE Program· CNA AMD

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

Noroxi assessment

Priority: Monitor (action score 24/100)

  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.30% (FIRST EPSS).
  • Someone with local access to the system can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: iwl100-firmware (AlmaLinux:8) 39.31.5.1-122.el8_10.1; iwl1000-firmware (AlmaLinux:8) 1:39.31.5.1-122.el8_10.1; iwl105-firmware (AlmaLinux:8) 18.168.6.1-122.el8_10.1.

Low priority for now. Upgrade to iwl100-firmware (AlmaLinux:8) 39.31.5.1-122.el8_10.1; iwl1000-firmware (AlmaLinux:8) 1:39.31.5.1-122.el8_10.1; iwl105-firmware (AlmaLinux:8) 18.168.6.1-122.el8_10.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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

MediumCVSS 6.0 · v3.1—Proof of concept Fix available
Published
Feb 13, 2024
Updated
Jun 17, 2026
EPSS
0.3% · 22th percentile

Report tools

JSON

Action score

24

Monitor

Low priority for now.

CVSS
24 / 40 · 6.0 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2023-31346

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
amdepyc 7773x firmware
amdepyc 7773x
amdepyc 7763 firmware
amdepyc 7763
amdepyc 7713 firmware
amdepyc 7713
amdepyc 7713p firmware
amdepyc 7713p
amdepyc 7663 firmware
amdepyc 7663
amdepyc 7663p firmware
amdepyc 7663p

and 111 more

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • amd epyc 7203 firmwarebefore milanpi_1.0.0.c
  • amd epyc 7203p firmwarebefore milanpi_1.0.0.c
  • amd epyc 72f3 firmwarebefore milanpi_1.0.0.c
  • amd epyc 7303 firmwarebefore milanpi_1.0.0.c
  • amd epyc 7303p firmwarebefore milanpi_1.0.0.c
  • amd epyc 7313 firmwarebefore milanpi_1.0.0.c
  • amd epyc 7313p firmwarebefore milanpi_1.0.0.c
  • amd epyc 7343 firmwarebefore milanpi_1.0.0.c
  • amd epyc 7373x firmwarebefore milanpi_1.0.0.c
  • amd epyc 73f3 firmwarebefore milanpi_1.0.0.c
  • amd epyc 7413 firmwarebefore milanpi_1.0.0.c
  • amd epyc 7443 firmwarebefore milanpi_1.0.0.c
  • amd epyc 7443p firmwarebefore milanpi_1.0.0.c
  • amd epyc 7453 firmwarebefore milanpi_1.0.0.c
  • amd epyc 7473x firmwarebefore milanpi_1.0.0.c
  • amd epyc 74f3 firmwarebefore milanpi_1.0.0.c
  • amd epyc 7513 firmwarebefore milanpi_1.0.0.c
  • amd epyc 7543 firmwarebefore milanpi_1.0.0.c
  • amd epyc 7543p firmwarebefore milanpi_1.0.0.c
  • amd epyc 7573x firmwarebefore milanpi_1.0.0.c

Versions reported by the vendor

Affected version ranges reported by the assigning authority (AMD). Independent of NVD's CPE analysis and usually ahead of it.

  • AMD 3rd Gen AMD EPYC™ Processors

    • variousaffected
  • AMD 4th Gen AMD EPYC™ Processors

    • variousaffected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:8iwl100-firmwarebefore 39.31.5.1-122.el8_10.139.31.5.1-122.el8_10.1
AlmaLinux:8iwl1000-firmwarebefore 1:39.31.5.1-122.el8_10.11:39.31.5.1-122.el8_10.1
AlmaLinux:8iwl105-firmwarebefore 18.168.6.1-122.el8_10.118.168.6.1-122.el8_10.1
AlmaLinux:8iwl135-firmwarebefore 18.168.6.1-122.el8_10.118.168.6.1-122.el8_10.1
AlmaLinux:8iwl2000-firmwarebefore 18.168.6.1-122.el8_10.118.168.6.1-122.el8_10.1
AlmaLinux:8iwl2030-firmwarebefore 18.168.6.1-122.el8_10.118.168.6.1-122.el8_10.1
AlmaLinux:8iwl3160-firmwarebefore 1:25.30.13.0-122.el8_10.11:25.30.13.0-122.el8_10.1
AlmaLinux:8iwl3945-firmwarebefore 15.32.2.9-122.el8_10.115.32.2.9-122.el8_10.1
AlmaLinux:8iwl4965-firmwarebefore 228.61.2.24-122.el8_10.1228.61.2.24-122.el8_10.1
AlmaLinux:8iwl5000-firmwarebefore 8.83.5.1_1-122.el8_10.18.83.5.1_1-122.el8_10.1
AlmaLinux:8iwl5150-firmwarebefore 8.24.2.2-122.el8_10.18.24.2.2-122.el8_10.1
AlmaLinux:8iwl6000-firmwarebefore 9.221.4.1-122.el8_10.19.221.4.1-122.el8_10.1
AlmaLinux:8iwl6000g2a-firmwarebefore 18.168.6.1-122.el8_10.118.168.6.1-122.el8_10.1
AlmaLinux:8iwl6000g2b-firmwarebefore 18.168.6.1-122.el8_10.118.168.6.1-122.el8_10.1
AlmaLinux:8iwl6050-firmwarebefore 41.28.5.1-122.el8_10.141.28.5.1-122.el8_10.1
AlmaLinux:8iwl7260-firmwarebefore 1:25.30.13.0-122.el8_10.11:25.30.13.0-122.el8_10.1
AlmaLinux:8libertas-sd8686-firmwarebefore 20240610-122.git90df68d2.el8_1020240610-122.git90df68d2.el8_10
AlmaLinux:8libertas-sd8787-firmwarebefore 20240610-122.git90df68d2.el8_1020240610-122.git90df68d2.el8_10
AlmaLinux:8libertas-usb8388-firmwarebefore 2:20240610-122.git90df68d2.el8_102:20240610-122.git90df68d2.el8_10
AlmaLinux:8libertas-usb8388-olpc-firmwarebefore 20240610-122.git90df68d2.el8_1020240610-122.git90df68d2.el8_10
AlmaLinux:8linux-firmwarebefore 20240610-122.git90df68d2.el8_1020240610-122.git90df68d2.el8_10
AlmaLinux:9iwl100-firmwarebefore 39.31.5.1-143.1.el9_439.31.5.1-143.1.el9_4
AlmaLinux:9iwl1000-firmwarebefore 1:39.31.5.1-143.1.el9_41:39.31.5.1-143.1.el9_4
AlmaLinux:9iwl105-firmwarebefore 18.168.6.1-143.1.el9_418.168.6.1-143.1.el9_4

+96

Same product

amd: all records

Other highest-scoring records for the same primary product.

  • CVE-2021-26371A compromised or malicious ABL or UApp could send a SHA256 system call to the bootloader, which may result in exposure of ASP memory to user
    22Monitor
  • CVE-2021-26354Insufficient bounds checking in ASP may allow an attacker to issue a system call from a compromised ABL which may cause arbitrary memory val
    22Monitor
  • CVE-2023-31347Due to a code bug in Secure_TSC, SEV firmware may allow an attacker with high privileges to cause a guest to observe an incorrect TSC when S
    19Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
almalinux:iwl100-firmware39.31.5.1-122.el8_10.1 · AlmaLinux:8Package registry (OSV)
almalinux:iwl1000-firmware1:39.31.5.1-122.el8_10.1 · AlmaLinux:8Package registry (OSV)
almalinux:iwl105-firmware18.168.6.1-122.el8_10.1 · AlmaLinux:8Package registry (OSV)
almalinux:iwl135-firmware18.168.6.1-122.el8_10.1 · AlmaLinux:8Package registry (OSV)
almalinux:iwl2000-firmware18.168.6.1-122.el8_10.1 · AlmaLinux:8Package registry (OSV)
almalinux:iwl2030-firmware18.168.6.1-122.el8_10.1 · AlmaLinux:8Package registry (OSV)
almalinux:iwl3160-firmware1:25.30.13.0-122.el8_10.1 · AlmaLinux:8Package registry (OSV)
almalinux:iwl3945-firmware15.32.2.9-122.el8_10.1 · AlmaLinux:8Package registry (OSV)
almalinux:iwl4965-firmware228.61.2.24-122.el8_10.1 · AlmaLinux:8Package registry (OSV)
almalinux:iwl5000-firmware8.83.5.1_1-122.el8_10.1 · AlmaLinux:8Package registry (OSV)
almalinux:iwl5150-firmware8.24.2.2-122.el8_10.1 · AlmaLinux:8Package registry (OSV)
almalinux:iwl6000-firmware9.221.4.1-122.el8_10.1 · AlmaLinux:8Package registry (OSV)
red hat:iwl100-firmware0:39.31.5.1-122.el8_10.1 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:iwl1000-firmware1:39.31.5.1-122.el8_10.1 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:iwl105-firmware0:18.168.6.1-122.el8_10.1 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:iwl135-firmware0:18.168.6.1-122.el8_10.1 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:iwl2000-firmware0:18.168.6.1-122.el8_10.1 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:iwl2030-firmware0:18.168.6.1-122.el8_10.1 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:iwl3160-firmware1:25.30.13.0-122.el8_10.1 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:iwl3945-firmware0:15.32.2.9-122.el8_10.1 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:iwl4965-firmware0:228.61.2.24-122.el8_10.1 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:iwl5000-firmware0:8.83.5.1_1-122.el8_10.1 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:iwl5150-firmware0:8.24.2.2-122.el8_10.1 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:iwl6000-firmware0:9.221.4.1-122.el8_10.1 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
rocky linux:linux-firmware0:20240610-122.git90df68d2.el8_10 · Rocky Linux:8Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:12023-09-03

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. First PoC-164 d
  2. Published
  3. TodayOct 18, 2026+978 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • Administrator privileges are required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
none

Impact can extend beyond the vulnerable component (scope changes).

Attack vector
Local
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Changed
Confidentiality impact
High
Integrity impact
None
Availability impact
None

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N

nvd-primary

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records