CVE-2022-23815 is a high severity out-of-bounds write in AMD's APCB firmware, scored 7.5. It could corrupt an APCB entry and potentially lead to code execution. AMD lists mitigations in Platform Initialization firmware, delivered as BIOS updates. Check bulletin AMD-SB-4004 for your processor family.
What's affected
AMD describes the issue as improper bounds checking in APCB firmware that may allow an out-of-bounds write, corrupting the APCB entry, with possible arbitrary code execution.
The NVD record lists a long set of AMD processors and their firmware, including Athlon Silver 3050U and Athlon Gold 3150U. The vendor bulletin, AMD-SB-4004 titled Client Vulnerabilities, August 2024, covers several issues in the AMD Secure Processor and other platform components, and says mitigations are provided in Platform Initialization (PI) firmware packages.
The bulletin has a per product mitigation table. I could not map each column to an exact processor from the text I retrieved. Some rows read not affected or no fix planned for particular families, so do not assume your system is covered or exposed without reading the row for your model.
The CVSS vector is local attack, high complexity and high privileges, with changed scope. AMD and NVD both give 7.5. No exploitation in the wild is reported in the record, and kev is false.
Weakness class per the record: CWE-787.
How to check if you're exposed
This is firmware, so the check is about the BIOS or UEFI version on each machine, not a package.
On Linux you can read the firmware version and date:
sudo dmidecode -s bios-version
sudo dmidecode -s bios-release-date
On Windows, systeminfo shows the BIOS version in its output. Then identify the exact processor model:
lscpu | grep 'Model name'
Match the model against the table in the AMD bulletin to see which PI firmware version carries the mitigation. Then compare that with the BIOS release notes from your system maker, since the maker decides when a PI update reaches a given laptop or board.
What to do now
- Build a list of machines with AMD client processors, with model and BIOS version.
- Read the AMD-SB-4004 table for each processor family to learn whether it is affected and which PI version mitigates it.
- Check your device maker's support page for a BIOS release that includes that PI version, and schedule the update.
- For systems marked as no fix planned, record the risk and limit who has local administrative access.
Why it matters
An out-of-bounds write is the weakness class (CWE-787). Here it sits in early boot firmware, below the operating system. Code at that level runs before security tools load, and a successful attack can survive a reinstall of the operating system.
The attack conditions in the score are demanding: local access, high privileges and high complexity. That keeps the realistic risk lower for most users than the 7.5 suggests. It matters more for shared systems, kiosks and devices that a person may leave unattended.
Firmware fixes depend on device makers, so the practical lag is the main risk. Keeping an inventory of BIOS versions is the only way to know where you stand.
Quick check
Can I fix this from the operating system?
No. The mitigation is in Platform Initialization firmware, which reaches machines as a BIOS or UEFI update from the device maker.
Sources
Last reviewed: 19 October 2026.