Vulnerability feed

CVE and vendor PSIRT advisories from 13 sources, last 30 days. Updated hourly, last run Oct 26 06:05 UTC

Critical in the last 24 hours

1602 in 30 days

Newly known exploited

In the last 24 hours, CISA KEV and vendor reports

Sources checked

Every hour, see the list

New in the last 24 hours

165-72% vs 7-day avg of 599

2 critical, 48 high, 64 medium, 31 low

Expand	Severity	Score	Advisory	Title	Source	Published
	Unknown	n/a	CVE-2026-98997	In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/userq: only accept doorbell BOs as queue doorbell amdgpu_userq_get_doorbell_index() pins any BO... Linux, AMDLinux, Linux kernel, amdgpu	NVD	Oct 23 13:17 UTC
CVE-2026-98997In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/userq: only accept doorbell BOs as queue doorbell amdgpu_userq_get_doorbell_index() pins any BO... Executive summary A flaw in the Linux kernel's AMD GPU user queue code allowed a client to pin an arbitrary buffer object into the doorbell domain, which could erase that buffer's contents, including buffers shared by another client. The advisory does not state a severity rating, and the fix rejects buffers not created in the doorbell domain. Users should apply the kernel stable tree update that carries this patch. Technical summary The weakness is improper validation of a buffer object passed as a doorbell handle in amdgpu_userq_get_doorbell_index(), which pins any BO into the doorbell domain and causes TTM to discard its contents via ttm_bo_move_null(). An importing client on the same device can trigger this against a buffer another client shared with it, so the precondition is local access with a shared GEM object. The fix rejects BOs whose preferred_domains lack AMDGPU_GEM_DOMAIN_DOORBELL and returns -EINVAL. The advisory cites the fixing commit 7f7c88dbf4d543f6703e53bdeed380e886733167 upstream and the fixed-by commit f7497bbc19db4821c62b9d97b31c9086feb2d917 in the stable tree, and it names Fixes tag f09c1e6077ab. No affected or fixed kernel version ranges, CVSS score, workaround, or detection guidance is stated in the advisory. Summaries are generated by AI from the linked advisory text. Confirm versions and fixes at the source. Summarized from git.kernel.org/stable/c/112dbe2b10d6d08…99980dd960dcbfa55ff0 Score No CVSS score published. Affects Linux AMD Linux Linux kernel amdgpu NIST National Vulnerability DatabasePublished Oct 23, 2026 13:17 UTC Read the advisory
	Unknown	n/a	CVE-2026-98933	In the Linux kernel, the following vulnerability has been resolved: usb: hub: use shorter 120ms post resume hold for SS root hubs Holding a USB3 hub PM runtime reference for... Linux, AMDLinux, Linux kernel	NVD	Oct 23 13:17 UTC
CVE-2026-98933In the Linux kernel, the following vulnerability has been resolved: usb: hub: use shorter 120ms post resume hold for SS root hubs Holding a USB3 hub PM runtime reference for... Executive summary This advisory concerns a Linux kernel USB hub change that shortens a post-resume hold time for USB3 root hubs. It describes the change as a mitigation for a crash seen on an AMD platform when Android adb repeatedly wakes the USB subsystem, and it is presented as a fix in the stable kernel tree. The advisory does not state a severity rating, and it recommends the change in the kernel source as shown, with vendors still said to be working on a full solution. Technical summary The flaw is described as a platform issue triggered by holding a USB3 hub runtime power management reference for 200ms during hub resume, which the advisory says causes crashes after repeated adb polling. The fix reduces the hold to 120ms for USB3 root hubs in drivers/usb/core/hub.c while keeping 200ms for external hubs, and it is tied to commit 8f5b7e2bec1c. The advisory does not state the attack vector, required privileges, or exploitation status. No affected or fixed kernel version numbers, CVSS score, workaround details beyond disabling USB runtime PM, or detection guidance are stated. Summaries are generated by AI from the linked advisory text. Confirm versions and fixes at the source. Summarized from git.kernel.org/stable/c/29480b05e6e2265…1ccf2a036fbd5cdd0e42 Score No CVSS score published. Affects Linux AMD Linux Linux kernel NIST National Vulnerability DatabasePublished Oct 23, 2026 13:17 UTC Read the advisory
	Unknown	n/a	CVE-2026-98914	In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: cap ATOM command table nesting depth Cap nesting at 32 levels with execute_depth and return... Linux, AMDLinux, Linux kernel, amdgpu	NVD	Oct 23 12:18 UTC
