VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291900 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-37853 | microsoft_vex | drm/amdkfd: debugfs hang_hws skip GPU with MES | fixed: 2 known affected: 7 | 2026-08-11T01:43:05+00:00 | Vulnerability · Source |
| CVE-2025-37852 | microsoft_vex | drm/amdgpu: handle amdgpu_cgs_create_device() errors in amd_powerplay_create() | fixed: 2 known affected: 7 | 2026-08-11T01:42:55+00:00 | Vulnerability · Source |
| CVE-2025-37849 | microsoft_vex | KVM: arm64: Tear down vGIC on failed vCPU creation | fixed: 2 known affected: 7 | 2026-08-11T01:42:46+00:00 | Vulnerability · Source |
| CVE-2025-37842 | microsoft_vex | spi: fsl-qspi: use devm function instead of driver remove | known affected: 5 known not affected: 1 | 2026-08-11T01:42:37+00:00 | Vulnerability · Source |
| CVE-2025-37980 | microsoft_vex | block: fix resource leak in blk_register_queue() error path | fixed: 2 known affected: 6 | 2026-08-11T01:42:27+00:00 | Vulnerability · Source |
| CVE-2025-37877 | microsoft_vex | iommu: Clear iommu-dma ops on cleanup | known affected: 21 under investigation: 3 | 2026-08-11T01:42:20+00:00 | Vulnerability · Source |
| CVE-2025-37957 | microsoft_vex | KVM: SVM: Forcibly leave SMM mode on SHUTDOWN interception | fixed: 2 known affected: 6 | 2026-08-11T01:42:18+00:00 | Vulnerability · Source |
| CVE-2025-37884 | microsoft_vex | bpf: Fix deadlock between rcu_tasks_trace and event_mutex. | fixed: 2 known affected: 7 | 2026-08-11T01:42:07+00:00 | Vulnerability · Source |
| CVE-2025-37879 | microsoft_vex | 9p/net: fix improper handling of bogus negative read/write replies | fixed: 2 known affected: 7 | 2026-08-11T01:41:57+00:00 | Vulnerability · Source |
| CVE-2025-37878 | microsoft_vex | perf/core: Fix WARN_ON(!ctx) in __free_event() for partial init | fixed: 2 known affected: 7 | 2026-08-11T01:41:47+00:00 | Vulnerability · Source |
| CVE-2025-37920 | microsoft_vex | xsk: Fix race condition in AF_XDP generic RX path | fixed: 1 known affected: 13 | 2026-08-11T01:41:19+00:00 | Vulnerability · Source |
| CVE-2025-37861 | microsoft_vex | scsi: mpi3mr: Synchronous access b/w reset and tm thread for reply queue | known affected: 24 | 2026-08-11T01:41:11+00:00 | Vulnerability · Source |
| CVE-2026-43091 | redhat_vex | kernel: xfrm: Wait for RCU readers during policy netns exit | known affected: 246 known not affected: 28 | 2026-08-11T01:13:54+00:00 | Vulnerability · Source |
| CVE-2026-42792 | redhat_vex | erlang-otp: epmd: Erlang OTP epmd: Remote Denial of Service via connection exhaustion | fixed: 3 | 2026-08-11T01:12:54+00:00 | Vulnerability · Source |
| CVE-2026-55995 | microsoft_vex | Double-free in the iSNS attribute decoder in open-iscsi | fixed: 2 known affected: 2 | 2026-08-11T01:04:58+00:00 | Vulnerability · Source |
| CVE-2026-6879 | microsoft_vex | Quadratic Behavior in xml.etree.ElementPath Index Predicates | fixed: 2 known affected: 2 known not affected: 1 | 2026-08-11T01:03:36+00:00 | Vulnerability · Source |
| CVE-2026-64539 | microsoft_vex | Bluetooth: eir: Fix stack OOB write when prepending the Flags AD | known affected: 2 | 2026-08-11T01:03:23+00:00 | Vulnerability · Source |
| CVE-2024-14040 | microsoft_vex | net: nexthop: Increase weight to u16 | known affected: 3 | 2026-08-11T01:03:09+00:00 | Vulnerability · Source |
| CVE-2026-64525 | microsoft_vex | xfrm: move policy_bydst RCU sync from per-netns .exit to .pre_exit | known affected: 3 | 2026-08-11T01:02:55+00:00 | Vulnerability · Source |
| CVE-2026-64388 | microsoft_vex | smb/client: fix chown/chgrp with SMB3 POSIX Extensions | known affected: 3 | 2026-08-11T01:02:42+00:00 | Vulnerability · Source |
| CVE-2026-64523 | microsoft_vex | net/handshake: Take a long-lived file reference at submit | known affected: 3 | 2026-08-11T01:02:30+00:00 | Vulnerability · Source |
| CVE-2026-64377 | microsoft_vex | cpufreq: qcom-cpufreq-hw: Fix possible double free | known affected: 3 | 2026-08-11T01:02:17+00:00 | Vulnerability · Source |
| CVE-2026-64513 | microsoft_vex | KVM: x86: Unconditionally recompute CR8 intercept on PPR update | known affected: 3 | 2026-08-11T01:02:06+00:00 | Vulnerability · Source |
| CVE-2026-15416 | redhat_vex | argo-cd: Argo CD unauthenticated remote code execution in repo-server via GenerateManifest gRPC endpoint | fixed: 8 known affected: 5 known not affected: 42 | 2026-08-11T00:38:34+00:00 | Vulnerability · Source |
| CVE-2024-8391 | redhat_vex | io.vertx:vertx-grpc-client: io.vertx:vertx-grpc-server: Vertx gRPC server does not limit the maximum message size | fixed: 31 known affected: 5 known not affected: 965 | 2026-08-11T00:24:14+00:00 | Vulnerability · Source |
| CVE-2007-6015 | suse_vex | SUSE CVE CVE-2007-6015 | recommended: 297 | 2026-08-11T00:20:00+00:00 | Vulnerability · Source |
| CVE-2009-3640 | suse_vex | SUSE CVE CVE-2009-3640 | known not affected: 372 recommended: 6 | 2026-08-11T00:19:56+00:00 | Vulnerability · Source |
| CVE-2010-1641 | suse_vex | SUSE CVE CVE-2010-1641 | known not affected: 496 recommended: 408 | 2026-08-11T00:19:53+00:00 | Vulnerability · Source |
| CVE-2011-2367 | suse_vex | SUSE CVE CVE-2011-2367 | known affected: 21 known not affected: 137 recommended: 107 | 2026-08-11T00:19:48+00:00 | Vulnerability · Source |
| CVE-2011-4862 | suse_vex | SUSE CVE CVE-2011-4862 | known affected: 2 known not affected: 62 recommended: 77 | 2026-08-11T00:19:45+00:00 | Vulnerability · Source |
| CVE-2013-4296 | suse_vex | SUSE CVE CVE-2013-4296 | recommended: 839 | 2026-08-11T00:19:37+00:00 | Vulnerability · Source |
| CVE-2014-8102 | suse_vex | SUSE CVE CVE-2014-8102 | known affected: 1 recommended: 97 | 2026-08-11T00:19:29+00:00 | Vulnerability · Source |
| CVE-2015-8716 | suse_vex | SUSE CVE CVE-2015-8716 | known affected: 86 recommended: 107 | 2026-08-11T00:19:13+00:00 | Vulnerability · Source |
| CVE-2015-8806 | suse_vex | SUSE CVE CVE-2015-8806 | known affected: 1 recommended: 112 | 2026-08-11T00:19:11+00:00 | Vulnerability · Source |
| CVE-2017-12673 | suse_vex | SUSE CVE CVE-2017-12673 | known affected: 94 recommended: 186 | 2026-08-11T00:18:43+00:00 | Vulnerability · Source |
| CVE-2018-5094 | suse_vex | SUSE CVE CVE-2018-5094 | known affected: 1 known not affected: 42 recommended: 12 | 2026-08-11T00:18:34+00:00 | Vulnerability · Source |
| CVE-2022-0185 | suse_vex | SUSE CVE CVE-2022-0185 | known affected: 335 known not affected: 303 recommended: 1173 | 2026-08-11T00:17:18+00:00 | Vulnerability · Source |
| CVE-2022-0492 | suse_vex | SUSE CVE CVE-2022-0492 | known affected: 349 known not affected: 57 recommended: 1722 | 2026-08-11T00:17:15+00:00 | Vulnerability · Source |
| CVE-2022-48985 | suse_vex | SUSE CVE CVE-2022-48985 | known affected: 385 known not affected: 147 recommended: 518 | 2026-08-11T00:16:37+00:00 | Vulnerability · Source |
| CVE-2023-7192 | suse_vex | SUSE CVE CVE-2023-7192 | known affected: 424 known not affected: 66 recommended: 705 | 2026-08-11T00:15:59+00:00 | Vulnerability · Source |
| CVE-2023-53365 | suse_vex | SUSE CVE CVE-2023-53365 | known affected: 431 known not affected: 20 recommended: 731 | 2026-08-11T00:15:38+00:00 | Vulnerability · Source |
| CVE-2024-21404 | suse_vex | SUSE CVE CVE-2024-21404 | recommended: 65 | 2026-08-11T00:15:18+00:00 | Vulnerability · Source |
| CVE-2024-43495 | suse_vex | SUSE CVE CVE-2024-43495 | known not affected: 161 | 2026-08-11T00:14:59+00:00 | Vulnerability · Source |
| CVE-2025-22868 | suse_vex | SUSE CVE CVE-2025-22868 | known affected: 525 known not affected: 519 recommended: 550 | 2026-08-11T00:14:08+00:00 | Vulnerability · Source |
| CVE-2025-38054 | suse_vex | SUSE CVE CVE-2025-38054 | known affected: 57 known not affected: 344 recommended: 53 | 2026-08-11T00:13:59+00:00 | Vulnerability · Source |
| CVE-2025-38311 | suse_vex | SUSE CVE CVE-2025-38311 | first fixed: 2 known not affected: 450 recommended: 154 | 2026-08-11T00:13:54+00:00 | Vulnerability · Source |
| CVE-2025-38355 | suse_vex | SUSE CVE CVE-2025-38355 | first fixed: 2 known affected: 394 known not affected: 367 recommended: 265 | 2026-08-11T00:13:51+00:00 | Vulnerability · Source |
| CVE-2025-38511 | suse_vex | SUSE CVE CVE-2025-38511 | first fixed: 2 known affected: 394 known not affected: 390 recommended: 289 | 2026-08-11T00:13:47+00:00 | Vulnerability · Source |
| CVE-2025-39894 | suse_vex | SUSE CVE CVE-2025-39894 | first fixed: 2 known not affected: 262 recommended: 172 | 2026-08-11T00:13:40+00:00 | Vulnerability · Source |
| CVE-2026-3039 | suse_vex | SUSE CVE CVE-2026-3039 | known affected: 516 recommended: 275 | 2026-08-11T00:13:05+00:00 | Vulnerability · Source |