VulnSocial

CVE-2023-20569Patch(amd / debian_linux)

LOWCVSS 4.7 · MEDIUM

Signal is active with 2 mentions in latest observed window

Immediate actions

  • Patch amd debian_linux systems immediately

Recommended action window: Monitor and triage in normal cycle

NVD description

A side channel vulnerability on some of the AMD CPUs may allow an attacker to influence the return address prediction. This may result in speculative execution at an attacker-controlled address, potentially leading to information disclosure.

amd CVEsBack to dashboard
1.5/ 10 priority

Sources & remediation

Exploit / PoC references
Vendor / third-party advisories
Other references
Weakness type (CWE)
CWE-203

Priority

LOW

Exploitation

NONE

PoC

YES

Patch

AVAILABLE

Momentum

STABLE

Are you affected?

If you run products in this scope, you should treat this CVE as relevant to your environment.

  • debian_linux
  • epyc_72f3
  • epyc_72f3_firmware
  • epyc_7313

Threat summary

  • Patch or workaround signal is available
  • 7 mentions across 3 observed days
  • Momentum state: stable

What's happening

  • Patch or workaround mentioned in 5 signals
  • Technical details provided in 3 signals
  • Disclosure: 2 classified signals
  • Peaked 1d ago at 3 mentions (2026-10-22); latest day: 2
  • 7 total mentions across 3 days

Affected systems

Vendors
amddebianfedoraprojectmicrosoft
Products
debian_linuxepyc_72f3epyc_72f3_firmwareepyc_7313epyc_7313_firmwareepyc_7313pepyc_7313p_firmwareepyc_7343epyc_7343_firmwareepyc_7373x

7 versions affected across 296 products

Deep dive