CVE-2026-98914In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: cap ATOM command table nesting depth Cap nesting at 32 levels with execute_depth and return... Executive summary The advisory describes a fix in the Linux kernel's AMD GPU driver (drm/amdgpu) that limits how deeply ATOM command tables can nest. The advisory does not state how severe the issue is or give a CVSS score. The fix is a code change in the stable kernel tree, and no separate vendor action beyond applying that kernel update is stated. Technical summary The change addresses unbounded recursion in ATOM command table execution in the amdgpu driver, which the patch comment says could overflow the kernel stack. The fix caps nesting at 32 levels using an execute_depth counter in the atom_context structure and returns -ELOOP when the limit is exceeded. The advisory does not state the attack vector, required privileges, or whether the issue is exploitable by an attacker. Affected and fixed kernel version numbers are not stated beyond the commit identifier 27ef1795bc4e47cae838e0a3ced531c549f9b23d. No workarounds or detection guidance are stated. Summaries are generated by AI from the linked advisory text. Confirm versions and fixes at the source. Summarized from git.kernel.org/stable/c/27ef1795bc4e47c…e0a3ced531c549f9b23d Score No CVSS score published. Affects Linux AMD Linux Linux kernel amdgpu NIST National Vulnerability DatabasePublished Oct 23, 2026 12:18 UTC Read the advisory
	Unknown	n/a	CVE-2026-98910	In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: Unwind debug trap enable on copy_to_user failure If kfd_dbg_trap_enable() fails while copying... Linux, AMDLinux, Linux kernel, amdkfd	NVD	Oct 23 12:18 UTC
CVE-2026-98910In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: Unwind debug trap enable on copy_to_user failure If kfd_dbg_trap_enable() fails while copying... Executive summary This advisory covers a Linux kernel fix in the AMD graphics driver component (amdkfd) that corrects how debug trap state is cleaned up when a copy to user space fails. The advisory does not state how severe the issue is, and it does not describe a specific recommended action beyond the fix itself. Systems running affected Linux kernel builds that include the AMD GPU driver should apply the vendor's kernel update once available. Technical summary The flaw is an error-handling and state-unwinding defect in kfd_dbg_trap_enable() in drivers/gpu/drm/amd/amdkfd/kfd_debug.c. When copy_to_user() failed while copying runtime_info to userspace, the function returned -EFAULT without undoing the trap activation, debug_trap_enabled flag, extra process reference, and debug event file, which left inconsistent trap state and a refcount imbalance that could break later DISABLE or ENABLE operations. The fix deactivates the trap, releases the debug event file, decrements the debugged process count, clears debug_trap_enabled, and drops the process reference before returning. The advisory does not state a CVSS score, attack vector or privilege requirements, affected version ranges, fixed version numbers, workarounds, or exploitation status, and it gives no detection guidance. Summaries are generated by AI from the linked advisory text. Confirm versions and fixes at the source. Summarized from git.kernel.org/stable/c/01112e241e37f9a…f418d93ce2e0b87b7ee0 Score No CVSS score published. Affects Linux AMD Linux Linux kernel amdkfd NIST National Vulnerability DatabasePublished Oct 23, 2026 12:18 UTC Read the advisory
	Unknown	n/a	CVE-2026-98894	In the Linux kernel, the following vulnerability has been resolved: drm/amd/ras: reset CPER ring on corrupt entry size When CPER ring overflow handling advances the read... Linux, AMDLinux, Linux kernel, amdgpu	NVD	Oct 23 12:18 UTC
