Lucene search
K

CVE-2021-26388

🗓️ 11 May 2022 16:29:06Reported by AMDType 
cve
 cve
🔗 web.nvd.nist.gov📰️ 1 Media mentions👁 100 Views

Improper BIOS directory validation, potential denial of servic

Related
Detection
Affected
Refs
Social
ReporterTitlePublishedViews
Family
Amd
AMD Client Vulnerabilities – May 2022
10 May 202200:00
amd
Amd
AMD Server Vulnerabilities - May 2022
10 May 202200:00
amd
CNNVD
AMD BIOS 缓冲区错误漏洞
11 May 202200:00
cnnvd
CNVD
AMD BIOS Denial of Service Vulnerability
13 May 202200:00
cnvd
Cvelist
CVE-2021-26388
11 May 202216:29
cvelist
EUVD
EUVD-2021-13194
7 Oct 202500:30
euvd
Hewlett-Packard
AMD Client UEFI Firmware May 2022 Security Updates
10 May 202200:00
hp
NCSC
Vulnerabilities fixed in Dell PowerEdge
12 May 202200:00
ncsc
NVD
CVE-2021-26388
11 May 202217:15
nvd
OpenVAS
openSUSE: Security Advisory for kernel-firmware (SUSE-SU-2022:1840-1)
26 May 202200:00
openvas
Rows per page
NVD
Node
amdepyc_7232p_firmwareRange<romepi-sp3_1.0.0.d
AND
Node
amdepyc_7302p_firmwareRange<romepi-sp3_1.0.0.d
AND
Node
amdepyc_7402p_firmwareRange<romepi-sp3_1.0.0.d
AND
Node
amdepyc_7502p_firmwareRange<romepi-sp3_1.0.0.d
AND
Node
amdepyc_7702p_firmwareRange<romepi-sp3_1.0.0.d
AND
Node
amdepyc_7252_firmwareRange<romepi-sp3_1.0.0.d
AND
Node
amdepyc_7262_firmwareRange<romepi-sp3_1.0.0.d
AND
Node
amdepyc_7272_firmwareRange<romepi-sp3_1.0.0.d
AND
Node
amdepyc_7282_firmwareRange<romepi-sp3_1.0.0.d
AND
Node
amdepyc_7302_firmwareRange<romepi-sp3_1.0.0.d
AND
Node
amdepyc_7352_firmwareRange<romepi-sp3_1.0.0.d
AND
Node
amdepyc_7402_firmwareRange<romepi-sp3_1.0.0.d
AND
Node
amdepyc_7452_firmwareRange<romepi-sp3_1.0.0.d
AND
Node
amdepyc_7502_firmwareRange<romepi-sp3_1.0.0.d
AND
Node
amdepyc_7532_firmwareRange<romepi-sp3_1.0.0.d
AND
Node
amdepyc_7542_firmwareRange<romepi-sp3_1.0.0.d
AND
Node
amdepyc_7552_firmwareRange<romepi-sp3_1.0.0.d
AND
Node
amdepyc_7642_firmwareRange<romepi-sp3_1.0.0.d
AND
Node
amdepyc_7662_firmwareRange<romepi-sp3_1.0.0.d
AND
Node
amdepyc_7702_firmwareRange<romepi-sp3_1.0.0.d
AND
Node
amdepyc_7742_firmwareRange<romepi-sp3_1.0.0.d
AND
Node
amdepyc_7f32_firmwareRange<romepi-sp3_1.0.0.d
AND
Node
amdepyc_7f52_firmwareRange<romepi-sp3_1.0.0.d
AND
Node
amdepyc_7f72_firmwareRange<romepi-sp3_1.0.0.d
AND
Node
amdepyc_7f32_firmwareRange<romepi-sp3_1.0.0.d
AND
Node
amdepyc_7f52_firmwareRange<romepi-sp3_1.0.0.d
AND
Node
amdepyc_7f72_firmwareRange<romepi-sp3_1.0.0.d
AND
Node
amdepyc_7313p_firmwareRange<milanpi-sp3_1.0.0.7
AND
Node
amdepyc_7443p_firmwareRange<milanpi-sp3_1.0.0.7
AND
Node
amdepyc_7543p_firmwareRange<milanpi-sp3_1.0.0.7
AND
Node
amdepyc_7713p_firmwareRange<milanpi-sp3_1.0.0.7
AND
Node
amdepyc_7773x_firmwareRange<milanpi-sp3_1.0.0.7
AND
Node
amdepyc_7763_firmwareRange<milanpi-sp3_1.0.0.7
AND
Node
amdepyc_7713_firmwareRange<milanpi-sp3_1.0.0.7
AND
Node
amdepyc_7663_firmwareRange<milanpi-sp3_1.0.0.7
AND
Node
amdepyc_7643_firmwareRange<milanpi-sp3_1.0.0.7
AND
Node
amdepyc_7573x_firmwareRange<milanpi-sp3_1.0.0.7
AND
Node
amdepyc_75f3_firmwareRange<milanpi-sp3_1.0.0.7
AND
Node
amdepyc_7513_firmwareRange<milanpi-sp3_1.0.0.7
AND
Node
amdepyc_7473x_firmwareRange<milanpi-sp3_1.0.0.7
AND
Node
amdepyc_7453_firmwareRange<milanpi-sp3_1.0.0.7
AND
Node
amdepyc_74f3_firmwareRange<milanpi-sp3_1.0.0.7
AND
Node
amdepyc_7413_firmwareRange<milanpi-sp3_1.0.0.7
AND
Node
amdepyc_73f3_firmwareRange<milanpi-sp3_1.0.0.7
AND
Node
amdepyc_7373x_firmwareRange<milanpi-sp3_1.0.0.7
AND
Node
amdepyc_7343_firmwareRange<milanpi-sp3_1.0.0.7
AND
Node
amdepyc_72f3_firmwareRange<milanpi-sp3_1.0.0.7
AND
Node
amdryzen_7_2700x_firmwareRange<comboam4_v2_pi_1.2.0.6c
AND
Node
amdryzen_7_2700x_firmwareRange<comboam4pi_1.0.0.8
AND
Node
amdryzen_7_2700_firmwareRange<comboam4pi_1.0.0.8
AND
Node
amdryzen_7_2700_firmwareRange<comboam4_v2_pi_1.2.0.6c
AND
Node
amdryzen_5_2600x_firmwareRange<comboam4_v2_pi_1.2.0.6c
AND
Node
amdryzen_5_2600x_firmwareRange<comboam4pi_1.0.0.8
AND
Node
amdryzen_5_2700_firmwareRange<comboam4pi_1.0.0.8
AND
Node
amdryzen_5_2700_firmwareRange<comboam4_v2_pi_1.2.0.6c
AND
Node
amdryzen_3_3100_firmwareRange<comboam4pi_1.0.0.8
AND
Node
amdryzen_3_3100_firmwareRange<comboam4_v2_pi_1.2.0.6c
AND
Node
amdryzen_3_3300x_firmwareRange<comboam4pi_1.0.0.8
AND
Node
amdryzen_3_3300x_firmwareRange<comboam4_v2_pi_1.2.0.6c
AND
Node
amdryzen_9_5950x_firmwareRange<comboam4_v2_pi_1.2.0.6c
AND
Node
amdryzen_7_5800x3d_firmwareRange<comboam4_v2_pi_1.2.0.6c
AND
Node
amdryzen_9_5900x_firmwareRange<comboam4_v2_pi_1.2.0.6c
AND
Node
amdryzen_7_5800x_firmwareRange<comboam4_v2_pi_1.2.0.6c
AND
Node
amdryzen_5_5600x_firmwareRange<comboam4_v2_pi_1.2.0.6c
AND
Node
amdryzen_7_5700x_firmwareRange<comboam4_v2_pi_1.2.0.6c
AND
Node
amdryzen_5_5600_firmwareRange<comboam4_v2_pi_1.2.0.6c
AND
Node
amdryzen_5_5500_firmwareRange<comboam4_v2_pi_1.2.0.6c
AND
Node
amdryzen_7_5700g_firmwareRange<comboam4_v2_pi_1.2.0.6c
AND
Node
amdryzen_5_5600g_firmwareRange<comboam4_v2_pi_1.2.0.6c
AND
Node
Node
Node
Node
Node
Node
Node
Node
Node
Node
Node
amdryzen_3_2200u_firmwareRange<raven-fp5-am4_1.1.0.e
AND
Node
amdryzen_3_2300u_firmwareRange<raven-fp5-am4_1.1.0.e
AND
Node
amdryzen_5_2500u_firmwareRange<raven-fp5-am4_1.1.0.e
AND
Node
amdryzen_5_2600h_firmwareRange<raven-fp5-am4_1.1.0.e
AND
Node
amdryzen_7_2700u_firmwareRange<raven-fp5-am4_1.1.0.e
AND
Node
amdryzen_7_2800h_firmwareRange<raven-fp5-am4_1.1.0.e
AND
Node
amdryzen_3_2200u_firmwareRange<pinnaclepi-am4_1.0.0.c_(rv1)
AND
Node
amdryzen_3_2300u_firmwareRange<pinnaclepi-am4_1.0.0.c_(rv1)
AND
Node
amdryzen_5_2500u_firmwareRange<pinnaclepi-am4_1.0.0.c_(rv1)
AND
Node
amdryzen_5_2600h_firmwareRange<pinnaclepi-am4_1.0.0.c_(rv1)
AND
Node
amdryzen_7_2700u_firmwareRange<pinnaclepi-am4_1.0.0.c_(rv1)
AND
Node
amdryzen_7_2800h_firmwareRange<comboam4pi_1.0.0.8
AND
Node
amdryzen_3_2200u_firmwareRange<comboam4pi_1.0.0.8
AND
Node
amdryzen_3_2300u_firmwareRange<comboam4pi_1.0.0.8
AND
Node
amdryzen_5_2500u_firmwareRange<comboam4pi_1.0.0.8
AND
Node
amdryzen_5_2600h_firmwareRange<comboam4pi_1.0.0.8
AND
Node
amdryzen_7_2700u_firmwareRange<comboam4pi_1.0.0.8
AND
Node
amdryzen_7_2800h_firmwareRange<comboam4v2_pi_1.2.0.6c
AND
Node
amdryzen_3_2200u_firmwareRange<comboam4v2_pi_1.2.0.6c
AND
Node
amdryzen_3_2300u_firmwareRange<comboam4v2_pi_1.2.0.6c
AND
Node
amdryzen_5_2500u_firmwareRange<comboam4v2_pi_1.2.0.6c
AND
Node
amdryzen_5_2600h_firmwareRange<comboam4v2_pi_1.2.0.6c
AND
Node
amdryzen_7_2700u_firmwareRange<comboam4v2_pi_1.2.0.6c
AND
Node
amdryzen_7_2800h_firmwareRange<comboam4v2_pi_1.2.0.6c
AND
Node
amdryzen_3_2200u_firmwareRange<picassopi-fp5_1.0.0.d
AND
Node
amdryzen_3_2300u_firmwareRange<picassopi-fp5_1.0.0.d
AND
Node
amdryzen_5_2500u_firmwareRange<picassopi-fp5_1.0.0.d
AND
Node
amdryzen_5_2600h_firmwareRange<picassopi-fp5_1.0.0.d
AND
Node
amdryzen_7_2700u_firmwareRange<picassopi-fp5_1.0.0.d
AND
Node
amdryzen_7_2800h_firmwareRange<picassopi-fp5_1.0.0.d
AND
Node
amdryzen_3_3200u_firmwareRange<comboam4pi_1.0.0.8
AND
Node
amdryzen_3_3250u_firmwareRange<comboam4pi_1.0.0.8
AND
Node
amdryzen_3_3200u_firmwareRange<comboam4v2_pi_1.2.0.6c
AND
Node
amdryzen_3_3250u_firmwareRange<comboam4v2_pi_1.2.0.6c
AND
Node
amdryzen_3_3200u_firmwareRange<renoirpi-fp6_1.0.0.7
AND
Node
amdryzen_3_3250u_firmwareRange<renoirpi-fp6_1.0.0.7
AND
Node
amdryzen_7_2700x_firmwareRange<raven-fp5-am4_1.1.0.e
AND
Node
amdryzen_7_2700x_firmwareRange<raven-fp5-am4_1.1.0.e
AND
Node
amdryzen_7_2700_firmwareRange<raven-fp5-am4_1.1.0.e
AND
Node
amdryzen_7_2700_firmwareRange<raven-fp5-am4_1.1.0.e
AND
Node
amdryzen_3_5300u_firmwareRange<cezannepi-fp6_1.0.0._9a
AND
Node
amdryzen_5_5500u_firmwareRange<cezannepi-fp6_1.0.0._9a
AND
Node
amdryzen_7_5700u_firmwareRange<cezannepi-fp6_1.0.0._9a
AND
Node
amdryzen_3_5125c_firmwareRange<cezannepi-fp6_1.0.0.9
AND
Node
amdryzen_3_5400u_firmwareRange<cezannepi-fp6_1.0.0.9
AND
Node
amdryzen_3_5425u_firmwareRange<cezannepi-fp6_1.0.0.9
AND
Node
amdryzen_5_5560u_firmwareRange<cezannepi-fp6_1.0.0.9
AND
Node
amdryzen_5_5600u_firmwareRange<cezannepi-fp6_1.0.0.9
AND
Node
amdryzen_5_5625u_firmwareRange<cezannepi-fp6_1.0.0.9
AND
Node
amdryzen_5_5600h_firmwareRange<cezannepi-fp6_1.0.0.9
AND
Node
amdryzen_5_5600hs_firmwareRange<cezannepi-fp6_1.0.0.9
AND
Node
amdryzen_7_5800u_firmwareRange<cezannepi-fp6_1.0.0.9
AND
Node
amdryzen_7_5825u_firmwareRange<cezannepi-fp6_1.0.0.9
AND
Node
amdryzen_7_5800h_firmwareRange<cezannepi-fp6_1.0.0.9
AND
Node
amdryzen_7_5800hs_firmwareRange<cezannepi-fp6_1.0.0.9
AND
Node
amdryzen_9_5900hs_firmwareRange<cezannepi-fp6_1.0.0.9
AND
Node
amdryzen_9_5900hx_firmwareRange<cezannepi-fp6_1.0.0.9
AND
Node
amdryzen_9_5980hs_firmwareRange<cezannepi-fp6_1.0.0.9
AND
Node
amdryzen_9_5980hx_firmwareRange<cezannepi-fp6_1.0.0.9
AND
[
  {
    "product": "EPYC™ Processors",
    "vendor": "AMD",
    "versions": [
      {
        "status": "affected",
        "version": "various"
      }
    ]
  },
  {
    "product": "Ryzen™ Series",
    "vendor": "AMD",
    "versions": [
      {
        "status": "affected",
        "version": "various"
      }
    ]
  },
  {
    "product": "Athlon™ Series",
    "vendor": "AMD",
    "versions": [
      {
        "status": "affected",
        "version": "various"
      }
    ]
  }
]

Data

Build on a solid foundation with Vulners data

We provide the essential building blocks for cybersecurity solutions with comprehensive, structured, and constantly updated vulnerability and exploits data

Api

Power your application with Vulners API

The Vulners REST API offers reliable, high-performance access to vulnerability intelligence, with 99.9% SLA uptime and CDN-backed data delivery for seamless global access

App

Assess and manage vulnerabilities with Vulners tools

Built on top of Vulners' database and SDK, end-user solutions give security professionals and developers lightweight and powerful tools for vulnerability remediation

21 Nov 2024 05:56Current
5.8Medium risk
Vulners AI Score5.8
CVSS 24.9
CVSS 3.15.5
EPSS0.0004
100