CVE-2024-36354: Improper input validation for DIMM serial presence detect (SPD) metadata could allow an attacker with physical access, ring0 access on a…
Noroxi assessment
Priority: Monitor (action score 30/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.16% (FIRST EPSS).
- Someone with local access to the system can trigger it. Administrator privileges are required. No user action is 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
Improper input validation for DIMM serial presence detect (SPD) metadata could allow an attacker with physical access, ring0 access on a system with a non-compliant DIMM, or control over the Root of Trust for BIOS update, to bypass SMM isolation potentially resulting in arbitrary code execution at the SMM level.
- Published
- Sep 6, 2025
- Updated
- Nov 9, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- CWE-1231
Report tools
Action score
30
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 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
- 7.5
- NVD has not scored this yet; the score shown is the CNA’s.
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.
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.
—
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 Athlon™ 3000 Series Desktop Processors with Radeon™ Graphics
- ComboAM4PI_1.0.0.Cnot affected
AMD AMD Athlon™ 3000 Series Mobile Processors with Radeon™ Graphics
- PicassoPI-FP5_1.0.1.2anot affected
AMD AMD EPYC™ 4004 Series Processors
- ComboAM5PI_1.2.0.2anot affected
AMD AMD EPYC™ 7001 Series Processors
- Naples 1.0.0.Qnot affected
AMD AMD EPYC™ 7002 Series Processors
- Rome PI 1.0.0.Mnot affected
AMD AMD EPYC™ 7003 Series Processors
- MilanPI 1.0.0.Dnot affected
AMD AMD EPYC™ 8004 Series Processors
- GenoaPI 1.0.0.Dnot affected
AMD AMD EPYC™ 9004 Series Processors
- GenoaPI 1.0.0.D, GenoaPI 1.0.0.Dnot affected
AMD AMD EPYC™ Embedded 3000 Series Processors
- SnowyOwl PI 1.1.0.Fnot affected
AMD AMD EPYC™ Embedded 7002 Series Processors
- EmbRomePI-SP3_1.0.0.Enot affected
AMD AMD EPYC™ Embedded 7003 Series Processors
- EmbMilanPI-SP3 1.0.0.Anot affected
AMD AMD EPYC™ Embedded 9004 Series Processors
- EmbGenoaPI-SP5 1.0.0.8not affected
Same product
amd: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-21947Improper input validation in the system management mode (SMM) could allow a privileged attacker to overwrite arbitrary memory potentially…30Monitor
- CVE-2024-21970Improper validation of an array index in the AND power Management Firmware could allow a privileged attacker to corrupt AGESA memory…17Monitor
- CVE-2023-31330An out-of-bounds read in the ASP could allow a privileged attacker with access to a malicious bootloader to potentially read sensitive…10Monitor
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.
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.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-1231 · Improper Prevention of Lock Bit ModificationCVSS vector
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H
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.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.