VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
290275 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2024-24549 | suse_vex | SUSE CVE CVE-2024-24549 | known affected: 523 known not affected: 3 recommended: 756 | 2026-08-01T23:30:10+00:00 | Vulnerability · Source |
| CVE-2024-26652 | suse_vex | SUSE CVE CVE-2024-26652 | known not affected: 403 recommended: 264 | 2026-08-01T23:30:08+00:00 | Vulnerability · Source |
| CVE-2024-39133 | suse_vex | SUSE CVE CVE-2024-39133 | known not affected: 114 recommended: 14 | 2026-08-01T23:29:56+00:00 | Vulnerability · Source |
| CVE-2024-40956 | suse_vex | SUSE CVE CVE-2024-40956 | known affected: 292 known not affected: 109 recommended: 964 | 2026-08-01T23:29:53+00:00 | Vulnerability · Source |
| CVE-2024-49975 | suse_vex | SUSE CVE CVE-2024-49975 | known affected: 582 known not affected: 42 recommended: 670 | 2026-08-01T23:29:43+00:00 | Vulnerability · Source |
| CVE-2024-58008 | suse_vex | SUSE CVE CVE-2024-58008 | known affected: 57 known not affected: 295 recommended: 53 | 2026-08-01T23:29:29+00:00 | Vulnerability · Source |
| CVE-2025-47273 | suse_vex | SUSE CVE CVE-2025-47273 | known affected: 365 known not affected: 9 recommended: 350 | 2026-08-01T23:28:57+00:00 | Vulnerability · Source |
| CVE-2025-69418 | suse_vex | SUSE CVE CVE-2025-69418 | known affected: 406 known not affected: 250 recommended: 329 | 2026-08-01T23:28:48+00:00 | Vulnerability · Source |
| CVE-2025-2843 | redhat_vex | observability-operator: Observability Operator privilege escalation | fixed: 4 known not affected: 77 | 2026-08-01T19:50:42+00:00 | Vulnerability · Source |
| CVE-2026-23034 | redhat_vex | kernel: drm/amdgpu/userq: Fix fence reference leak on queue teardown v2 | known affected: 198 known not affected: 76 | 2026-08-01T18:08:30+00:00 | Vulnerability · Source |
| CVE-2026-23163 | redhat_vex | kernel: drm/amdgpu: fix NULL pointer dereference in amdgpu_gmc_filter_faults_remove | known affected: 198 known not affected: 76 | 2026-08-01T17:58:26+00:00 | Vulnerability · Source |
| CVE-2026-23213 | redhat_vex | kernel: drm/amd/pm: Disable MMIO access during SMU Mode 1 reset | known affected: 274 | 2026-08-01T17:53:34+00:00 | Vulnerability · Source |
| CVE-2026-23338 | redhat_vex | kernel: drm/amdgpu/userq: Do not allow userspace to trivially triger kernel warnings | known affected: 198 known not affected: 76 | 2026-08-01T17:48:43+00:00 | Vulnerability · Source |
| CVE-2026-31462 | redhat_vex | kernel: drm/amdgpu: prevent immediate PASID reuse case | known affected: 274 | 2026-08-01T17:33:29+00:00 | Vulnerability · Source |
| CVE-2026-31765 | redhat_vex | kernel: drm/amdgpu: Change AMDGPU_VA_RESERVED_TRAP_SIZE to 64KB | known affected: 184 known not affected: 90 | 2026-08-01T17:28:44+00:00 | Vulnerability · Source |
| CVE-2020-26116 | suse_vex | SUSE CVE CVE-2020-26116 | known affected: 338 known not affected: 56 recommended: 1408 | 2026-08-01T17:14:06+00:00 | Vulnerability · Source |
| CVE-2020-26951 | suse_vex | SUSE CVE CVE-2020-26951 | known affected: 59 recommended: 405 | 2026-08-01T17:14:03+00:00 | Vulnerability · Source |
| CVE-2020-26974 | suse_vex | SUSE CVE CVE-2020-26974 | recommended: 463 | 2026-08-01T17:14:02+00:00 | Vulnerability · Source |
| CVE-2020-27749 | suse_vex | SUSE CVE CVE-2020-27749 | known affected: 293 recommended: 869 | 2026-08-01T17:13:59+00:00 | Vulnerability · Source |
| CVE-2020-27815 | suse_vex | SUSE CVE CVE-2020-27815 | known affected: 300 known not affected: 470 recommended: 1369 | 2026-08-01T17:13:57+00:00 | Vulnerability · Source |
| CVE-2020-27820 | suse_vex | SUSE CVE CVE-2020-27820 | known affected: 340 known not affected: 220 recommended: 1285 | 2026-08-01T17:13:56+00:00 | Vulnerability · Source |
| CVE-2020-27845 | suse_vex | SUSE CVE CVE-2020-27845 | known affected: 40 recommended: 318 | 2026-08-01T17:13:54+00:00 | Vulnerability · Source |
| CVE-2020-35524 | suse_vex | SUSE CVE CVE-2020-35524 | known affected: 395 recommended: 289 | 2026-08-01T17:13:50+00:00 | Vulnerability · Source |
| CVE-2020-36558 | suse_vex | SUSE CVE CVE-2020-36558 | known affected: 368 known not affected: 51 recommended: 938 | 2026-08-01T17:13:46+00:00 | Vulnerability · Source |
| CVE-2020-36773 | suse_vex | SUSE CVE CVE-2020-36773 | known not affected: 124 recommended: 68 | 2026-08-01T17:13:45+00:00 | Vulnerability · Source |
| CVE-2021-0961 | suse_vex | SUSE CVE CVE-2021-0961 | known not affected: 365 | 2026-08-01T17:13:43+00:00 | Vulnerability · Source |
| CVE-2021-3236 | suse_vex | SUSE CVE CVE-2021-3236 | known not affected: 258 | 2026-08-01T17:13:40+00:00 | Vulnerability · Source |
| CVE-2021-3556 | suse_vex | SUSE CVE CVE-2021-3556 | known not affected: 1585 | 2026-08-01T17:13:38+00:00 | Vulnerability · Source |
| CVE-2021-3711 | suse_vex | SUSE CVE CVE-2021-3711 | known affected: 311 known not affected: 573 recommended: 393 | 2026-08-01T17:13:35+00:00 | Vulnerability · Source |
| CVE-2021-3974 | suse_vex | SUSE CVE CVE-2021-3974 | known affected: 353 known not affected: 42 recommended: 366 | 2026-08-01T17:13:33+00:00 | Vulnerability · Source |
| CVE-2021-20224 | suse_vex | SUSE CVE CVE-2021-20224 | known affected: 86 known not affected: 120 recommended: 199 | 2026-08-01T17:13:31+00:00 | Vulnerability · Source |
| CVE-2021-23840 | suse_vex | SUSE CVE CVE-2021-23840 | known affected: 298 known not affected: 407 recommended: 1250 | 2026-08-01T17:13:27+00:00 | Vulnerability · Source |
| CVE-2021-25329 | suse_vex | SUSE CVE CVE-2021-25329 | known affected: 394 recommended: 670 | 2026-08-01T17:13:26+00:00 | Vulnerability · Source |
| CVE-2021-26934 | suse_vex | SUSE CVE CVE-2021-26934 | known not affected: 345 | 2026-08-01T17:13:24+00:00 | Vulnerability · Source |
| CVE-2021-26937 | suse_vex | SUSE CVE CVE-2021-26937 | known affected: 394 known not affected: 4 recommended: 88 | 2026-08-01T17:13:23+00:00 | Vulnerability · Source |
| CVE-2021-28696 | suse_vex | SUSE CVE CVE-2021-28696 | known affected: 312 known not affected: 46 recommended: 495 | 2026-08-01T17:13:20+00:00 | Vulnerability · Source |
| CVE-2021-33909 | suse_vex | SUSE CVE CVE-2021-33909 | known affected: 469 known not affected: 88 recommended: 1791 | 2026-08-01T17:13:15+00:00 | Vulnerability · Source |
| CVE-2021-33930 | suse_vex | SUSE CVE CVE-2021-33930 | known not affected: 266 recommended: 4 | 2026-08-01T17:13:13+00:00 | Vulnerability · Source |
| CVE-2021-34141 | suse_vex | SUSE CVE CVE-2021-34141 | known affected: 2 known not affected: 26 | 2026-08-01T17:13:12+00:00 | Vulnerability · Source |
| CVE-2021-36978 | suse_vex | SUSE CVE CVE-2021-36978 | known affected: 7 recommended: 133 | 2026-08-01T17:13:09+00:00 | Vulnerability · Source |
| CVE-2021-39252 | suse_vex | SUSE CVE CVE-2021-39252 | recommended: 144 | 2026-08-01T17:13:05+00:00 | Vulnerability · Source |
| CVE-2021-46941 | suse_vex | SUSE CVE CVE-2021-46941 | known affected: 516 known not affected: 210 recommended: 70 | 2026-08-01T17:12:57+00:00 | Vulnerability · Source |
| CVE-2021-47064 | suse_vex | SUSE CVE CVE-2021-47064 | known not affected: 292 | 2026-08-01T17:12:55+00:00 | Vulnerability · Source |
| CVE-2021-47538 | suse_vex | SUSE CVE CVE-2021-47538 | known affected: 324 known not affected: 181 recommended: 433 | 2026-08-01T17:12:42+00:00 | Vulnerability · Source |
| CVE-2022-0204 | suse_vex | SUSE CVE CVE-2022-0204 | known not affected: 51 recommended: 257 | 2026-08-01T17:12:30+00:00 | Vulnerability · Source |
| CVE-2022-0400 | suse_vex | SUSE CVE CVE-2022-0400 | known not affected: 643 | 2026-08-01T17:12:28+00:00 | Vulnerability · Source |
| CVE-2022-1183 | suse_vex | SUSE CVE CVE-2022-1183 | known not affected: 579 recommended: 25 | 2026-08-01T17:12:22+00:00 | Vulnerability · Source |
| CVE-2022-3515 | suse_vex | SUSE CVE CVE-2022-3515 | known affected: 253 known not affected: 1 recommended: 290 | 2026-08-01T17:12:11+00:00 | Vulnerability · Source |
| CVE-2022-3522 | suse_vex | SUSE CVE CVE-2022-3522 | recommended: 47 | 2026-08-01T17:12:10+00:00 | Vulnerability · Source |
| CVE-2022-21296 | suse_vex | SUSE CVE CVE-2022-21296 | known affected: 406 known not affected: 32 recommended: 1076 | 2026-08-01T17:11:57+00:00 | Vulnerability · Source |