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-63882 | redhat_vex | kernel: drm/amdkfd: fix NULL pointer bug in svm_range_set_attr | known affected: 274 | 2026-07-31T18:19:18+00:00 | Vulnerability · Source |
| CVE-2026-46150 | redhat_vex | kernel: fanotify: fix false positive on permission events | fixed: 762 known affected: 64 | 2026-07-31T18:19:04+00:00 | Vulnerability · Source |
| CVE-2026-31692 | redhat_vex | kernel: rtnetlink: add missing netlink_ns_capable() check for peer netns | fixed: 459 known affected: 136 known not affected: 14 | 2026-07-31T18:19:00+00:00 | Vulnerability · Source |
| CVE-2026-43116 | redhat_vex | kernel: netfilter: ctnetlink: ensure safe access to master conntrack | fixed: 1980 known affected: 64 | 2026-07-31T18:19:00+00:00 | Vulnerability · Source |
| CVE-2026-64097 | redhat_vex | kernel: drm/amd/display: Validate GPIO pin LUT table size before iterating | known affected: 274 | 2026-07-31T18:13:21+00:00 | Vulnerability · Source |
| CVE-2026-9149 | redhat_vex | libsolv: Heap buffer overflow in libsolv repo_add_solv via negative maxsize from crafted .solv file | fixed: 149 known affected: 22 known not affected: 88 | 2026-07-31T17:51:19+00:00 | Vulnerability · Source |
| CVE-2026-9150 | redhat_vex | libsolv: Stack-based buffer overflow in libsolv's Debian metadata parser when handling SHA384/SHA512 checksums | fixed: 149 known affected: 17 known not affected: 93 | 2026-07-31T17:51:19+00:00 | Vulnerability · Source |
| CVE-2019-19959 | suse_vex | SUSE CVE CVE-2019-19959 | known affected: 364 known not affected: 268 recommended: 440 | 2026-07-31T17:07:08+00:00 | Vulnerability · Source |
| CVE-2020-6581 | suse_vex | SUSE CVE CVE-2020-6581 | known not affected: 39 | 2026-07-31T17:07:02+00:00 | Vulnerability · Source |
| CVE-2020-8428 | suse_vex | SUSE CVE CVE-2020-8428 | known affected: 382 known not affected: 226 recommended: 1282 | 2026-07-31T17:06:58+00:00 | Vulnerability · Source |
| CVE-2020-9843 | suse_vex | SUSE CVE CVE-2020-9843 | known affected: 97 recommended: 1078 | 2026-07-31T17:06:56+00:00 | Vulnerability · Source |
| CVE-2020-12396 | suse_vex | SUSE CVE CVE-2020-12396 | known affected: 21 recommended: 9 | 2026-07-31T17:06:52+00:00 | Vulnerability · Source |
| CVE-2020-14765 | suse_vex | SUSE CVE CVE-2020-14765 | known not affected: 90 recommended: 654 | 2026-07-31T17:06:46+00:00 | Vulnerability · Source |
| CVE-2020-16012 | suse_vex | SUSE CVE CVE-2020-16012 | known affected: 56 recommended: 419 | 2026-07-31T17:06:41+00:00 | Vulnerability · Source |
| CVE-2020-16155 | suse_vex | SUSE CVE CVE-2020-16155 | known not affected: 285 | 2026-07-31T17:06:40+00:00 | Vulnerability · Source |
| CVE-2020-16300 | suse_vex | SUSE CVE CVE-2020-16300 | known not affected: 172 recommended: 8 | 2026-07-31T17:06:38+00:00 | Vulnerability · Source |
| CVE-2020-17049 | suse_vex | SUSE CVE CVE-2020-17049 | known affected: 335 known not affected: 368 recommended: 722 | 2026-07-31T17:06:36+00:00 | Vulnerability · Source |
| CVE-2020-19185 | suse_vex | SUSE CVE CVE-2020-19185 | known affected: 1 known not affected: 634 | 2026-07-31T17:06:33+00:00 | Vulnerability · Source |
| CVE-2020-19715 | suse_vex | SUSE CVE CVE-2020-19715 | known not affected: 106 | 2026-07-31T17:06:31+00:00 | Vulnerability · Source |
| CVE-2020-21681 | suse_vex | SUSE CVE CVE-2020-21681 | recommended: 47 | 2026-07-31T17:06:29+00:00 | Vulnerability · Source |
| CVE-2020-25692 | suse_vex | SUSE CVE CVE-2020-25692 | known affected: 392 recommended: 854 | 2026-07-31T17:06:23+00:00 | Vulnerability · Source |
| CVE-2021-3639 | suse_vex | SUSE CVE CVE-2021-3639 | known affected: 1 recommended: 99 | 2026-07-31T17:06:05+00:00 | Vulnerability · Source |
| CVE-2021-3695 | suse_vex | SUSE CVE CVE-2021-3695 | known affected: 353 recommended: 724 | 2026-07-31T17:06:01+00:00 | Vulnerability · Source |
| CVE-2021-4069 | suse_vex | SUSE CVE CVE-2021-4069 | known affected: 363 known not affected: 15 recommended: 366 | 2026-07-31T17:05:52+00:00 | Vulnerability · Source |
| CVE-2021-25217 | suse_vex | SUSE CVE CVE-2021-25217 | known affected: 329 recommended: 473 | 2026-07-31T17:05:42+00:00 | Vulnerability · Source |
| CVE-2021-31535 | suse_vex | SUSE CVE CVE-2021-31535 | known affected: 403 recommended: 504 | 2026-07-31T17:05:33+00:00 | Vulnerability · Source |
| CVE-2021-34798 | suse_vex | SUSE CVE CVE-2021-34798 | known affected: 419 known not affected: 5 recommended: 396 | 2026-07-31T17:05:29+00:00 | Vulnerability · Source |
| CVE-2021-45469 | suse_vex | SUSE CVE CVE-2021-45469 | known not affected: 416 | 2026-07-31T17:05:17+00:00 | Vulnerability · Source |
| CVE-2021-46904 | suse_vex | SUSE CVE CVE-2021-46904 | known affected: 480 known not affected: 180 recommended: 264 | 2026-07-31T17:05:15+00:00 | Vulnerability · Source |
| CVE-2021-47279 | suse_vex | SUSE CVE CVE-2021-47279 | known not affected: 330 | 2026-07-31T17:05:10+00:00 | Vulnerability · Source |
| CVE-2022-1015 | suse_vex | SUSE CVE CVE-2022-1015 | known affected: 32 known not affected: 18 recommended: 364 | 2026-07-31T17:04:55+00:00 | Vulnerability · Source |
| CVE-2022-1651 | suse_vex | SUSE CVE CVE-2022-1651 | known affected: 257 known not affected: 339 recommended: 615 | 2026-07-31T17:04:51+00:00 | Vulnerability · Source |
| CVE-2022-3531 | suse_vex | SUSE CVE CVE-2022-3531 | known not affected: 327 | 2026-07-31T17:04:43+00:00 | Vulnerability · Source |
| CVE-2022-22737 | suse_vex | SUSE CVE CVE-2022-22737 | recommended: 413 | 2026-07-31T17:04:31+00:00 | Vulnerability · Source |
| CVE-2022-27666 | suse_vex | SUSE CVE CVE-2022-27666 | known not affected: 208 recommended: 1026 | 2026-07-31T17:04:26+00:00 | Vulnerability · Source |
| CVE-2022-34468 | suse_vex | SUSE CVE CVE-2022-34468 | known affected: 1 recommended: 482 | 2026-07-31T17:04:20+00:00 | Vulnerability · Source |
| CVE-2022-35948 | suse_vex | SUSE CVE CVE-2022-35948 | known not affected: 194 recommended: 128 | 2026-07-31T17:04:19+00:00 | Vulnerability · Source |
| CVE-2022-38238 | suse_vex | SUSE CVE CVE-2022-38238 | known not affected: 330 | 2026-07-31T17:04:16+00:00 | Vulnerability · Source |
| CVE-2022-42890 | suse_vex | SUSE CVE CVE-2022-42890 | recommended: 71 | 2026-07-31T17:04:05+00:00 | Vulnerability · Source |
| CVE-2022-46344 | suse_vex | SUSE CVE CVE-2022-46344 | known affected: 395 recommended: 309 | 2026-07-31T17:03:59+00:00 | Vulnerability · Source |
| CVE-2022-48770 | suse_vex | SUSE CVE CVE-2022-48770 | known affected: 434 known not affected: 202 recommended: 298 | 2026-07-31T17:03:55+00:00 | Vulnerability · Source |
| CVE-2022-48966 | suse_vex | SUSE CVE CVE-2022-48966 | known affected: 390 known not affected: 260 recommended: 311 | 2026-07-31T17:03:45+00:00 | Vulnerability · Source |
| CVE-2022-49048 | suse_vex | SUSE CVE CVE-2022-49048 | known affected: 112 known not affected: 240 | 2026-07-31T17:03:39+00:00 | Vulnerability · Source |
| CVE-2022-49192 | suse_vex | SUSE CVE CVE-2022-49192 | known not affected: 302 recommended: 70 | 2026-07-31T17:03:36+00:00 | Vulnerability · Source |
| CVE-2022-49245 | suse_vex | SUSE CVE CVE-2022-49245 | known not affected: 352 | 2026-07-31T17:03:33+00:00 | Vulnerability · Source |
| CVE-2022-49510 | suse_vex | SUSE CVE CVE-2022-49510 | known affected: 364 known not affected: 302 recommended: 100 | 2026-07-31T17:03:28+00:00 | Vulnerability · Source |
| CVE-2022-49563 | suse_vex | SUSE CVE CVE-2022-49563 | known affected: 424 known not affected: 148 recommended: 370 | 2026-07-31T17:03:25+00:00 | Vulnerability · Source |
| CVE-2022-49883 | suse_vex | SUSE CVE CVE-2022-49883 | known not affected: 397 | 2026-07-31T17:03:19+00:00 | Vulnerability · Source |
| CVE-2022-49911 | suse_vex | SUSE CVE CVE-2022-49911 | known affected: 55 known not affected: 342 recommended: 27 | 2026-07-31T17:03:17+00:00 | Vulnerability · Source |
| CVE-2022-49926 | suse_vex | SUSE CVE CVE-2022-49926 | known affected: 154 known not affected: 258 | 2026-07-31T17:03:16+00:00 | Vulnerability · Source |