CVE-2021-26364: Insufficient bounds checking in an SMU mailbox register could allow an attacker to potentially read outside of the SRAM address range which…
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 (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
Insufficient bounds checking in an SMU mailbox register could allow an attacker to potentially read outside of the SRAM address range which could result in an exception handling leading to a potential denial of service.
- 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
- openSUSE-SU-2025:14787-1
- Published
- May 11, 2022
- Updated
- Jun 16, 2026
- EPSS
- 0.2% · 12th percentile
- CWE
- CWE-119
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 7232p firmware | cpe:2.3:o:amd:epyc_7232p_firmware |
| amd | epyc 7232p | cpe:2.3:h:amd:epyc_7232p |
| amd | epyc 7302p firmware | cpe:2.3:o:amd:epyc_7302p_firmware |
| amd | epyc 7302p | cpe:2.3:h:amd:epyc_7302p |
| amd | epyc 7402p firmware | cpe:2.3:o:amd:epyc_7402p_firmware |
| amd | epyc 7402p | cpe:2.3:h:amd:epyc_7402p |
| amd | epyc 7502p firmware | cpe:2.3:o:amd:epyc_7502p_firmware |
| amd | epyc 7502p | cpe:2.3:h:amd:epyc_7502p |
| amd | epyc 7702p firmware | cpe:2.3:o:amd:epyc_7702p_firmware |
| amd | epyc 7702p | cpe:2.3:h:amd:epyc_7702p |
| amd | epyc 7252 firmware | cpe:2.3:o:amd:epyc_7252_firmware |
| amd | epyc 7252 | cpe:2.3:h:amd:epyc_7252 |
and 76 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 7232p firmwarebefore romepi-sp3_1.0.0.d
- amd epyc 7252 firmwarebefore romepi-sp3_1.0.0.d
- amd epyc 7262 firmwarebefore romepi-sp3_1.0.0.d
- amd epyc 7272 firmwarebefore romepi-sp3_1.0.0.d
- amd epyc 7282 firmwarebefore romepi-sp3_1.0.0.d
- amd epyc 72f3 firmwarebefore milanpi-sp3_1.0.0.7
- amd epyc 7302 firmwarebefore romepi-sp3_1.0.0.d
- amd epyc 7302p firmwarebefore romepi-sp3_1.0.0.d
- amd epyc 7313p firmwarebefore milanpi-sp3_1.0.0.7
- amd epyc 7343 firmwarebefore milanpi-sp3_1.0.0.7
- amd epyc 7352 firmwarebefore romepi-sp3_1.0.0.d
- amd epyc 7373x firmwarebefore milanpi-sp3_1.0.0.7
- amd epyc 73f3 firmwarebefore milanpi-sp3_1.0.0.7
- amd epyc 7402 firmwarebefore romepi-sp3_1.0.0.d
- amd epyc 7402p firmwarebefore romepi-sp3_1.0.0.d
- amd epyc 7413 firmwarebefore milanpi-sp3_1.0.0.7
- amd epyc 7443p firmwarebefore milanpi-sp3_1.0.0.7
- amd epyc 7452 firmwarebefore romepi-sp3_1.0.0.d
- amd epyc 7453 firmwarebefore milanpi-sp3_1.0.0.7
- amd epyc 7473x 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 |
| 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-26323Failure to validate SEV Commands while SNP is active may result in a potential impact to memory integrity.31Monitor
- CVE-2021-26326Failure to validate VM_HSAVE_PA during SNP_INIT may result in a loss of memory integrity.31Monitor
- CVE-2023-20533Insufficient DRAM address validation in System
Management Unit (SMU) may allow an attacker to read/write from/to an invalid
DRAM address…30Monitor
Published before and after this one in the same product
- ← EarlierCVE-2021-26325Nov 16, 2021 · Insufficient input validation in the SNP_GUEST_REQUEST command may lead to a potential data abort error and a denial of service.22Monitor
- ← EarlierCVE-2021-26350May 11, 2022 · A TOCTOU race condition in SMU may allow for the caller to obtain and manipulate the address of a message port register which may result in…18Monitor
- Later →CVE-2021-26372May 11, 2022 · Insufficient bound checks related to PCIE in the System Management Unit (SMU) may result in access to an invalid address space that could…22Monitor
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.
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
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-119 · Improper Restriction of Operations within the Bounds of a Memory BufferCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
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)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Overflow BuffersCAPEC-100likelihood: High · Very High
- Buffer ManipulationCAPEC-123likelihood: High · Very High
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
- Filter Failure through Buffer OverflowCAPEC-24likelihood: High · High
- MIME ConversionCAPEC-42likelihood: High · High
- Overflow Binary Resource FileCAPEC-44likelihood: High · Very High
- Buffer Overflow via Symbolic LinksCAPEC-45likelihood: High · High
ATT&CK techniques
—
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.