CVE-2021-26349: Failure to assign a new report ID to an imported guest may potentially result in an SEV-SNP guest VM being tricked into trusting a dishonest…
Noroxi assessment
Priority: Monitor (action score 22/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.21% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: kernel-firmware (openSUSE:Leap 15.3) 20210208-150300.4.10.1; kernel-firmware (openSUSE:Leap 15.4) 20220509-150400.4.5.1; kernel-firmware (SUSE:Linux Enterprise High Performance Computing 15 SP1-ESPOS) 20200107-150100.3.31.1.
Low priority for now. Upgrade to kernel-firmware (openSUSE:Leap 15.3) 20210208-150300.4.10.1; kernel-firmware (openSUSE:Leap 15.4) 20220509-150400.4.5.1; kernel-firmware (SUSE:Linux Enterprise High Performance Computing 15 SP1-ESPOS) 20200107-150100.3.31.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 assign a new report ID to an imported guest may potentially result in an SEV-SNP guest VM being tricked into trusting a dishonest Migration Agent (MA).
- Published
- May 11, 2022
- Updated
- Jun 16, 2026
- EPSS
- 0.2% · 12th percentile
- CWE
- —
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
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 7763 firmware | cpe:2.3:o:amd:epyc_7763_firmware |
| amd | epyc 7763 | cpe:2.3:h:amd:epyc_7763 |
| amd | epyc 7713p firmware | cpe:2.3:o:amd:epyc_7713p_firmware |
| amd | epyc 7713p | cpe:2.3:h:amd:epyc_7713p |
| amd | epyc 7713 firmware | cpe:2.3:o:amd:epyc_7713_firmware |
| amd | epyc 7713 | cpe:2.3:h:amd:epyc_7713 |
| amd | epyc 7663 firmware | cpe:2.3:o:amd:epyc_7663_firmware |
| amd | epyc 7663 | cpe:2.3:h:amd:epyc_7663 |
| amd | epyc 7643 firmware | cpe:2.3:o:amd:epyc_7643_firmware |
| amd | epyc 7643 | cpe:2.3:h:amd:epyc_7643 |
| amd | epyc 75f3 firmware | cpe:2.3:o:amd:epyc_75f3_firmware |
| amd | epyc 75f3 | cpe:2.3:h:amd:epyc_75f3 |
and 34 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 EPYC™ Processors
- variousaffected
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 72f3 firmwarebefore milanpi-sp3_1.0.0.7
- amd epyc 7313 firmwarebefore milanpi-sp3_1.0.0.7
- amd epyc 7313p firmwarebefore milanpi-sp3_1.0.0.7
- amd epyc 7343 firmwarebefore milanpi-sp3_1.0.0.7
- amd epyc 7373x firmwarebefore milanpi-sp3_1.0.0.7
- amd epyc 73f3 firmwarebefore milanpi-sp3_1.0.0.7
- amd epyc 7413 firmwarebefore milanpi-sp3_1.0.0.7
- amd epyc 7443 firmwarebefore milanpi-sp3_1.0.0.7
- amd epyc 7443p firmwarebefore milanpi-sp3_1.0.0.7
- amd epyc 7453 firmwarebefore milanpi-sp3_1.0.0.7
- amd epyc 7473x firmwarebefore milanpi-sp3_1.0.0.7
- amd epyc 74f3 firmwarebefore milanpi-sp3_1.0.0.7
- amd epyc 7513 firmwarebefore milanpi-sp3_1.0.0.7
- amd epyc 7543 firmwarebefore milanpi-sp3_1.0.0.7
- amd epyc 7543p firmwarebefore milanpi-sp3_1.0.0.7
- amd epyc 7573x firmwarebefore milanpi-sp3_1.0.0.7
- amd epyc 75f3 firmwarebefore milanpi-sp3_1.0.0.7
- amd epyc 7643 firmwarebefore milanpi-sp3_1.0.0.7
- amd epyc 7663 firmwarebefore milanpi-sp3_1.0.0.7
- amd epyc 7713 firmwarebefore milanpi-sp3_1.0.0.7
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| openSUSE:Leap 15.3 | kernel-firmware | before 20210208-150300.4.10.1 | 20210208-150300.4.10.1 |
| openSUSE:Leap 15.4 | kernel-firmware | before 20220509-150400.4.5.1 | 20220509-150400.4.5.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP1-ESPOS | kernel-firmware | before 20200107-150100.3.31.1 | 20200107-150100.3.31.1 |
| SUSE:Linux Enterprise High Performance Computing 15-ESPOS | kernel-firmware | before 20191118-150000.3.42.1 | 20191118-150000.3.42.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP3 | kernel-firmware | before 20210208-150300.4.10.1 | 20210208-150300.4.10.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP4 | kernel-firmware | before 20220509-150400.4.5.1 | 20220509-150400.4.5.1 |
| SUSE:OpenStack Cloud 9 | kernel-firmware | before 20190618-5.25.2 | 20190618-5.25.2 |
Same product
amd: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-46771Insufficient validation of addresses in AMD Secure Processor (ASP) firmware system call may potentially lead to arbitrary code execution by…31Monitor
- CVE-2021-26353Failure to validate inputs in SMM may allow an attacker to create a mishandled error leaving the DRTM UApp in a partially initialized state…31Monitor
- CVE-2021-26324A bug with the SEV-ES TMR may lead to a potential loss of memory integrity for SNP-active VMs.31Monitor
Published before and after this one in the same product
- ← EarlierCVE-2021-26347May 11, 2022 · Failure to validate the integer operand in ASP (AMD Secure Processor) bootloader may allow an attacker to introduce an integer overflow in…18Monitor
- ← EarlierCVE-2021-26348May 11, 2022 · Failure to flush the Translation Lookaside Buffer (TLB) of the I/O memory management unit (IOMMU) may lead an IO device to write to memory…22Monitor
- Later →CVE-2023-20566Nov 14, 2023 · Improper address validation in ASP with SNP enabled may potentially allow an attacker to compromise guest memory integrity.30Monitor
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 |
|---|---|---|
| opensuse:kernel-firmware | 20210208-150300.4.10.1 · openSUSE:Leap 15.3 | Package registry (OSV) |
| suse:kernel-firmware | 20200107-150100.3.31.1 · SUSE:Linux Enterprise High Performance Computing 15 SP1-ESPOS | Package registry (OSV) |
| suse:kernel-firmware | 20210208-150300.4.10.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP3 | 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.
- A low-privileged account is enough.
- 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
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/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.