🛡️ CVE-2023-20521 — amd-3015ce-firmware

How this vulnerability can be exploited

This issue can be reached with physical access to the device, attack complexity is high, an attacker needs administrative privileges on the target. No user interaction is required. The scope is changed, meaning a successful attack can affect components beyond the vulnerable one. Rated impact: confidentiality low, integrity none, availability low.

CVSS metrics in full

The score comes from this vector: CVSS:3.1/AV:P/AC:H/PR:H/UI:N/S:C/C:L/I:N/A:L

• Attack vector: Physical — the attacker has to touch the device.
• Attack complexity: High — the attacker first has to win a race, learn a secret or otherwise prepare the target.
• Privileges required: High — administrative rights are needed first.
• User interaction: None — nobody has to be tricked into anything.
• Scope: Changed — a successful attack reaches components beyond the vulnerable one.
• Confidentiality impact: Low — limited, and the attacker does not choose what is affected.
• Integrity impact: None.
• Availability impact: Low — limited, and the attacker does not choose what is affected.

Weakness class

CVE-2023-20521 is classified as CWE-367: Time-of-check Time-of-use Race Condition. The state checked and the state acted upon can differ, because it may change between the two steps.

Affected software

CVE-2023-20521 is recorded against 93 packages.

• amd-3015ce-firmware (fixed in pollockpi-ft5_1.0.0.4)
• amd-3015e-firmware (fixed in pollockpi-ft5_1.0.0.4)
• athlon-gold-3150g-firmware
• athlon-gold-pro-3150g-firmware
• athlon-gold-pro-3150ge-firmware
• athlon-pro-300ge-firmware
• epyc-7001-firmware (fixed in naplespi_1.0.0.h)
• epyc-7203-firmware (fixed in milanpi_1.0.0.7)
• epyc-7203p-firmware (fixed in milanpi_1.0.0.7)
• epyc-7232p-firmware (fixed in romepi_1.0.0.d)
• epyc-7251-firmware (fixed in naplespi_1.0.0.h)
• epyc-7252-firmware (fixed in romepi_1.0.0.d)
• epyc-7261-firmware (fixed in naplespi_1.0.0.h)
• epyc-7262-firmware (fixed in romepi_1.0.0.d)
• epyc-7272-firmware (fixed in romepi_1.0.0.d)
• epyc-7281-firmware (fixed in naplespi_1.0.0.h)
• epyc-7282-firmware (fixed in romepi_1.0.0.d)
• epyc-72f3-firmware (fixed in milanpi_1.0.0.7)
• epyc-7301-firmware (fixed in naplespi_1.0.0.h)
• epyc-7302-firmware (fixed in romepi_1.0.0.d)
• epyc-7302p-firmware (fixed in romepi_1.0.0.d)
• epyc-7303-firmware (fixed in milanpi_1.0.0.7)
• epyc-7303p-firmware (fixed in milanpi_1.0.0.7)
• epyc-7313-firmware (fixed in milanpi_1.0.0.7)

Timeline and source

Published on 14 November 2023 and last revised on 17 June 2026. No public exploit is currently recorded for this entry. Record sourced from NVD.

References

www.amd.com
www.amd.com
www.amd.com
www.amd.com
www.amd.com
www.amd.com

Same weakness in other software

These advisories are the same class of weakness (CWE-367: Time-of-check Time-of-use Race Condition) in other software:

• CVE-2022-23563 (8.0 High, published 9 Jul 2026)
• CVE-2022-23826 (published 15 May 2026)
• CVE-2022-26522 (7.8 High, published 8 May 2026)
• CVE-2022-27540 (7.8 High, published 28 Jun 2024)
• CVE-2022-23181 (8.0 High, published 6 Mar 2024)
• CVE-2022-23084 (7.5 High, published 15 Feb 2024)
• CVE-2022-24351 (4.7 Medium, published 16 Dec 2023)
• CVE-2022-31636 (7.8 High, published 13 Jun 2023)

Details

Affected Packages

References