CVE-2022-27672: When SMT is enabled, certain AMD processors may speculatively execute instructions using a target from the sibling thread after an SMT mode
Noroxi assessment
Priority: Monitor (action score 18/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.28% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: xen (Alpine:v3.16) 4.16.4-r0; xen (Alpine:v3.18) 4.17.0-r2; linux (Debian:12) 6.1.12-1.
- Mentioned 3 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to xen (Alpine:v3.16) 4.16.4-r0; xen (Alpine:v3.18) 4.17.0-r2; linux (Debian:12) 6.1.12-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 SMT is enabled, certain AMD processors may speculatively execute instructions using a target from the sibling thread after an SMT mode switch potentially resulting in information disclosure.
- Published
- Mar 1, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 20th percentile
- CWE
- —
Report tools
Action score
18
Monitor
Low priority for now.
- CVSS
- 18 / 40 · 4.7 / 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.
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 | athlon x4 750 firmware | cpe:2.3:o:amd:athlon_x4_750_firmware |
| amd | athlon x4 750 | cpe:2.3:h:amd:athlon_x4_750 |
| amd | athlon x4 760k firmware | cpe:2.3:o:amd:athlon_x4_760k_firmware |
| amd | athlon x4 760k | cpe:2.3:h:amd:athlon_x4_760k |
| amd | athlon x4 830 firmware | cpe:2.3:o:amd:athlon_x4_830_firmware |
| amd | athlon x4 830 | cpe:2.3:h:amd:athlon_x4_830 |
| amd | athlon x4 840 firmware | cpe:2.3:o:amd:athlon_x4_840_firmware |
| amd | athlon x4 840 | cpe:2.3:h:amd:athlon_x4_840 |
| amd | athlon x4 860k firmware | cpe:2.3:o:amd:athlon_x4_860k_firmware |
| amd | athlon x4 860k | cpe:2.3:h:amd:athlon_x4_860k |
| amd | athlon x4 870k firmware | cpe:2.3:o:amd:athlon_x4_870k_firmware |
| amd | athlon x4 870k | cpe:2.3:h:amd:athlon_x4_870k |
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 a10-9600p firmwareall versions
- amd a10-9630p firmwareall versions
- amd a12-9700p firmwareall versions
- amd a12-9730p firmwareall versions
- amd a4-9120 firmwareall versions
- amd a4-9120c firmwareall versions
- amd a6-9210 firmwareall versions
- amd a6-9220 firmwareall versions
- amd a6-9220c firmwareall versions
- amd a9-9410 firmwareall versions
- amd a9-9420 firmwareall versions
- amd athlon gold 3150c firmwareall versions
- amd athlon gold 3150u firmwareall versions
- amd athlon gold 7220u firmwareall versions
- amd athlon pro 300u firmwareall versions
- amd athlon pro 3045b firmwareall versions
- amd athlon pro 3145b firmwareall versions
- amd athlon silver 3050c firmwareall versions
- amd athlon silver 3050e firmwareall versions
- amd athlon silver 3050u 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 1st Gen AMD EPYC™ Processors
- Contact your OS vendoraffected
AMD 2nd Gen AMD EPYC™ Processors
- Contact your OS vendoraffected
AMD 2nd Gen AMD Ryzen™ Threadripper™ Processors
- Contact your OS vendoraffected
AMD 3rd Gen AMD Ryzen™ Threadripper™ Processors
- Contact your OS vendoraffected
AMD 7th Generation AMD A-Series APUs
- Contact your OS vendoraffected
AMD Athlon™ Mobile Processors
- Contact your OS vendoraffected
AMD Athlon™ X4 Processor
- Contact your OS vendoraffected
AMD Ryzen™ 2000 Series Processors
- Contact your OS vendoraffected
AMD Ryzen™ 3000 Series Processors
- Contact your OS vendoraffected
AMD Ryzen™ 4000 Series Processors
- Contact your OS vendoraffected
AMD Ryzen™ 5000 Series Processors
- Contact your OS vendoraffected
AMD Ryzen™ Threadripper™ PRO Processor
- Contact your OS vendoraffected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.16 | xen | before 4.16.4-r0 | 4.16.4-r0 |
| Alpine:v3.18 | xen | before 4.17.0-r2 | 4.17.0-r2 |
| Debian:12 | linux | before 6.1.12-1 | 6.1.12-1 |
| Debian:12 | xen | before 4.17.0+46-gaaf74a532c-1 | 4.17.0+46-gaaf74a532c-1 |
| openSUSE:Leap Micro 5.3 | xen | before 4.16.3_04-150400.4.22.1 | 4.16.3_04-150400.4.22.1 |
| openSUSE:Tumbleweed | xen | before 4.17.0_04-3.1 | 4.17.0_04-3.1 |
| Red Hat:rhel_eus:9.2::appstream | bpftool-debuginfo | before 0:7.0.0-284.40.1.el9_2 | 0:7.0.0-284.40.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-64k-debug-debuginfo | before 0:5.14.0-284.40.1.el9_2 | 0:5.14.0-284.40.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-64k-debug-devel | before 0:5.14.0-284.40.1.el9_2 | 0:5.14.0-284.40.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-64k-debug-devel-matched | before 0:5.14.0-284.40.1.el9_2 | 0:5.14.0-284.40.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-64k-debuginfo | before 0:5.14.0-284.40.1.el9_2 | 0:5.14.0-284.40.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-64k-devel | before 0:5.14.0-284.40.1.el9_2 | 0:5.14.0-284.40.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-64k-devel-matched | before 0:5.14.0-284.40.1.el9_2 | 0:5.14.0-284.40.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-debug-debuginfo | before 0:5.14.0-284.40.1.el9_2 | 0:5.14.0-284.40.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-debug-devel | before 0:5.14.0-284.40.1.el9_2 | 0:5.14.0-284.40.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-debug-devel-matched | before 0:5.14.0-284.40.1.el9_2 | 0:5.14.0-284.40.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-debuginfo | before 0:5.14.0-284.40.1.el9_2 | 0:5.14.0-284.40.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-debuginfo-common-aarch64 | before 0:5.14.0-284.40.1.el9_2 | 0:5.14.0-284.40.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-debuginfo-common-ppc64le | before 0:5.14.0-284.40.1.el9_2 | 0:5.14.0-284.40.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-debuginfo-common-s390x | before 0:5.14.0-284.40.1.el9_2 | 0:5.14.0-284.40.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-debuginfo-common-x86_64 | before 0:5.14.0-284.40.1.el9_2 | 0:5.14.0-284.40.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-devel | before 0:5.14.0-284.40.1.el9_2 | 0:5.14.0-284.40.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-devel-matched | before 0:5.14.0-284.40.1.el9_2 | 0:5.14.0-284.40.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-doc | before 0:5.14.0-284.40.1.el9_2 | 0:5.14.0-284.40.1.el9_2 |
+59
Same product
amd: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-23825Aliases in the branch predictor may cause some AMD processors to predict the wrong branch type potentially leading to information disclosure26Monitor
- CVE-2022-23823A potential vulnerability in some AMD processors using frequency scaling may allow an authenticated attacker to execute a timing attack to p26Monitor
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 |
|---|---|---|
| alpine:xen | 4.16.4-r0 · Alpine:v3.16 | Package registry (OSV) |
| debian:linux | 6.1.12-1 · Debian:12 | Package registry (OSV) |
| debian:xen | 4.17.0+46-gaaf74a532c-1 · Debian:12 | Package registry (OSV) |
| opensuse:xen | 4.16.3_04-150400.4.22.1 · openSUSE:Leap Micro 5.3 | Package registry (OSV) |
| red hat:bpftool-debuginfo | 0:7.0.0-284.40.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:5.14.0-284.40.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:5.14.0-284.40.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:5.14.0-284.40.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:5.14.0-284.40.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:5.14.0-284.40.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:5.14.0-284.40.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:5.14.0-284.40.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:5.14.0-284.40.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:5.14.0-284.40.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:5.14.0-284.40.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-aarch64 | 0:5.14.0-284.40.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| suse:xen | 4.16.3_04-150400.4.22.1 · SUSE:Linux Enterprise Micro 5.3 | 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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-23-0661 · Nov 24, 2023(RedHat Güvenlik Güncellemesi)
- TR-23-0391 · Jul 10, 2023(Linux Kernel Güncellemesi)
- TR-23-0271 · May 17, 2023(Linux Kernel Güncellemesi)
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.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
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.