CVE-2023-20584: IOMMU improperly handles certain special address ranges with invalid device table entries (DTEs), which may allow an attacker with…
Noroxi assessment
Priority: Monitor (action score 24/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.18% (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-124.el8_10.1; iwl1000-firmware (AlmaLinux:8) 1:39.31.5.1-124.el8_10.1; iwl105-firmware (AlmaLinux:8) 18.168.6.1-124.el8_10.1.
Low priority for now. Upgrade to iwl100-firmware (AlmaLinux:8) 39.31.5.1-124.el8_10.1; iwl1000-firmware (AlmaLinux:8) 1:39.31.5.1-124.el8_10.1; iwl105-firmware (AlmaLinux:8) 18.168.6.1-124.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
IOMMU improperly handles certain special address ranges with invalid device table entries (DTEs), which may allow an attacker with privileges and a compromised Hypervisor to induce DTE faults to bypass RMP checks in SEV-SNP, potentially leading to a loss of guest integrity.
- Published
- Aug 13, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 8th percentile
- CWE
- —
Report tools
Action score
24
Low priority for now.
- CVSS
- 24 / 40 · 6.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 6.0
- CNA · AMD
- 5.3
- 0.7 point gap
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:N/I:H/A:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi 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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| amd | epyc 8024pn firmware | cpe:2.3:o:amd:epyc_8024pn_firmware |
| amd | epyc 8024pn | cpe:2.3:h:amd:epyc_8024pn |
| amd | epyc 8024p firmware | cpe:2.3:o:amd:epyc_8024p_firmware |
| amd | epyc 8024p | cpe:2.3:h:amd:epyc_8024p |
| amd | epyc 8124pn firmware | cpe:2.3:o:amd:epyc_8124pn_firmware |
| amd | epyc 8124pn | cpe:2.3:h:amd:epyc_8124pn |
| amd | epyc 8124p firmware | cpe:2.3:o:amd:epyc_8124p_firmware |
| amd | epyc 8124p | cpe:2.3:h:amd:epyc_8124p |
| amd | epyc 8224pn firmware | cpe:2.3:o:amd:epyc_8224pn_firmware |
| amd | epyc 8224pn | cpe:2.3:h:amd:epyc_8224pn |
| amd | epyc 8224p firmware | cpe:2.3:o:amd:epyc_8224p_firmware |
| amd | epyc 8224p | cpe:2.3:h:amd:epyc_8224p |
and 118 more
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 AMD EPYC™ 7003 Processors
- MilanPI 1.0.0.Cnot affected
AMD AMD EPYC™ 9004 Processors
- GenoaPI 1.0.0.Bnot affected
Affected versions · NVD (20)
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.b
- amd epyc 7203p firmwarebefore milanpi_1.0.0.b
- amd epyc 72f3 firmwarebefore milanpi_1.0.0.b
- amd epyc 7303 firmwarebefore milanpi_1.0.0.b
- amd epyc 7303p firmwarebefore milanpi_1.0.0.b
- amd epyc 7313 firmwarebefore milanpi_1.0.0.b
- amd epyc 7313p firmwarebefore milanpi_1.0.0.b
- amd epyc 7343 firmwarebefore milanpi_1.0.0.b
- amd epyc 7373x firmwarebefore milanpi_1.0.0.b
- amd epyc 73f3 firmwarebefore milanpi_1.0.0.b
- amd epyc 7413 firmwarebefore milanpi_1.0.0.b
- amd epyc 7443 firmwarebefore milanpi_1.0.0.b
- amd epyc 7443p firmwarebefore milanpi_1.0.0.b
- amd epyc 7453 firmwarebefore milanpi_1.0.0.b
- amd epyc 7473x firmwarebefore milanpi_1.0.0.b
- amd epyc 74f3 firmwarebefore milanpi_1.0.0.b
- amd epyc 7513 firmwarebefore milanpi_1.0.0.b
- amd epyc 7543 firmwarebefore milanpi_1.0.0.b
- amd epyc 7543p firmwarebefore milanpi_1.0.0.b
- amd epyc 7573x firmwarebefore milanpi_1.0.0.b
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | iwl100-firmware | before 39.31.5.1-124.el8_10.1 | 39.31.5.1-124.el8_10.1 |
| AlmaLinux:8 | iwl1000-firmware | before 1:39.31.5.1-124.el8_10.1 | 1:39.31.5.1-124.el8_10.1 |
| AlmaLinux:8 | iwl105-firmware | before 18.168.6.1-124.el8_10.1 | 18.168.6.1-124.el8_10.1 |
| AlmaLinux:8 | iwl135-firmware | before 18.168.6.1-124.el8_10.1 | 18.168.6.1-124.el8_10.1 |
| AlmaLinux:8 | iwl2000-firmware | before 18.168.6.1-124.el8_10.1 | 18.168.6.1-124.el8_10.1 |
| AlmaLinux:8 | iwl2030-firmware | before 18.168.6.1-124.el8_10.1 | 18.168.6.1-124.el8_10.1 |
| AlmaLinux:8 | iwl3160-firmware | before 1:25.30.13.0-124.el8_10.1 | 1:25.30.13.0-124.el8_10.1 |
| AlmaLinux:8 | iwl3945-firmware | before 15.32.2.9-124.el8_10.1 | 15.32.2.9-124.el8_10.1 |
| AlmaLinux:8 | iwl4965-firmware | before 228.61.2.24-124.el8_10.1 | 228.61.2.24-124.el8_10.1 |
| AlmaLinux:8 | iwl5000-firmware | before 8.83.5.1_1-124.el8_10.1 | 8.83.5.1_1-124.el8_10.1 |
| AlmaLinux:8 | iwl5150-firmware | before 8.24.2.2-124.el8_10.1 | 8.24.2.2-124.el8_10.1 |
| AlmaLinux:8 | iwl6000-firmware | before 9.221.4.1-124.el8_10.1 | 9.221.4.1-124.el8_10.1 |
| AlmaLinux:8 | iwl6000g2a-firmware | before 18.168.6.1-124.el8_10.1 | 18.168.6.1-124.el8_10.1 |
| AlmaLinux:8 | iwl6000g2b-firmware | before 18.168.6.1-124.el8_10.1 | 18.168.6.1-124.el8_10.1 |
| AlmaLinux:8 | iwl6050-firmware | before 41.28.5.1-124.el8_10.1 | 41.28.5.1-124.el8_10.1 |
| AlmaLinux:8 | iwl7260-firmware | before 1:25.30.13.0-124.el8_10.1 | 1:25.30.13.0-124.el8_10.1 |
| AlmaLinux:8 | libertas-sd8686-firmware | before 20240827-124.git3cff7109.el8_10 | 20240827-124.git3cff7109.el8_10 |
| AlmaLinux:8 | libertas-sd8787-firmware | before 20240827-124.git3cff7109.el8_10 | 20240827-124.git3cff7109.el8_10 |
| AlmaLinux:8 | libertas-usb8388-firmware | before 2:20240827-124.git3cff7109.el8_10 | 2:20240827-124.git3cff7109.el8_10 |
| AlmaLinux:8 | libertas-usb8388-olpc-firmware | before 20240827-124.git3cff7109.el8_10 | 20240827-124.git3cff7109.el8_10 |
| AlmaLinux:8 | linux-firmware | before 20240827-124.git3cff7109.el8_10 | 20240827-124.git3cff7109.el8_10 |
| AlmaLinux:9 | iwl100-firmware | before 39.31.5.1-143.3.el9_4 | 39.31.5.1-143.3.el9_4 |
| AlmaLinux:9 | iwl1000-firmware | before 1:39.31.5.1-143.3.el9_4 | 1:39.31.5.1-143.3.el9_4 |
| AlmaLinux:9 | iwl105-firmware | before 18.168.6.1-143.3.el9_4 | 18.168.6.1-143.3.el9_4 |
+93
Same product
amd: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-20591Improper re-initialization of IOMMU during the DRTM event
may permit an untrusted platform configuration to persist, allowing an…40Plan
- CVE-2023-20578A TOCTOU (Time-Of-Check-Time-Of-Use) in SMM may allow
an attacker with ring0 privileges and access to the
BIOS menu or UEFI shell to modify…25Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| almalinux:iwl100-firmware | 39.31.5.1-124.el8_10.1 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:iwl1000-firmware | 1:39.31.5.1-124.el8_10.1 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:iwl105-firmware | 18.168.6.1-124.el8_10.1 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:iwl135-firmware | 18.168.6.1-124.el8_10.1 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:iwl2000-firmware | 18.168.6.1-124.el8_10.1 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:iwl2030-firmware | 18.168.6.1-124.el8_10.1 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:iwl3160-firmware | 1:25.30.13.0-124.el8_10.1 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:iwl3945-firmware | 15.32.2.9-124.el8_10.1 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:iwl4965-firmware | 228.61.2.24-124.el8_10.1 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:iwl5000-firmware | 8.83.5.1_1-124.el8_10.1 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:iwl5150-firmware | 8.24.2.2-124.el8_10.1 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:iwl6000-firmware | 9.221.4.1-124.el8_10.1 · AlmaLinux:8 | Package registry (OSV) |
| debian:amd64-microcode | 3.20240820.1~deb12u1 · Debian:12 | Package registry (OSV) |
| red hat:iwl100-firmware | 0:39.31.5.1-114.3.el8_6.1 · Red Hat:rhel_aus:8.6::baseos | Package registry (OSV) |
| red hat:iwl1000-firmware | 1:39.31.5.1-114.3.el8_6.1 · Red Hat:rhel_aus:8.6::baseos | Package registry (OSV) |
| red hat:iwl105-firmware | 0:18.168.6.1-114.3.el8_6.1 · Red Hat:rhel_aus:8.6::baseos | Package registry (OSV) |
| red hat:iwl135-firmware | 0:18.168.6.1-114.3.el8_6.1 · Red Hat:rhel_aus:8.6::baseos | Package registry (OSV) |
| red hat:iwl2000-firmware | 0:18.168.6.1-114.3.el8_6.1 · Red Hat:rhel_aus:8.6::baseos | Package registry (OSV) |
| red hat:iwl2030-firmware | 0:18.168.6.1-114.3.el8_6.1 · Red Hat:rhel_aus:8.6::baseos | Package registry (OSV) |
| red hat:iwl3160-firmware | 1:25.30.13.0-114.3.el8_6.1 · Red Hat:rhel_aus:8.6::baseos | Package registry (OSV) |
| red hat:iwl3945-firmware | 0:15.32.2.9-114.3.el8_6.1 · Red Hat:rhel_aus:8.6::baseos | Package registry (OSV) |
| red hat:iwl4965-firmware | 0:228.61.2.24-114.3.el8_6.1 · Red Hat:rhel_aus:8.6::baseos | Package registry (OSV) |
| red hat:iwl5000-firmware | 0:8.83.5.1_1-114.3.el8_6.1 · Red Hat:rhel_aus:8.6::baseos | Package registry (OSV) |
| red hat:iwl5150-firmware | 0:8.24.2.2-114.3.el8_6.1 · Red Hat:rhel_aus:8.6::baseos | Package registry (OSV) |
| red hat:iwl6000-firmware | 0:9.221.4.1-114.3.el8_6.1 · Red Hat:rhel_aus:8.6::baseos | Package registry (OSV) |
| rocky linux:linux-firmware | 0:20240827-124.git3cff7109.el8_10 · Rocky Linux:8 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
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.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
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
- none
- Integrity
- high · data or configuration can be modified
- 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
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:N/I:H/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
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.