Activity timeline7 mentions / 3d
01223Mentions · 2026-08-04: 2Mentions · 2026-10-22: 3Mentions · 2026-10-28: 2Patch / Workaround · 2026-08-04: 2Patch / Workaround · 2026-10-22: 3Technical Details · 2026-08-04: 1Technical Details · 2026-10-28: 208-0410-2210-28
Signal classification2 categories
Patch
571.4%
Disclosure
228.6%
Classification over time
DateTotalLabels
2026-08-042
Patch2
2026-10-223
Patch3
2026-10-282
Disclosure2
Full discourse7 posts
  • Alexey Fateev@superalesha
    Patch

    Bonus. At some point during the day we turned off two kernel security mitigations on the rig: spec_rstack_overflow=off retbleed=off The prefill thread was doing millions of syscalls per second, and on Zen 2 every single one pays the SRSO "safe RET" tax (CVE-2023-20569, the Inception attack). With mitigations off, sched_yield went from 549 ns to 162 ns, minus 70%. End to end it bought a whole +2% prefill. Yes. We disabled a CVE mitigation for two percent. Do not repeat this on any machine that runs code you do not trust, this rig is a local box behind a router and this risk is mine only. The things you do for tokens per second ❤️

    Post summary

    The user disabled kernel mitigations for CVE‑2023‑20569 to gain a 70% performance improvement on a local box; the post provides a workaround but no active exploitation or detailed technical vulnerability data.

    10062736
    7.3K followersView on X
  • Helveticus | Swiss Perspective 🇨🇭@GerberEV
    Patch

    @phoronix This is why embargoes exist: ETH Zurich reported the Inception CPU flaw (CVE-2023-20569) to AMD in February 2023. It went public on 8 Aug 2023, with the Linux fix merged the day before. Leak the details early and that head start is gone. #Linux

    Post summary

    The text discusses the disclosure timeline of CVE-2023-20569 (Inception CPU flaw) and highlights that a Linux kernel fix was merged the day before public disclosure, emphasizing the value of embargoes.

    00010188
    148 followersView on X
  • Alexey Fateev@superalesha
    Patch

    @AIPulseNewsX Kernels have no further optimization possible at the moment. Currently I am at the stage of disabling mitigation of the SRSO / Inception vulnerability (CVE-2023-20569) - a speculative attack on the return address predictor in AMD Zen 1 to 4. 🤡📷

    Post summary

    The author notes they are disabling mitigation for CVE-2023‑20569, a speculative return-address-predictor attack on AMD Zen 1‑4, highlighting a workaround rather than active exploitation.

    10000110
    1.5K followersView on X
  • Helveticus | Swiss Perspective 🇨🇭@GerberEV
    Disclosure

    @TheHackersNews Chains are the real threat model: each flaw looks minor on its own. ETH Zurich's COMSEC group showed this with Inception (CVE-2023-20569), combining phantom speculation with training in transient execution to leak AMD Zen 4 kernel memory at 39 bytes/s. #CyberSecurity

    Post summary

    The tweet discloses technical details of CVE-2023-20569 (Inception), describing a transient execution side-channel leak on AMD Zen 4 by ETH Zurich's COMSEC group, without referencing PoC code, exploits, active exploitation, or patches.

    0000042
    163 followersView on X
  • Helveticus | Swiss Perspective 🇨🇭@GerberEV
    Disclosure

    Chains are the real threat model: each flaw looks minor on its own. ETH Zurich's COMSEC group showed this with Inception (CVE-2023-20569), combining phantom speculation with training in transient execution to leak AMD Zen 4 kernel memory at 39 bytes/s. #CyberSecurity

    Post summary

    The tweet announces CVE-2023-20569's technical mechanism (phantom speculation, transient execution, AMD Zen 4 kernel leak at 39 bytes/s) without mentioning patches, exploits, active in-the-wild usage, or PoC code, serving as a research disclosure.

    0000061
    162 followersView on X
  • Helveticus | Swiss Perspective 🇨🇭@GerberEV
    Patch

    This is why embargoes exist: ETH Zurich reported the Inception CPU flaw (CVE-2023-20569) to AMD in February 2023. It went public on 8 Aug 2023, with the Linux fix merged the day before. Leak the details early and that head start is gone. #Linux

    Post summary

    The text discusses the disclosure timeline of CVE-2023-20569 (Inception CPU flaw) and confirms a Linux fix was merged prior to public disclosure, classifying it primarily as a Patch-related post.

    0000040
    148 followersView on X
  • Helveticus | Swiss Perspective 🇨🇭@GerberEV
    Patch

    Genau dafür gibt es Embargos: Die ETH Zürich meldete die CPU-Lücke Inception (CVE-2023-20569) im Februar 2023 an AMD, öffentlich wurde sie erst am 8.8.2023, der Linux-Fix war am Vortag gemergt. Gehen Details zu früh raus, fehlt genau dieser Vorsprung. #Linux

    Post summary

    The text discusses the disclosure timeline of CVE-2023-20569 (Inception), a CPU vulnerability reported by ETH Zürich to AMD, emphasizing the importance of embargoes as the Linux fix was merged before public disclosure.

    0000034
    148 followersView on X
CPE platform detail301 entries

301 of 301 entries

