CVE-2022-23820: Failure to validate the AMD SMM communication buffer may allow an attacker to corrupt the SMRAM potentially leading to arbitrary code execut
Noroxi assessment
Priority: Monitor (action score 39/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.69% (FIRST EPSS); higher than 53.3% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: kernel-firmware (openSUSE:Leap 15.5) 20230724-150500.3.9.1; kernel-firmware (openSUSE:Leap Micro 5.3) 20220509-150400.4.25.1; kernel-firmware (openSUSE:Tumbleweed) 20231128-1.1.
- Severity is disputed: the assigning authority (CNA) scores it 7.5, NVD 9.8.
Low priority for now. Upgrade to kernel-firmware (openSUSE:Leap 15.5) 20230724-150500.3.9.1; kernel-firmware (openSUSE:Leap Micro 5.3) 20220509-150400.4.25.1; kernel-firmware (openSUSE:Tumbleweed) 20231128-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
Failure to validate the AMD SMM communication buffer may allow an attacker to corrupt the SMRAM potentially leading to arbitrary code execution.
- Published
- Nov 14, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.6% · 53th percentile
- CWE
- CWE-20
Report tools
Action score
39
Monitor
Low priority for now.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
CNA vs NVD score
- NVD
- 9.8
- CNA · AMD
- 7.5
- 2.3 point gap
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H
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
- 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 | ryzen 9 3900 firmware | cpe:2.3:o:amd:ryzen_9_3900_firmware |
| amd | ryzen 9 3900 | cpe:2.3:h:amd:ryzen_9_3900 |
| amd | ryzen 9 3900x firmware | cpe:2.3:o:amd:ryzen_9_3900x_firmware |
| amd | ryzen 9 3900x | cpe:2.3:h:amd:ryzen_9_3900x |
| amd | ryzen 9 3900xt firmware | cpe:2.3:o:amd:ryzen_9_3900xt_firmware |
| amd | ryzen 9 3900xt | cpe:2.3:h:amd:ryzen_9_3900xt |
| amd | ryzen 9 3950x firmware | cpe:2.3:o:amd:ryzen_9_3950x_firmware |
| amd | ryzen 9 3950x | cpe:2.3:h:amd:ryzen_9_3950x |
| amd | ryzen 7 3700x firmware | cpe:2.3:o:amd:ryzen_7_3700x_firmware |
| amd | ryzen 7 3700x | cpe:2.3:h:amd:ryzen_7_3700x |
| amd | ryzen 7 3800x firmware | cpe:2.3:o:amd:ryzen_7_3800x_firmware |
| amd | ryzen 7 3800x | cpe:2.3:h:amd:ryzen_7_3800x |
and 188 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- amd athlon 3015ce firmwarepollockpi-ft5_1.0.0.5
- amd athlon 3015e firmwarepollockpi-ft5_1.0.0.5
- amd ryzen 3 3100 firmwarecomboam4_pi_1.0.0.9
- amd ryzen 3 3100 firmwarecomboam4_v2_pi_1.2.0.8
- amd ryzen 3 3300u firmwarepicassopi-fp5_1.0.0.e
- amd ryzen 3 3300x firmwarecomboam4_pi_1.0.0.9
- amd ryzen 3 3300x firmwarecomboam4_v2_pi_1.2.0.8
- amd ryzen 3 3350u firmwarepicassopi-fp5_1.0.0.e
- amd ryzen 3 4300u firmwarerenoirpi-fp6_1.0.0.9
- amd ryzen 3 5100 firmwarecomboam4v2_pi_1.2.0.8
- amd ryzen 3 5125c firmwarecezannepi-fp6_1.0.0.b
- amd ryzen 3 5400u firmwarecezannepi-fp6_1.0.0.b
- amd ryzen 3 5425u firmwarecezannepi-fp6_1.0.0.b
- amd ryzen 3 7335u firmwarerembrandtpi-fp7_1.0.0.2
- amd ryzen 5 3450u firmwarepicassopi-fp5_1.0.0.e
- amd ryzen 5 3500 firmwarecomboam4_pi_1.0.0.9
- amd ryzen 5 3500 firmwarecomboam4_v2_pi_1.2.0.8
- amd ryzen 5 3500c firmwarepicassopi-fp5_1.0.0.e
- amd ryzen 5 3500u firmwarepicassopi-fp5_1.0.0.e
- amd ryzen 5 3500x firmwarecomboam4_pi_1.0.0.9
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 3rd Gen AMD EPYC™ Processors
- variousaffected
AMD AMD Athlon™ 3000 Series Desktop Processors with Radeon™ Graphics “Picasso” AM4
- variousaffected
AMD AMD Athlon™ 3000 Series Mobile Processors with Radeon™ Graphics “Pollock”
- variousaffected
AMD AMD EPYC™ Embedded 7003
- various, variousaffected
AMD AMD Ryzen™ 3000 Series Mobile Processor with Radeon™ Graphics “Picasso” FP5
- variousaffected
AMD AMD Ryzen™ 4000 Series Mobile Processors with Radeon™ Graphics “Renoir” FP6
- variousaffected
AMD AMD Ryzen™ 5000 Series Desktop Processor with Radeon™ Graphics “Cezanne”
- variousaffected
AMD AMD Ryzen™ 5000 Series Desktop Processors “Vermeer”
- variousaffected
AMD AMD Ryzen™ 5000 Series Mobile Processors with Radeon™ Graphics “Cezanne”
- variousaffected
AMD AMD Ryzen™ 5000 Series Mobile Processors with Radeon™ Graphics “Lucienne”
- variousaffected
AMD AMD Ryzen™ 5000 Series Processors with Radeon™ Graphics “Barcelo”
- variousaffected
AMD AMD Ryzen™ 6000 Series Processors with Radeon™ Graphics "Rembrandt"
- variousaffected
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.5 | kernel-firmware | before 20230724-150500.3.9.1 | 20230724-150500.3.9.1 |
| openSUSE:Leap Micro 5.3 | kernel-firmware | before 20220509-150400.4.25.1 | 20220509-150400.4.25.1 |
| openSUSE:Tumbleweed | kernel-firmware | before 20231128-1.1 | 20231128-1.1 |
| openSUSE:Tumbleweed | kernel-firmware-ath12k | before 20250206-1.1 | 20250206-1.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP1-LTSS | kernel-firmware | before 20200107-150100.3.40.1 | 20200107-150100.3.40.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP3-ESPOS | kernel-firmware | before 20210208-150300.4.19.1 | 20210208-150300.4.19.1 |
| SUSE:Linux Enterprise Micro 5.3 | kernel-firmware | before 20220509-150400.4.25.1 | 20220509-150400.4.25.1 |
| SUSE:Linux Enterprise Micro 5.5 | kernel-firmware | before 20230724-150500.3.9.1 | 20230724-150500.3.9.1 |
| SUSE:Linux Enterprise Server 12 SP5 | kernel-firmware | before 20190618-5.34.1 | 20190618-5.34.1 |
Same product
amd: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-23821Improper access control in System Management Mode (SMM) may allow an attacker to write to SPI ROM potentially leading to arbitrary code exec39Monitor
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 | 20230724-150500.3.9.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:kernel-firmware-ath12k | 20250206-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| suse:kernel-firmware | 20210208-150300.4.19.1 · SUSE:Linux Enterprise High Performance Computing 15 SP3-ESPOS | Package registry (OSV) |
| suse:kernel-firmware | 20230724-150500.3.9.1 · SUSE:Linux Enterprise Micro 5.5 | 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.
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
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-20 · Improper Input ValidationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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
- Server Side Include (SSI) InjectionCAPEC-101likelihood: High · High
- Cross Zone ScriptingCAPEC-104likelihood: Medium · High
- Command Line Execution through SQL InjectionCAPEC-108likelihood: Low · Very High
- Object Relational Mapping InjectionCAPEC-109likelihood: Low · High
- SQL Injection through SOAP Parameter TamperingCAPEC-110likelihood: High · Very High
- Double EncodingCAPEC-120likelihood: Low · Medium
- Subverting Environment Variable ValuesCAPEC-13likelihood: High · Very High
ATT&CK techniques
- Obfuscated Files or InformationT1027
- Masquerading: Invalid Code SignatureT1036.001
- Steal Web Session CookieT1539
- Subvert Trust Controls: Code SigningT1553.002
- Impair Defenses:Impair Command History LoggingT1562.003
- Hijack Execution Flow:Dynamic Linker HijackingT1574.006
- Hijack Execution Flow:Path Interception by PATH Environment VariableT1574.007
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.