ryzen 3 3250u firmware · threatengine.sh

Home/Product/amd ryzen 3 3250u firmware

Product

amd ryzen 3 3250u firmware

30 known vulnerabilities across versions

Vulnerabilities are listed by affected version. Select any CVE for the full briefing and its intelligence graph.

Sort Min CVSS Published since

< picassopi-fp5_1.0.0.e

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

< cezannepi-fp6_1.0.1.0

Improper Access Control in the AMD SPI protection feature may allow a user with Ring0 (kernel mode) privileged access to bypass pr

A GPU kernel can read sensitive data from another GPU kernel (even from another user or app) through an optimized GPU memory regio

< picassopi-fp5_1.0.0.e

TOCTOU in the ASP Bootloader may allow an attacker with physical access to tamper with SPI ROM records after memory content verifi

Improper access control in System Management Mode (SMM) may allow an attacker to write to SPI ROM potentially leading to arbitrary

Improper initialization of variables in the DXE driver may allow a privileged user to leak sensitive information via local access.

Improper initialization of variables in the DXE driver may allow a privileged user to leak sensitive information via local access.

< picassopi-fp5_1.0.0.d

A compromised or malicious ABL or UApp could send a SHA256 system call to the bootloader, which may result in exposure of ASP memo

< picassopi-fp5_1.0.0.d

Certain size values in firmware binary headers could trigger out of bounds reads during signature validation, leading to denial of

< picassopi-fp5_1.0.0.d

Insufficient bounds checking in ASP may allow an attacker to issue a system call from a compromised ABL which may cause arbitrary

Insufficient control flow management in AmdCpmGpioInitSmm may allow a privileged attacker to tamper with the SMM handler potential

Insufficient control flow management in AmdCpmOemSmm may allow a privileged attacker to tamper with the SMM handler potentially le

When SMT is enabled, certain AMD processors may speculatively execute instructions using a target from the sibling thread after an

Failure to validate the integer operand in ASP (AMD Secure Processor) bootloader may allow an attacker to introduce an integer ove

IBPB may not prevent return branch predictions from being specified by pre-IBPB branch targets leading to a potential information

Insufficient memory cleanup in the AMD Secure Processor (ASP) Trusted Execution Environment (TEE) may allow an authenticated attac

Insufficient verification of missing size check in 'LoadModule' may lead to an out-of-bounds write potentially allowing an attacke

Improper parameters handling in the AMD Secure Processor (ASP) kernel may allow a privileged attacker to elevate their privileges

Improper parameters handling in AMD Secure Processor (ASP) drivers may allow a privileged attacker to elevate their privileges pot

Execution unit scheduler contention may lead to a side channel vulnerability found on AMD CPU microarchitectures codenamed “Zen

Aliases in the branch predictor may cause some AMD processors to predict the wrong branch type potentially leading to information

A malformed SMI (System Management Interface) command may allow an attacker to establish a corrupted SMI Trigger Info data structu

< renoirpi-fp6_1.0.0.7

An attacker with root account privileges can load any legitimately signed firmware image into the Audio Co-Processor (ACP,) irresp

Mis-trained branch predictions for return instructions may allow arbitrary speculative code execution under certain microarchitect

A potential vulnerability in some AMD processors using frequency scaling may allow an authenticated attacker to execute a timing a

< comboam4pi_1.0.0.8

Improper validation of the BIOS directory may allow for searches to read beyond the directory table copy in RAM, exposing out of b

< comboam4pi_1.0.0.8

Insufficient bound checks in the System Management Unit (SMU) may result in access to an invalid address space that could result i

< comboam4pi_1.0.0.8

Insufficient checks in System Management Unit (SMU) FeatureConfig may result in reenabling features potentially resulting in denia

< comboam4pi_1.0.0.8

Insufficient General Purpose IO (GPIO) bounds check in System Management Unit (SMU) may result in access/updates from/to invalid a

< comboam4pi_1.0.0.8

Insufficient bound checks in the System Management Unit (SMU) may result in a system voltage malfunction that could result in deni

Vulnerabilities
CISA KEV catalog
CWE weaknesses
CAPEC attack patterns
Package vulnerabilities

Threat intelligence
Threat actors
Tools & malware
ATT&CK techniques
IOCs

Detection & defense
Sigma rules
YARA rules
Atomic Red Team tests
D3FEND countermeasures

Compliance
NIST 800-53
ISO 27001:2022
SOC 2 TSC
PCI-DSS v4.0
CIS Controls v8.1

About
All capabilities
Live statistics
Data sources
Privacy policy
Terms of service

threatengine.sh · Open-source threat intelligence platform · 100+ authoritative sources · Every fact traces to its origin