CVE-2026-98894In the Linux kernel, the following vulnerability has been resolved: drm/amd/ras: reset CPER ring on corrupt entry size When CPER ring overflow handling advances the read... Executive summary This advisory concerns a fix in the Linux kernel's AMD graphics driver (drm/amd/ras) that prevents a hang caused by corrupt error-record data. The advisory does not state a severity rating, and it does not state whether the hang can be triggered remotely or by a low-privileged user. Technical summary The flaw is a denial-of-service condition, described as a hang, in the CPER ring recovery loop of the amdgpu driver in the Linux kernel. Corrupt CPER data can produce an entry size that does not advance the read pointer after dword conversion and masking, so the loop keeps testing the same location while holding the ring mutex, which can hang the writer thread. The fix detects a no-progress read pointer update and resets the ring to an empty state, dropping the corrupt contents. The advisory does not state affected or fixed kernel version ranges, a CVSS score, workarounds, exploitation status, or detection guidance. Summaries are generated by AI from the linked advisory text. Confirm versions and fixes at the source. Summarized from git.kernel.org/stable/c/4d695e66d7027a0…2e47ac76293675fbbb4d Score No CVSS score published. Affects Linux AMD Linux Linux kernel amdgpu NIST National Vulnerability DatabasePublished Oct 23, 2026 12:18 UTC Read the advisory
	High	7.7	CVE-2026-43598	Improper input validation in the AMD ROCm Communication Collectives Library (RCCL) could allow a compromised peer rank or network-adjacent attacker to dereference an... AMDAMD Instinct™ MI210, AMD Instinct™ MI250, AMD Instinct™ MI300A, AMD Instinct™ MI300X, AMD Instinct™ MI325X, AMD Instinct™ MI350X, AMD Instinct™ MI355X, AMD Instinct™ MI308X, AMD Instinct™ MI250X	NVD	Oct 6 21:17 UTC
CVE-2026-43598Improper input validation in the AMD ROCm Communication Collectives Library (RCCL) could allow a compromised peer rank or network-adjacent attacker to dereference an... From the advisory Improper input validation in the AMD ROCm Communication Collectives Library (RCCL) could allow a compromised peer rank or network-adjacent attacker to dereference an attacker-controlled pointer, potentially resulting in remote code execution. Impact if exploited ConfidentialityHigh IntegrityHigh AvailabilityHigh How it is exploited Attack vector Network Attack complexity High Attack requirements None Privileges required Low User interaction None CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X Affects AMD AMD Instinct™ MI210 AMD Instinct™ MI250 AMD Instinct™ MI300A AMD Instinct™ MI300X AMD Instinct™ MI325X AMD Instinct™ MI350X AMD Instinct™ MI355X AMD Instinct™ MI308X AMD Instinct™ MI250X NIST National Vulnerability DatabasePublished Oct 6, 2026 21:17 UTC Read the advisory
	Medium	5.4	CVE-2026-0482	In AMD Versal™ Adaptive SoC devices, insufficient boundary checks in USB boot mode—when enabled through board modifications—could allow crafted images to trigger a buffer... AMDAMD Alveo™ Accelerator Cards, AMD Versal™ Prime Series Adaptive SoCs, AMD Versal™ Premium Series Adaptive SoCs, AMD Versal™ AI Edge Series Adaptive SoCs, AMD Versal™ AI Core Series Adaptive SoCs, AMD Versal™ HBM Series Adaptive SoCs, AMD Versal™ RF Series Adaptive SoCs, AMD Versal Premium Series Gen 2 Adaptive SOCs (2VP3402, 2VP3502, 2VP3602)	NVD	Oct 5 22:16 UTC
