CVE-2021-46744: An attacker with access to a malicious hypervisor may be able to infer data values used in a SEV guest on AMD CPUs by monitoring ciphertext
Noroxi assessment
Priority: Monitor (action score 26/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.33% (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 (openSUSE:Tumbleweed) 20220516-1.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 (openSUSE:Tumbleweed) 20220516-1.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
An attacker with access to a malicious hypervisor may be able to infer data values used in a SEV guest on AMD CPUs by monitoring ciphertext values over time.
- BDU:2022-02878
- openSUSE-SU-2024:12088-1
- openSUSE-SU-2025:14769-1
- openSUSE-SU-2025:14770-1
- openSUSE-SU-2025:14771-1
- openSUSE-SU-2025:14772-1
- openSUSE-SU-2025:14773-1
- openSUSE-SU-2025:14774-1
- openSUSE-SU-2025:14775-1
- openSUSE-SU-2025:14776-1
- openSUSE-SU-2025:14777-1
- openSUSE-SU-2025:14778-1
- openSUSE-SU-2025:14779-1
- openSUSE-SU-2025:14780-1
- openSUSE-SU-2025:14781-1
- openSUSE-SU-2025:14782-1
- openSUSE-SU-2025:14783-1
- openSUSE-SU-2025:14784-1
- openSUSE-SU-2025:14785-1
- openSUSE-SU-2025:14786-1
- Published
- May 11, 2022
- Updated
- Jun 17, 2026
- EPSS
- 0.3% · 26th percentile
- CWE
- CWE-203
Report tools
Action score
26
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
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.
Running WordPress? Scan your site free with WP Lens
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 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 7261 firmware | cpe:2.3:o:amd:epyc_7261_firmware |
| amd | epyc 7001 firmware | cpe:2.3:o:amd:epyc_7001_firmware |
| amd | epyc 7001 | cpe:2.3:h:amd:epyc_7001 |
| amd | epyc 7002 firmware | cpe:2.3:o:amd:epyc_7002_firmware |
| amd | epyc 7002 | cpe:2.3:h:amd:epyc_7002 |
| amd | epyc 7003 firmware | cpe:2.3:o:amd:epyc_7003_firmware |
| amd | epyc 7003 | cpe:2.3:h:amd:epyc_7003 |
| amd | epyc 7232p firmware | cpe:2.3:o:amd:epyc_7232p_firmware |
| amd | epyc 7232p | cpe:2.3:h:amd:epyc_7232p |
| amd | epyc 7251 firmware | cpe:2.3:o:amd:epyc_7251_firmware |
| amd | epyc 7251 | cpe:2.3:h:amd:epyc_7251 |
| amd | epyc 7252 firmware | cpe:2.3:o:amd:epyc_7252_firmware |
and 186 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- amd epyc 7001 firmwareall versions
- amd epyc 7002 firmwareall versions
- amd epyc 7003 firmwareall versions
- amd epyc 7232p firmwareall versions
- amd epyc 7251 firmwareall versions
- amd epyc 7252 firmwareall versions
- amd epyc 7261 firmwareall versions
- amd epyc 7262 firmwareall versions
- amd epyc 7272 firmwareall versions
- amd epyc 7281 firmwareall versions
- amd epyc 7282 firmwareall versions
- amd epyc 7301 firmwareall versions
- amd epyc 7302 firmwareall versions
- amd epyc 7302p firmwareall versions
- amd epyc 7313 firmwareall versions
- amd epyc 7313p firmwareall versions
- amd epyc 7343 firmwareall versions
- amd epyc 7351 firmwareall versions
- amd epyc 7351p firmwareall versions
- amd epyc 7352 firmwareall versions
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 Processors
- Processor EPYCaffected
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 |
| openSUSE:Tumbleweed | kernel-firmware | before 20220516-1.1 | 20220516-1.1 |
| openSUSE:Tumbleweed | kernel-firmware-all | before 20250206-1.1 | 20250206-1.1 |
| openSUSE:Tumbleweed | kernel-firmware-amdgpu | before 20250206-1.1 | 20250206-1.1 |
| openSUSE:Tumbleweed | kernel-firmware-ath10k | before 20250206-1.1 | 20250206-1.1 |
| openSUSE:Tumbleweed | kernel-firmware-ath11k | before 20250206-1.1 | 20250206-1.1 |
| openSUSE:Tumbleweed | kernel-firmware-ath12k | before 20250206-1.1 | 20250206-1.1 |
| openSUSE:Tumbleweed | kernel-firmware-atheros | before 20250206-1.1 | 20250206-1.1 |
| openSUSE:Tumbleweed | kernel-firmware-bluetooth | before 20250208-1.1 | 20250208-1.1 |
| openSUSE:Tumbleweed | kernel-firmware-bnx2 | before 20250206-1.1 | 20250206-1.1 |
| openSUSE:Tumbleweed | kernel-firmware-brcm | before 20250206-1.1 | 20250206-1.1 |
| openSUSE:Tumbleweed | kernel-firmware-chelsio | before 20250206-1.1 | 20250206-1.1 |
| openSUSE:Tumbleweed | kernel-firmware-dpaa2 | before 20250206-1.1 | 20250206-1.1 |
| openSUSE:Tumbleweed | kernel-firmware-i915 | before 20250210-1.1 | 20250210-1.1 |
| openSUSE:Tumbleweed | kernel-firmware-intel | before 20250206-1.1 | 20250206-1.1 |
| openSUSE:Tumbleweed | kernel-firmware-iwlwifi | before 20250206-1.1 | 20250206-1.1 |
| openSUSE:Tumbleweed | kernel-firmware-liquidio | before 20250206-1.1 | 20250206-1.1 |
| openSUSE:Tumbleweed | kernel-firmware-marvell | before 20250206-1.1 | 20250206-1.1 |
| openSUSE:Tumbleweed | kernel-firmware-media | before 20250206-1.1 | 20250206-1.1 |
| openSUSE:Tumbleweed | kernel-firmware-mediatek | before 20250206-1.1 | 20250206-1.1 |
| openSUSE:Tumbleweed | kernel-firmware-mellanox | before 20250206-1.1 | 20250206-1.1 |
| openSUSE:Tumbleweed | kernel-firmware-mwifiex | before 20250206-1.1 | 20250206-1.1 |
| openSUSE:Tumbleweed | kernel-firmware-network | before 20250206-1.1 | 20250206-1.1 |
+18
Same product
amd: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-26340A malicious hypervisor in conjunction with an unprivileged attacker process inside an SEV/SEV-ES guest VM may fail to flush the Translation 33Monitor
- CVE-2021-46774Insufficient DRAM address validation in System
Management Unit (SMU) may allow an attacker to read/write from/to an invalid
DRAM address, po30Monitor
- CVE-2020-12988A potential denial of service (DoS) vulnerability exists in the integrated chipset that may allow a malicious attacker to hang the system wh30Monitor
Published before and after this one in the same product
- Later →CVE-2021-26403Jan 11, 2023 · Insufficient checks in SEV may lead to a malicious hypervisor disclosing the launch secret potentially resulting in compromise of VM confide26Monitor
- Later →CVE-2021-26356May 9, 2023 · A TOCTOU in ASP bootloader may allow an attacker
to tamper with the SPI ROM following data read to memory potentially resulting
in S3 data c29Monitor
- Later →CVE-2023-20521Nov 14, 2023 · TOCTOU in the ASP Bootloader may allow an attacker with physical access to tamper with SPI ROM records after memory content verification, po22Monitor
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) |
| opensuse:kernel-firmware-amdgpu | 20250206-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:kernel-firmware-ath10k | 20250206-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:kernel-firmware-ath11k | 20250206-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:kernel-firmware-ath12k | 20250206-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:kernel-firmware-atheros | 20250206-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:kernel-firmware-bluetooth | 20250208-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:kernel-firmware-bnx2 | 20250206-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:kernel-firmware-brcm | 20250206-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:kernel-firmware-chelsio | 20250206-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:kernel-firmware-dpaa2 | 20250206-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:kernel-firmware-i915 | 20250210-1.1 · openSUSE:Tumbleweed | 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.
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.
Credits
All researchersFinders, 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.
- A low-privileged account is enough.
- 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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-203 · Observable DiscrepancyCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/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.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.