CVE-2020-12965· NVD / CVE Program· CNA AMD

When combined with specific software sequences, AMD CPUs may transiently execute non-canonical loads and store using only the lower 48 addre

Noroxi assessment

Priority: Monitor (action score 31/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: 2.3% (FIRST EPSS); higher than 83.4% 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: spectre-meltdown-checker (openSUSE:Tumbleweed) 26.36.0602723-1.1.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to spectre-meltdown-checker (openSUSE:Tumbleweed) 26.36.0602723-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

When combined with specific software sequences, AMD CPUs may transiently execute non-canonical loads and store using only the lower 48 address bits potentially resulting in data leakage.

HighCVSS 7.5 · v3.1—No exploit Fix available

Pre-auth

Published: Feb 4, 2022
Updated: Jun 16, 2026
EPSS: 2.3% · 83th percentile
CWE: CWE-74

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 30 / 40 · 7.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 1 / 30 · 2.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

Is your version affected? Check it

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 help

Affected 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 pro 5650g firmware	cpe:2.3:o:amd:ryzen_pro_5650g_firmware
amd	ryzen pro 5650g	cpe:2.3:h:amd:ryzen_pro_5650g
amd	ryzen pro 5650ge firmware	cpe:2.3:o:amd:ryzen_pro_5650ge_firmware
amd	ryzen pro 5650ge	cpe:2.3:h:amd:ryzen_pro_5650ge
amd	ryzen pro 5750g firmware	cpe:2.3:o:amd:ryzen_pro_5750g_firmware
amd	ryzen pro 5750g	cpe:2.3:h:amd:ryzen_pro_5750g
amd	ryzen pro 5750ge firmware	cpe:2.3:o:amd:ryzen_pro_5750ge_firmware
amd	ryzen pro 5750ge	cpe:2.3:h:amd:ryzen_pro_5750ge
amd	ryzen pro 5350g firmware	cpe:2.3:o:amd:ryzen_pro_5350g_firmware
amd	ryzen pro 5350g	cpe:2.3:h:amd:ryzen_pro_5350g
amd	ryzen pro 5350ge firmware	cpe:2.3:o:amd:ryzen_pro_5350ge_firmware
amd	ryzen pro 5350ge	cpe:2.3:h:amd:ryzen_pro_5350ge

and 114 more

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

amd athlon 3050ge firmwareall versions
amd athlon 3150g firmwareall versions
amd athlon 3150ge firmwareall versions
amd athlon gold pro 3150g firmwareall versions
amd athlon gold pro 3150ge firmwareall versions
amd athlon pro 200ge firmwareall versions
amd athlon pro 300ge firmwareall versions
amd athlon silver pro 3125ge firmwareall versions
amd ryzen 4300g firmwareall versions
amd ryzen 4300ge firmwareall versions
amd ryzen 4600g firmwareall versions
amd ryzen 4600ge firmwareall versions
amd ryzen 4700g firmwareall versions
amd ryzen 4700ge firmwareall versions
amd ryzen 5300g firmwareall versions
amd ryzen 5300ge firmwareall versions
amd ryzen 5600g firmwareall versions
amd ryzen 5600ge firmwareall versions
amd ryzen 5600x firmwareall versions
amd ryzen 5700g 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 All supported processors
- unspecified and later · before undefinedaffected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
openSUSE:Tumbleweed	spectre-meltdown-checker	before 26.36.0602723-1.1	26.36.0602723-1.1

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:spectre-meltdown-checker	26.36.0602723-1.1 · openSUSE:Tumbleweed	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.

EPSS, last 120 days

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 researchers

Finders, 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).