VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291911 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-46263 | redhat_vex | kernel: drm/amd/display: Fix out-of-bounds stream encoder index v3 | known affected: 198 known not affected: 76 | 2026-08-01T13:38:38+00:00 | Vulnerability · Source |
| CVE-2026-46311 | redhat_vex | kernel: drm/amdgpu/userq: fix access to stale wptr mapping | known affected: 274 | 2026-08-01T13:33:55+00:00 | Vulnerability · Source |
| CVE-2026-46276 | redhat_vex | kernel: drm/amdgpu: fix zero-size GDS range init on RDNA4 | known affected: 274 | 2026-08-01T13:33:47+00:00 | Vulnerability · Source |
| CVE-2026-52987 | redhat_vex | kernel: drm/amdgpu: avoid double drm_exec_fini() in userq validate | known affected: 184 known not affected: 76 under investigation: 14 | 2026-08-01T13:23:22+00:00 | Vulnerability · Source |
| CVE-2026-63842 | redhat_vex | kernel: drm/amdgpu/jpeg: set no_user_fence for JPEG v5.0.0 ring | known affected: 198 known not affected: 76 | 2026-08-01T07:03:20+00:00 | Vulnerability · Source |
| CVE-2026-57053 | redhat_vex | libidn: GNU libidn: Out-of-bounds read in ToUnicode APIs | fixed: 3 known affected: 8 known not affected: 10 | 2026-08-01T03:45:47+00:00 | Vulnerability · Source |
| CVE-2007-0957 | suse_vex | SUSE CVE CVE-2007-0957 | recommended: 75 | 2026-08-01T00:28:16+00:00 | Vulnerability · Source |
| CVE-2007-2721 | suse_vex | SUSE CVE CVE-2007-2721 | known not affected: 224 | 2026-08-01T00:28:12+00:00 | Vulnerability · Source |
| CVE-2007-2798 | suse_vex | SUSE CVE CVE-2007-2798 | recommended: 75 | 2026-08-01T00:28:11+00:00 | Vulnerability · Source |
| CVE-2007-3644 | suse_vex | SUSE CVE CVE-2007-3644 | recommended: 16 | 2026-08-01T00:28:09+00:00 | Vulnerability · Source |
| CVE-2007-5894 | suse_vex | SUSE CVE CVE-2007-5894 | known affected: 2 recommended: 67 | 2026-08-01T00:28:06+00:00 | Vulnerability · Source |
| CVE-2008-2725 | suse_vex | SUSE CVE CVE-2008-2725 | known not affected: 300 | 2026-08-01T00:28:02+00:00 | Vulnerability · Source |
| CVE-2009-0040 | suse_vex | SUSE CVE CVE-2009-0040 | known affected: 1 known not affected: 42 recommended: 289 | 2026-08-01T00:27:57+00:00 | Vulnerability · Source |
| CVE-2009-0652 | suse_vex | SUSE CVE CVE-2009-0652 | recommended: 193 | 2026-08-01T00:27:55+00:00 | Vulnerability · Source |
| CVE-2009-1439 | suse_vex | SUSE CVE CVE-2009-1439 | known not affected: 495 recommended: 42 | 2026-08-01T00:27:50+00:00 | Vulnerability · Source |
| CVE-2009-1955 | suse_vex | SUSE CVE CVE-2009-1955 | recommended: 214 | 2026-08-01T00:27:48+00:00 | Vulnerability · Source |
| CVE-2009-2848 | suse_vex | SUSE CVE CVE-2009-2848 | known not affected: 495 | 2026-08-01T00:27:47+00:00 | Vulnerability · Source |
| CVE-2009-3380 | suse_vex | SUSE CVE CVE-2009-3380 | known affected: 2 known not affected: 63 recommended: 198 | 2026-08-01T00:27:45+00:00 | Vulnerability · Source |
| CVE-2010-0176 | suse_vex | SUSE CVE CVE-2010-0176 | known affected: 3 recommended: 266 | 2026-08-01T00:27:42+00:00 | Vulnerability · Source |
| CVE-2010-0412 | suse_vex | SUSE CVE CVE-2010-0412 | recommended: 133 | 2026-08-01T00:27:41+00:00 | Vulnerability · Source |
| CVE-2010-1167 | suse_vex | SUSE CVE CVE-2010-1167 | recommended: 83 | 2026-08-01T00:27:39+00:00 | Vulnerability · Source |
| CVE-2010-2529 | suse_vex | SUSE CVE CVE-2010-2529 | recommended: 68 | 2026-08-01T00:27:37+00:00 | Vulnerability · Source |
| CVE-2010-2801 | suse_vex | SUSE CVE CVE-2010-2801 | recommended: 83 | 2026-08-01T00:27:35+00:00 | Vulnerability · Source |
| CVE-2010-2948 | suse_vex | SUSE CVE CVE-2010-2948 | known not affected: 125 recommended: 13 | 2026-08-01T00:27:33+00:00 | Vulnerability · Source |
| CVE-2010-3298 | suse_vex | SUSE CVE CVE-2010-3298 | known not affected: 458 recommended: 377 | 2026-08-01T00:27:31+00:00 | Vulnerability · Source |
| CVE-2010-3876 | suse_vex | SUSE CVE CVE-2010-3876 | known not affected: 495 recommended: 89 | 2026-08-01T00:27:28+00:00 | Vulnerability · Source |
| CVE-2010-3877 | suse_vex | SUSE CVE CVE-2010-3877 | known not affected: 495 recommended: 89 | 2026-08-01T00:27:27+00:00 | Vulnerability · Source |
| CVE-2011-1202 | suse_vex | SUSE CVE CVE-2011-1202 | known affected: 3 recommended: 149 | 2026-08-01T00:27:22+00:00 | Vulnerability · Source |
| CVE-2011-1675 | suse_vex | SUSE CVE CVE-2011-1675 | known not affected: 55 | 2026-08-01T00:27:21+00:00 | Vulnerability · Source |
| CVE-2011-1677 | suse_vex | SUSE CVE CVE-2011-1677 | known not affected: 55 | 2026-08-01T00:27:19+00:00 | Vulnerability · Source |
| CVE-2011-1837 | suse_vex | SUSE CVE CVE-2011-1837 | recommended: 180 | 2026-08-01T00:27:15+00:00 | Vulnerability · Source |
| CVE-2011-2489 | suse_vex | SUSE CVE CVE-2011-2489 | known affected: 394 recommended: 102 | 2026-08-01T00:27:12+00:00 | Vulnerability · Source |
| CVE-2011-2517 | suse_vex | SUSE CVE CVE-2011-2517 | known not affected: 495 recommended: 31 | 2026-08-01T00:27:10+00:00 | Vulnerability · Source |
| CVE-2011-3149 | suse_vex | SUSE CVE CVE-2011-3149 | recommended: 191 | 2026-08-01T00:27:08+00:00 | Vulnerability · Source |
| CVE-2011-4315 | suse_vex | SUSE CVE CVE-2011-4315 | known not affected: 5 recommended: 10 | 2026-08-01T00:27:03+00:00 | Vulnerability · Source |
| CVE-2011-4600 | suse_vex | SUSE CVE CVE-2011-4600 | recommended: 796 | 2026-08-01T00:27:01+00:00 | Vulnerability · Source |
| CVE-2012-0028 | suse_vex | SUSE CVE CVE-2012-0028 | known not affected: 513 | 2026-08-01T00:26:59+00:00 | Vulnerability · Source |
| CVE-2012-0217 | suse_vex | SUSE CVE CVE-2012-0217 | recommended: 250 | 2026-08-01T00:26:58+00:00 | Vulnerability · Source |
| CVE-2012-0390 | suse_vex | SUSE CVE CVE-2012-0390 | recommended: 247 | 2026-08-01T00:26:56+00:00 | Vulnerability · Source |
| CVE-2012-1090 | suse_vex | SUSE CVE CVE-2012-1090 | known not affected: 496 recommended: 88 | 2026-08-01T00:26:51+00:00 | Vulnerability · Source |
| CVE-2012-1096 | suse_vex | SUSE CVE CVE-2012-1096 | known affected: 18 | 2026-08-01T00:26:49+00:00 | Vulnerability · Source |
| CVE-2012-1152 | suse_vex | SUSE CVE CVE-2012-1152 | known not affected: 24 recommended: 72 | 2026-08-01T00:26:48+00:00 | Vulnerability · Source |
| CVE-2012-1716 | suse_vex | SUSE CVE CVE-2012-1716 | known affected: 1 known not affected: 51 recommended: 163 | 2026-08-01T00:26:46+00:00 | Vulnerability · Source |
| CVE-2012-2393 | suse_vex | SUSE CVE CVE-2012-2393 | recommended: 148 | 2026-08-01T00:26:42+00:00 | Vulnerability · Source |
| CVE-2012-2657 | suse_vex | SUSE CVE CVE-2012-2657 | known not affected: 328 | 2026-08-01T00:26:40+00:00 | Vulnerability · Source |
| CVE-2012-3868 | suse_vex | SUSE CVE CVE-2012-3868 | recommended: 411 | 2026-08-01T00:26:34+00:00 | Vulnerability · Source |
| CVE-2012-4287 | suse_vex | SUSE CVE CVE-2012-4287 | recommended: 138 | 2026-08-01T00:26:30+00:00 | Vulnerability · Source |
| CVE-2012-6536 | suse_vex | SUSE CVE CVE-2012-6536 | known not affected: 410 | 2026-08-01T00:26:28+00:00 | Vulnerability · Source |
| CVE-2012-6701 | suse_vex | SUSE CVE CVE-2012-6701 | known not affected: 466 | 2026-08-01T00:26:26+00:00 | Vulnerability · Source |
| CVE-2012-6704 | suse_vex | SUSE CVE CVE-2012-6704 | known not affected: 526 recommended: 182 | 2026-08-01T00:26:25+00:00 | Vulnerability · Source |