CVE-2022-27672

MEDIUMNVD 4.74.7—
EchelonGraph scoreMEDIUM confidence

Score 4.7 from GitHub Security Advisory published 2023-03-01. NVD baseline CVSS 4.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
4.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 4.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
4.7
EG Score
4.7MEDIUMmedium confidence
EG Risk
26
EG Risk 26/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity47% × 45%
Exploitation0% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.3%
EPSS %ILE
19th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

March 1, 2023

Last Modified

April 13, 2026

References (5)

Vendor Advisories for CVE-2022-27672(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(21)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-buildinfo-6.1.0-1008-oem (6.1.0-1008.8) @ jammy2026-05-22ubuntu
ubuntulinux-image-lowlatency (5.19.0.1024.20) @ kinetic2026-05-22ubuntu
ubuntulinux-modules-5.15.0-72-lowlatency (5.15.0-72.79) @ jammy2026-05-22ubuntu
ubuntulinux-headers-5.15.0-1029-raspi-nolpae (5.15.0-1029.31) @ jammy2026-05-22ubuntu
ubuntulinux-tools-gkeop-5.15 (5.15.0.1020.19) @ jammy2026-05-22ubuntu
ubuntulinux-ibm-cloud-tools-common (5.19.0-1022.24) @ kinetic2026-05-22ubuntu
ubuntulinux-image-5.15.0-1030-intel-iotg (5.15.0-1030.35~20.04.1) @ focal2026-05-22ubuntu
ubuntulinux-buildinfo-5.19.0-1024-gcp (5.19.0-1024.26) @ kinetic2026-05-22ubuntu
ubuntulinux-tools-intel-iotg (5.15.0.1030.29) @ jammy2026-05-22ubuntu
ubuntulinux-virtual-hwe-18.04-edge (5.4.0.156.152) @ focal2026-05-22ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.4.0-1027 (5.4.0-1027.31) @ focal2026-05-22ubuntu
ubuntulinux-tools-kvm (4.15.0.1145.136) @ bionic2026-05-22ubuntu
ubuntulinux-tools-azure-lts-20.04 (5.4.0.1114.107) @ focal2026-05-22ubuntu
ubuntulinux-tools-ibm-lts-20.04 (5.4.0.1054.83) @ focal2026-05-22ubuntu
ubuntulinux-tools-azure-edge (5.4.0.1113.86) @ bionic2026-05-22ubuntu
ubuntulinux-tools-oem-22.04b (6.0.0.1021.21) @ jammy2026-05-22ubuntu
ubuntulinux-tools-azure (4.15.0.1170.136) @ trusty2026-05-22ubuntu
ubuntulinux-tools-gke-5.4 (5.4.0.1105.110) @ focal2026-05-22ubuntu
ubuntulinux-virtual-hwe-16.04-edge (4.15.0.218.2) @ xenial2026-05-22ubuntu
redhatkernel-0:5.14.0-284.40.1.el9_22023-11-21redhat
redhatkernel-rt-0:5.14.0-284.40.1.rt14.325.el9_22023-11-21redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(16 across 13 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.12-1: fixed in 6.1.12-1
—
xen—
  • every version up to 4.17.0+46-gaaf74a532c-1: fixed in 4.17.0+46-gaaf74a532c-1
—
Debian:13(2)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.12-1: fixed in 6.1.12-1
—
xen—
  • every version up to 4.17.0+46-gaaf74a532c-1: fixed in 4.17.0+46-gaaf74a532c-1
—
Debian:14(2)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.12-1: fixed in 6.1.12-1
—
xen—
  • every version up to 4.17.0+46-gaaf74a532c-1: fixed in 4.17.0+46-gaaf74a532c-1
—
Alpine:v3.16(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.16.4-r0: fixed in 4.16.4-r0
—
Alpine:v3.17(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.16.4-r0: fixed in 4.16.4-r0
—
Alpine:v3.18(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.17.0-r2: fixed in 4.17.0-r2
—
Alpine:v3.19(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.17.0-r2: fixed in 4.17.0-r2
—
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.17.0-r2: fixed in 4.17.0-r2
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.17.0-r2: fixed in 4.17.0-r2
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.17.0-r2: fixed in 4.17.0-r2
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.17.0-r2: fixed in 4.17.0-r2
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
xen—
  • every version up to 4.17.0-r2: fixed in 4.17.0-r2
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)
  • every version on: no fix on record
—

Additional Vendor Advisories

(19)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 8× in last 7d / 29× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 219 total refreshes for this CVE.

  1. 2026-10-09 20:04 UTCEPSS rescore
  2. 2026-10-08 16:40 UTCEPSS rescore
  3. 2026-10-07 23:45 UTCEPSS rescore
  4. 2026-10-07 19:05 UTCOSV refresh
  5. 2026-10-06 15:14 UTCEPSS rescore
  6. 2026-10-05 17:40 UTCEPSS rescore
  7. 2026-10-04 23:19 UTCEPSS rescore
  8. 2026-10-03 14:23 UTCEPSS rescore
  9. 2026-10-02 16:23 UTCEPSS rescore
  10. 2026-09-30 15:53 UTCEG score recompute
  11. 2026-09-30 15:00 UTCEPSS rescore
  12. 2026-09-29 15:16 UTCEPSS rescore
  13. 2026-09-28 13:48 UTCEPSS rescore
  14. 2026-09-27 13:42 UTCEPSS rescore
  15. 2026-09-26 15:54 UTCEPSS rescore
  16. 2026-09-26 00:22 UTCEPSS rescore
  17. 2026-09-24 14:00 UTCEPSS rescore
  18. 2026-09-23 13:45 UTCEPSS rescore
  19. 2026-09-22 14:44 UTCEPSS rescore
  20. 2026-09-20 20:13 UTCEPSS rescore
  21. 2026-09-19 15:38 UTCEPSS rescore
  22. 2026-09-18 19:24 UTCEPSS rescore
  23. 2026-09-18 01:06 UTCOSV refresh
  24. 2026-09-16 14:05 UTCEPSS rescore
  25. 2026-09-15 03:06 UTCEPSS rescore
Show 75 more
  1. 2026-09-13 16:44 UTCEPSS rescore
  2. 2026-09-12 14:57 UTCEPSS rescore
  3. 2026-09-11 14:49 UTCEPSS rescore
  4. 2026-09-11 09:33 UTCEPSS rescore
  5. 2026-09-08 21:57 UTCEPSS rescore
  6. 2026-09-07 15:58 UTCEPSS rescore
  7. 2026-09-06 13:45 UTCEPSS rescore
  8. 2026-09-05 15:25 UTCEPSS rescore
  9. 2026-09-04 13:57 UTCEPSS rescore
  10. 2026-09-04 13:57 UTCEPSS rescore
  11. 2026-09-04 05:04 UTCEPSS rescore
  12. 2026-09-02 14:09 UTCEPSS rescore
  13. 2026-09-01 13:51 UTCEPSS rescore
  14. 2026-08-30 19:14 UTCEPSS rescore
  15. 2026-08-30 01:43 UTCOSV refresh
  16. 2026-08-30 01:19 UTCEPSS rescore
  17. 2026-08-28 21:38 UTCEPSS rescore
  18. 2026-08-27 14:22 UTCEPSS rescore
  19. 2026-08-26 14:43 UTCEPSS rescore
  20. 2026-08-25 13:46 UTCEPSS rescore
  21. 2026-08-24 14:13 UTCEPSS rescore
  22. 2026-08-23 00:16 UTCEPSS rescore
  23. 2026-08-21 23:46 UTCEPSS rescore
  24. 2026-08-20 22:52 UTCEPSS rescore
  25. 2026-08-19 17:01 UTCEPSS rescore
  26. 2026-08-18 13:45 UTCEPSS rescore
  27. 2026-08-17 13:44 UTCEPSS rescore
  28. 2026-08-16 14:53 UTCEPSS rescore
  29. 2026-08-16 02:11 UTCEPSS rescore
  30. 2026-08-15 01:27 UTCEPSS rescore
  31. 2026-08-13 21:57 UTCEPSS rescore
  32. 2026-08-13 12:21 UTCOSV refresh
  33. 2026-08-12 13:48 UTCEPSS rescore
  34. 2026-08-11 13:38 UTCEPSS rescore
  35. 2026-08-09 13:44 UTCEPSS rescore
  36. 2026-08-08 16:34 UTCEPSS rescore
  37. 2026-08-07 16:24 UTCEPSS rescore
  38. 2026-08-06 13:44 UTCEPSS rescore
  39. 2026-08-05 19:15 UTCEPSS rescore
  40. 2026-08-04 15:07 UTCEPSS rescore
  41. 2026-08-04 10:35 UTCEPSS rescore
  42. 2026-08-01 04:13 UTCEPSS rescore
  43. 2026-07-30 16:25 UTCEPSS rescore
  44. 2026-07-30 01:28 UTCEPSS rescore
  45. 2026-07-28 19:51 UTCOSV refresh
  46. 2026-07-28 15:33 UTCEPSS rescore
  47. 2026-07-26 14:52 UTCEPSS rescore
  48. 2026-07-25 14:15 UTCEPSS rescore
  49. 2026-07-24 14:15 UTCEPSS rescore
  50. 2026-07-24 14:15 UTCEPSS rescore
  51. 2026-07-23 14:16 UTCEPSS rescore
  52. 2026-07-23 14:16 UTCEPSS rescore
  53. 2026-07-23 02:10 UTCEG score recompute
  54. 2026-07-22 22:57 UTCEG score recompute
  55. 2026-07-22 14:06 UTCEPSS rescore
  56. 2026-07-22 14:06 UTCEPSS rescore
  57. 2026-07-21 15:22 UTCEPSS rescore
  58. 2026-07-21 15:22 UTCEPSS rescore
  59. 2026-07-20 17:05 UTCEPSS rescore
  60. 2026-07-19 14:29 UTCEPSS rescore
  61. 2026-07-19 02:27 UTCEPSS rescore
  62. 2026-07-19 02:27 UTCEPSS rescore
  63. 2026-07-18 10:03 UTCEPSS rescore
  64. 2026-07-18 10:02 UTCEPSS rescore
  65. 2026-07-16 17:00 UTCEPSS rescore
  66. 2026-07-15 16:56 UTCEPSS rescore
  67. 2026-07-15 16:56 UTCEPSS rescore
  68. 2026-07-15 01:58 UTCEPSS rescore
  69. 2026-07-15 01:58 UTCEPSS rescore
  70. 2026-07-13 22:27 UTCEPSS rescore
  71. 2026-07-13 06:11 UTCEPSS rescore
  72. 2026-07-13 06:11 UTCEPSS rescore
  73. 2026-07-12 05:44 UTCEPSS rescore
  74. 2026-07-12 05:44 UTCEPSS rescore
  75. 2026-07-11 12:41 UTCOSV refresh

Related CVEs(same product + same vendor)

Frequently asked(5)

What is CVE-2022-27672?
CVE-2022-27672 is a medium vulnerability published on March 1, 2023. 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.
When was CVE-2022-27672 disclosed?
CVE-2022-27672 was first published on March 1, 2023, with the most recent update on April 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-27672 actively exploited?
CVE-2022-27672 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (19th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-27672?
CVE-2022-27672 has a CVSS v3 base score of 4.7 (NVD).
How do I remediate CVE-2022-27672?
A fix for CVE-2022-27672 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-27672 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-27672

Explore →

Is Your Infrastructure Affected by CVE-2022-27672?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs