Skip to content
Fencer Vulns
high 7.5

CVE-2022-23815 json

Improper bounds checking in APCB firmware may allow an attacker to perform an out of bounds write, corrupting the APCB entry, potentially l…

published 2024-08-13 2 y ago modified 2026-06-17 4 mo ago also EUVD-2022-28744

cvss
7.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 5%
public exploits
0
none known

Summary

Improper bounds checking in APCB firmware may allow an attacker to perform an out of bounds write, corrupting the APCB entry, potentially leading to arbitrary code execution.

Patch / fix

  • AMD AMD Athlon™ 3000 Series Mobile Processors with Radeon™ Graphics PicassoPI-FP5 1.0.0.F, PollockPI-FT5 1.0.0.5
  • AMD AMD Ryzen™ 3000 Series Mobile Processor with Radeon™ Graphics PicassoPI-FP5 1.0.0.E
  • AMD AMD RyzenTM Embedded R1000 EmbeddedPI-FP5 1.2.0.A
  • AMD AMD RyzenTM Embedded R2000 EmbeddedR2KPI-FP5 1.0.0.2
  • AMD AMD RyzenTM Embedded V1000 EmbeddedPI-FP5 1.2.0.A
  • amd athlon_3000g 1.0.0.5, 1.0.0.E, 1.0.0.F

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
2 y ago

Exploit prediction

0.16% chance of exploitation in the next 30 days, higher than 5% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 7.5 CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H
NVD 3.1 8.2 CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

Affected products

  • AMD AMD Athlon™ 3000 Series Desktop Processors with Radeon™ Graphics
  • AMD AMD Athlon™ 3000 Series Mobile Processors with Radeon™ Graphics
  • AMD AMD Ryzen™ 3000 Series Mobile Processor with Radeon™ Graphics
  • AMD AMD RyzenTM Embedded R1000
  • AMD AMD RyzenTM Embedded R2000
  • AMD AMD RyzenTM Embedded V1000
  • amd athlon_3000g
  • amd ryzen_embedded_r1000
  • amd ryzen_embedded_r2000
  • amd ryzen_embedded_v1000

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.