PartVendorProductVersionTarget SWTarget HW
HWamdepyc_72f3---
OSamdepyc_72f3_firmware---
HWamdepyc_7313---
OSamdepyc_7313_firmware---
HWamdepyc_7313p---
OSamdepyc_7313p_firmware---
HWamdepyc_7343---
OSamdepyc_7343_firmware---
HWamdepyc_7373x---
OSamdepyc_7373x_firmware---
HWamdepyc_73f3---
OSamdepyc_73f3_firmware---
HWamdepyc_7413---
OSamdepyc_7413_firmware---
HWamdepyc_7443---
OSamdepyc_7443_firmware---
HWamdepyc_7443p---
OSamdepyc_7443p_firmware---
HWamdepyc_7453---
OSamdepyc_7453_firmware---
HWamdepyc_7473x---
OSamdepyc_7473x_firmware---
HWamdepyc_74f3---
OSamdepyc_74f3_firmware---
HWamdepyc_7513---
OSamdepyc_7513_firmware---
HWamdepyc_7543---
OSamdepyc_7543_firmware---
HWamdepyc_7543p---
OSamdepyc_7543p_firmware---
HWamdepyc_7573x---
OSamdepyc_7573x_firmware---
HWamdepyc_75f3---
OSamdepyc_75f3_firmware---
HWamdepyc_7643---
OSamdepyc_7643_firmware---
HWamdepyc_7663---
OSamdepyc_7663_firmware---
HWamdepyc_7713---
OSamdepyc_7713_firmware---
HWamdepyc_7713p---
OSamdepyc_7713p_firmware---
HWamdepyc_7763---
OSamdepyc_7763_firmware---
HWamdepyc_7773x---
OSamdepyc_7773x_firmware---
HWamdepyc_9124---
OSamdepyc_9124_firmware---
HWamdepyc_9174f---
OSamdepyc_9174f_firmware---
HWamdepyc_9184x---
OSamdepyc_9184x_firmware---
HWamdepyc_9224---
OSamdepyc_9224_firmware---
HWamdepyc_9254---
OSamdepyc_9254_firmware---
HWamdepyc_9274f---
OSamdepyc_9274f_firmware---
HWamdepyc_9334---
OSamdepyc_9334_firmware---
HWamdepyc_9354---
OSamdepyc_9354_firmware---
HWamdepyc_9354p---
OSamdepyc_9354p_firmware---
HWamdepyc_9374f---
OSamdepyc_9374f_firmware---
HWamdepyc_9384x---
OSamdepyc_9384x_firmware---
HWamdepyc_9454---
OSamdepyc_9454_firmware---
HWamdepyc_9454p---
OSamdepyc_9454p_firmware---
HWamdepyc_9474f---
OSamdepyc_9474f_firmware---
HWamdepyc_9534---
OSamdepyc_9534_firmware---
HWamdepyc_9554---
OSamdepyc_9554_firmware---
HWamdepyc_9554p---
OSamdepyc_9554p_firmware---
HWamdepyc_9634---
OSamdepyc_9634_firmware---
HWamdepyc_9654---
OSamdepyc_9654_firmware---
HWamdepyc_9654p---
OSamdepyc_9654p_firmware---
HWamdepyc_9684x---
OSamdepyc_9684x_firmware---
HWamdepyc_9734---
OSamdepyc_9734_firmware---
HWamdepyc_9754---
OSamdepyc_9754_firmware---
HWamdepyc_9754s---
OSamdepyc_9754s_firmware---
HWamdryzen_3_5100---
OSamdryzen_3_5100_firmware---
HWamdryzen_3_5125c---
OSamdryzen_3_5125c_firmware---
HWamdryzen_3_5300g---
OSamdryzen_3_5300g_firmware---
HWamdryzen_3_5300ge---
OSamdryzen_3_5300ge_firmware---
HWamdryzen_3_5300u---
OSamdryzen_3_5300u_firmware---
HWamdryzen_3_5400u---
OSamdryzen_3_5400u_firmware---
HWamdryzen_3_5425u---
OSamdryzen_3_5425u_firmware---
HWamdryzen_3_7335u---
OSamdryzen_3_7335u_firmware---
HWamdryzen_3_7440u---
OSamdryzen_3_7440u_firmware---
HWamdryzen_3_pro_7330u---
OSamdryzen_3_pro_7330u_firmware---
HWamdryzen_5_5500---
OSamdryzen_5_5500_firmware---
HWamdryzen_5_5500u---
OSamdryzen_5_5500u_firmware---
HWamdryzen_5_5560u---
OSamdryzen_5_5560u_firmware---
HWamdryzen_5_5600---
OSamdryzen_5_5600_firmware---
HWamdryzen_5_5600g---
OSamdryzen_5_5600g_firmware---
HWamdryzen_5_5600ge---
OSamdryzen_5_5600ge_firmware---
HWamdryzen_5_5600h---
OSamdryzen_5_5600h_firmware---
HWamdryzen_5_5600hs---
OSamdryzen_5_5600hs_firmware---
HWamdryzen_5_5600u---
OSamdryzen_5_5600u_firmware---
HWamdryzen_5_5600x---
HWamdryzen_5_5600x3d---
OSamdryzen_5_5600x3d_firmware---
OSamdryzen_5_5600x_firmware---
HWamdryzen_5_5625u---
OSamdryzen_5_5625u_firmware---
HWamdryzen_5_6600h---
OSamdryzen_5_6600h_firmware---
HWamdryzen_5_6600hs---
OSamdryzen_5_6600hs_firmware---
HWamdryzen_5_6600u---
OSamdryzen_5_6600u_firmware---
HWamdryzen_5_7500f---
OSamdryzen_5_7500f_firmware---
HWamdryzen_5_7535hs---
OSamdryzen_5_7535hs_firmware---
HWamdryzen_5_7535u---
OSamdryzen_5_7535u_firmware---
HWamdryzen_5_7540u---
OSamdryzen_5_7540u_firmware---
HWamdryzen_5_7600---
OSamdryzen_5_7600_firmware---
HWamdryzen_5_7600x---
OSamdryzen_5_7600x_firmware---
HWamdryzen_5_7640h---
OSamdryzen_5_7640h_firmware---
HWamdryzen_5_7640u---
OSamdryzen_5_7640u_firmware---
HWamdryzen_5_7645hx---
OSamdryzen_5_7645hx_firmware---
HWamdryzen_5_pro_5645---
OSamdryzen_5_pro_5645_firmware---
HWamdryzen_5_pro_7530u---
OSamdryzen_5_pro_7530u_firmware---
HWamdryzen_5_pro_7640hs---
OSamdryzen_5_pro_7640hs_firmware---
HWamdryzen_5_pro_7645---
OSamdryzen_5_pro_7645_firmware---
HWamdryzen_7_5700---
OSamdryzen_7_5700_firmware---
HWamdryzen_7_5700g---
OSamdryzen_7_5700g_firmware---
HWamdryzen_7_5700ge---
OSamdryzen_7_5700ge_firmware---
HWamdryzen_7_5700u---
OSamdryzen_7_5700u_firmware---
HWamdryzen_7_5700x---
OSamdryzen_7_5700x_firmware---
HWamdryzen_7_5800---
OSamdryzen_7_5800_firmware---
HWamdryzen_7_5800h---
OSamdryzen_7_5800h_firmware---
HWamdryzen_7_5800hs---
OSamdryzen_7_5800hs_firmware---
HWamdryzen_7_5800u---
OSamdryzen_7_5800u_firmware---
HWamdryzen_7_5800x---
HWamdryzen_7_5800x3d---
OSamdryzen_7_5800x3d_firmware---
OSamdryzen_7_5800x_firmware---
HWamdryzen_7_5825u---
OSamdryzen_7_5825u_firmware---
HWamdryzen_7_6800h---
OSamdryzen_7_6800h_firmware---
HWamdryzen_7_6800hs---
OSamdryzen_7_6800hs_firmware---
HWamdryzen_7_6800u---
OSamdryzen_7_6800u_firmware---
HWamdryzen_7_7700---
OSamdryzen_7_7700_firmware---
HWamdryzen_7_7700x---
OSamdryzen_7_7700x_firmware---
HWamdryzen_7_7735hs---
OSamdryzen_7_7735hs_firmware---
HWamdryzen_7_7735u---
OSamdryzen_7_7735u_firmware---
HWamdryzen_7_7736u---
OSamdryzen_7_7736u_firmware---
HWamdryzen_7_7745hx---
OSamdryzen_7_7745hx_firmware---
HWamdryzen_7_7800x3d---
OSamdryzen_7_7800x3d_firmware---
HWamdryzen_7_7840h---
OSamdryzen_7_7840h_firmware---
HWamdryzen_7_7840u---
OSamdryzen_7_7840u_firmware---
HWamdryzen_7_pro_5845---
OSamdryzen_7_pro_5845_firmware---
HWamdryzen_7_pro_7730u---
OSamdryzen_7_pro_7730u_firmware---
HWamdryzen_7_pro_7745---
OSamdryzen_7_pro_7745_firmware---
HWamdryzen_7_pro_7840hs---
OSamdryzen_7_pro_7840hs_firmware---
HWamdryzen_9_5900---
OSamdryzen_9_5900_firmware---
HWamdryzen_9_5900hs---
OSamdryzen_9_5900hs_firmware---
HWamdryzen_9_5900hx---
OSamdryzen_9_5900hx_firmware---
HWamdryzen_9_5900x---
OSamdryzen_9_5900x_firmware---
HWamdryzen_9_5950x---
OSamdryzen_9_5950x_firmware---
HWamdryzen_9_5980hs---
OSamdryzen_9_5980hs_firmware---
HWamdryzen_9_5980hx---
OSamdryzen_9_5980hx_firmware---
HWamdryzen_9_6900hs---
OSamdryzen_9_6900hs_firmware---
HWamdryzen_9_6900hx---
OSamdryzen_9_6900hx_firmware---
HWamdryzen_9_6980hs---
OSamdryzen_9_6980hs_firmware---
HWamdryzen_9_6980hx---
OSamdryzen_9_6980hx_firmware---
HWamdryzen_9_7845hx---
OSamdryzen_9_7845hx_firmware---
HWamdryzen_9_7900---
OSamdryzen_9_7900_firmware---
HWamdryzen_9_7900x---
HWamdryzen_9_7900x3d---
OSamdryzen_9_7900x3d_firmware---
OSamdryzen_9_7900x_firmware---
HWamdryzen_9_7940h---
OSamdryzen_9_7940h_firmware---
HWamdryzen_9_7945hx---
HWamdryzen_9_7945hx3d---
OSamdryzen_9_7945hx3d_firmware---
OSamdryzen_9_7945hx_firmware---
HWamdryzen_9_7950x---
HWamdryzen_9_7950x3d---
OSamdryzen_9_7950x3d_firmware---
OSamdryzen_9_7950x_firmware---
HWamdryzen_9_pro_5945---
OSamdryzen_9_pro_5945_firmware---
HWamdryzen_9_pro_7640hs---
OSamdryzen_9_pro_7640hs_firmware---
HWamdryzen_9_pro_7945---
OSamdryzen_9_pro_7945_firmware---
HWamdryzen_threadripper_pro_5945wx---
OSamdryzen_threadripper_pro_5945wx_firmware---
HWamdryzen_threadripper_pro_5955wx---
OSamdryzen_threadripper_pro_5955wx_firmware---
HWamdryzen_threadripper_pro_5965wx---
OSamdryzen_threadripper_pro_5965wx_firmware---
HWamdryzen_threadripper_pro_5975wx---
OSamdryzen_threadripper_pro_5975wx_firmware---
HWamdryzen_threadripper_pro_5995wx---
OSamdryzen_threadripper_pro_5995wx_firmware---
OSdebiandebian_linux10.0--
OSdebiandebian_linux11.0--
OSdebiandebian_linux12.0--
OSfedoraprojectfedora37--
OSfedoraprojectfedora38--
OSmicrosoftwindows_10_1507---
OSmicrosoftwindows_10_1607---
OSmicrosoftwindows_10_1809---
OSmicrosoftwindows_10_21h2---
OSmicrosoftwindows_10_22h2---
OSmicrosoftwindows_11_21h2---
OSmicrosoftwindows_11_22h2---
OSmicrosoftwindows_server_2008---
OSmicrosoftwindows_server_2008r2-x64
OSmicrosoftwindows_server_2012---
OSmicrosoftwindows_server_2012r2--
OSmicrosoftwindows_server_2016---
OSmicrosoftwindows_server_2019---
OSmicrosoftwindows_server_2022---

Explore more

Back to dashboardamd CVEsdebian CVEsfedoraproject CVEsdebian_linux vulnerabilities