CVE-2026-0482In AMD Versal™ Adaptive SoC devices, insufficient boundary checks in USB boot mode—when enabled through board modifications—could allow crafted images to trigger a buffer... From the advisory In AMD Versal™ Adaptive SoC devices, insufficient boundary checks in USB boot mode—when enabled through board modifications—could allow crafted images to trigger a buffer overflow and overwrite an active function pointer, which may result in arbitrary code execution during boot process. This condition could lead to potential impacts on confidentiality, integrity, and availability. Impact if exploited ConfidentialityHigh IntegrityHigh AvailabilityHigh How it is exploited Attack vector Physical Attack complexity High Attack requirements None Privileges required None User interaction None CVSS:4.0/AV:P/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X Affects AMD AMD Alveo™ Accelerator Cards AMD Versal™ Prime Series Adaptive SoCs AMD Versal™ Premium Series Adaptive SoCs AMD Versal™ AI Edge Series Adaptive SoCs AMD Versal™ AI Core Series Adaptive SoCs AMD Versal™ HBM Series Adaptive SoCs AMD Versal™ RF Series Adaptive SoCs AMD Versal Premium Series Gen 2 Adaptive SOCs (2VP3402, 2VP3502, 2VP3602) NIST National Vulnerability DatabasePublished Oct 5, 2026 22:16 UTC Read the advisory
	High	7.5	CVE-2026-0461	Insufficient boundary validation in the USB boot mode implementation of AMD Zynq™ UltraScale+ MPSoC and RFSoC devices could allow unbounded Device Firmware Upgrade (DFU)... AMDAMD Zynq™ UltraScale+ MPSoCs, AMD Zynq™ UltraScale+ RFSoCs, AMD Kria SOMs	NVD	Oct 5 22:16 UTC
CVE-2026-0461Insufficient boundary validation in the USB boot mode implementation of AMD Zynq™ UltraScale+ MPSoC and RFSoC devices could allow unbounded Device Firmware Upgrade (DFU)... From the advisory Insufficient boundary validation in the USB boot mode implementation of AMD Zynq™ UltraScale+ MPSoC and RFSoC devices could allow unbounded Device Firmware Upgrade (DFU) download requests to overflow the DDR receive buffer into FSBL memory, potentially resulting in unauthorized code execution during the boot process. This issue could impact the confidentiality, integrity, or availability of affected system. Impact if exploited ConfidentialityHigh IntegrityHigh AvailabilityHigh How it is exploited Attack vector Local Attack complexity Low Attack requirements Present Privileges required None User interaction None CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X Affects AMD AMD Zynq™ UltraScale+ MPSoCs AMD Zynq™ UltraScale+ RFSoCs AMD Kria SOMs NIST National Vulnerability DatabasePublished Oct 5, 2026 22:16 UTC Read the advisory

Example	Finds
	Every word appears somewhere: title, summaries, IDs, vendor, or product
	An exact phrase
	One vendor. product: for a product, vp: for either
	Commas mean any of them, in every field
	Severity: critical, high, medium, low, or unknown
	CVSS score, with >, >=, <, or <=
	A score range
	Known exploited. is:kev works too, and kev:no leaves them out
	One source, by name
	Confidentiality impact: high, low, none, or any (low or high)
	Integrity and availability work the same way
	An advisory or CVE ID, or part of one
	A minus sign leaves out whatever the term matches

Vulnerability feed

Executive summary

Technical summary

Score

Affects

Executive summary

Technical summary

Score

Affects

Executive summary

Technical summary

Score

Affects

Executive summary

Technical summary

Score

Affects

Executive summary

Technical summary

Score

Affects

From the advisory

Impact if exploited

How it is exploited

Affects

From the advisory

Impact if exploited

How it is exploited

Affects

From the advisory

Impact if exploited

How it is exploited

Affects

Search syntax

Welcome to CVEsee.org

What is CVEsee.org?

Disclaimer

You are leaving CVEsee.org

Install CVEsee