CVE-2026-0438: A System Management Mode (SMM) handler could perform a callout to code located in non-SMM/untrusted memory.
Noroxi assessment
Priority: Monitor (action score 21/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.13% (FIRST EPSS).
- Physical access to the device is required. Administrator privileges are required. Special conditions such as timing or configuration are required.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
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
A System Management Mode (SMM) handler could perform a callout to code located in non-SMM/untrusted memory. A highly privileged attacker could, with active user interaction and under high complexity and present preconditions, trigger execution of attacker-controlled code in SMM, potentially compromising the system’s confidentiality, integrity, and availability.
- Published
- May 15, 2026
- Updated
- Oct 26, 2026
- EPSS
- 0.1% · 3th percentile
- CWE
- CWE-1072
Report tools
Action score
21
Monitor
Low priority for now.
- CVSS
- 21 / 40 · 5.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · AMD
- 5.4
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:P/AC:H/AT:P/PR:H/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA: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
- No fixed version yet
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.
—
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™ 4004 Series Processors
- ComboAM5PI 1.0.0.d / ComboAM5PI 1.1.0.3f / ComboAM5PI_1.2.0.3inot affected
AMD AMD EPYC™ 4005 Series Processors
- ComboAM5PI_1.2.0.3inot affected
AMD AMD Ryzen™ 7000 Series Desktop Processors
- ComboAM5PI 1.0.0.d, ComboAM5PI 1.1.0.3f, ComboAM5PI_1.2.0.3inot affected
AMD AMD Ryzen™ 7000 Series Desktop Processors (formerly codenamed "Raphael")
- ComboAM5PI_1.3.0.0not affected
AMD AMD Ryzen™ 7040 Series Mobile Processors with Radeon™ Graphics
- PhoenixPI-FP8-FP7_1.2.0.0fnot affected
AMD AMD Ryzen™ 7045 Series Mobile Processors with Radeon™ Graphics
- DragonRangeFL1PI 1.0.0.3knot affected
AMD AMD Ryzen™ 8000 Series Desktop Processors
- ComboAM5PI 1.1.0.3f, ComboAM5PI_1.2.0.3inot affected
AMD AMD Ryzen™ 8000 Series Desktop Processors (formerly codenamed "Phoenix")
- ComboAM5PI_1.3.0.0not affected
AMD AMD Ryzen™ 8040 Series Mobile Processors with Radeon™ Graphics
- PhoenixPI-FP8-FP7_1.2.0.0fnot affected
AMD AMD Ryzen™ 9000 Series Desktop Processors
- ComboAM5PI_1.2.0.3inot affected
AMD AMD Ryzen™ 9000 Series Desktop Processors (formerly codenamed "Granite Ridge")
- ComboAM5PI_1.3.0.0not affected
AMD AMD Ryzen™ 9000HX Series Processors
- FireRangeFL1PI 1.0.0.0dnot affected
Same product
amd: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-36326Missing authorization in AMD RomArmor could allow an attacker to bypass ROMArmor protections during system resume from a standby state, pote33Monitor
- CVE-2025-48518Improper input validation in AMD Graphics Driver could allow a local attacker to write out of bounds, potentially resulting in loss of integ27Monitor
- CVE-2025-0040Improper access control between the Joint Test Action Group (JTAG) and Advanced Extensible Interface (AXI) could allow an attacker with phys21Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
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.
No history yet (it accumulates with the daily EPSS job).
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
- Physical access to the device is required.
- Administrator privileges are required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Physical
- Attack complexity
- High
- Privileges required
- High
- User interaction
- A
- Scope
- X
Weakness class (CWE)
CWE-1072 · Data Resource Access without Use of Connection PoolingCVSS vector
CVSS:4.0/AV:P/AC:H/AT:P/PR:H/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
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
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.