VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
294018 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-31455 | suse_vex | SUSE CVE CVE-2026-31455 | first fixed: 2 known affected: 529 known not affected: 96 recommended: 267 | 2026-07-24T02:33:48+00:00 | Vulnerability · Source |
| CVE-2026-31694 | suse_vex | SUSE CVE CVE-2026-31694 | first fixed: 2 known affected: 420 known not affected: 63 recommended: 645 | 2026-07-24T02:32:23+00:00 | Vulnerability · Source |
| CVE-2026-31700 | suse_vex | SUSE CVE CVE-2026-31700 | first fixed: 2 known affected: 451 known not affected: 4 recommended: 487 | 2026-07-24T02:32:19+00:00 | Vulnerability · Source |
| CVE-2026-31703 | suse_vex | SUSE CVE CVE-2026-31703 | first fixed: 2 known affected: 424 known not affected: 177 recommended: 271 | 2026-07-24T02:32:16+00:00 | Vulnerability · Source |
| CVE-2026-31767 | suse_vex | SUSE CVE CVE-2026-31767 | known affected: 526 known not affected: 92 recommended: 122 | 2026-07-24T02:32:06+00:00 | Vulnerability · Source |
| CVE-2026-45676 | suse_vex | SUSE CVE CVE-2026-45676 | known affected: 8 | 2026-07-24T02:25:21+00:00 | Vulnerability · Source |
| CVE-2026-54514 | suse_vex | SUSE CVE CVE-2026-54514 | known affected: 11 recommended: 103 | 2026-07-24T02:17:31+00:00 | Vulnerability · Source |
| CVE-2026-54515 | suse_vex | SUSE CVE CVE-2026-54515 | known affected: 11 recommended: 103 | 2026-07-24T02:17:29+00:00 | Vulnerability · Source |
| CVE-2026-56366 | suse_vex | SUSE CVE CVE-2026-56366 | known affected: 269 known not affected: 8 recommended: 15 | 2026-07-24T02:17:00+00:00 | Vulnerability · Source |
| CVE-2026-56367 | suse_vex | SUSE CVE CVE-2026-56367 | known affected: 85 known not affected: 8 recommended: 245 | 2026-07-24T02:16:58+00:00 | Vulnerability · Source |
| CVE-2026-56372 | suse_vex | SUSE CVE CVE-2026-56372 | known affected: 199 known not affected: 78 recommended: 15 | 2026-07-24T02:16:56+00:00 | Vulnerability · Source |
| CVE-2026-56373 | suse_vex | SUSE CVE CVE-2026-56373 | known affected: 85 known not affected: 8 | 2026-07-24T02:16:54+00:00 | Vulnerability · Source |
| CVE-2026-56377 | suse_vex | SUSE CVE CVE-2026-56377 | known affected: 269 known not affected: 8 recommended: 15 | 2026-07-24T02:16:50+00:00 | Vulnerability · Source |
| CVE-2026-59678 | suse_vex | SUSE CVE CVE-2026-59678 | No product status | 2026-07-24T02:16:11+00:00 | Vulnerability · Source |
| CVE-2026-63811 | suse_vex | SUSE CVE CVE-2026-63811 | No product status | 2026-07-24T02:14:19+00:00 | Vulnerability · Source |
| CVE-2026-63814 | suse_vex | SUSE CVE CVE-2026-63814 | No product status | 2026-07-24T02:14:17+00:00 | Vulnerability · Source |
| CVE-2026-63815 | suse_vex | SUSE CVE CVE-2026-63815 | No product status | 2026-07-24T02:14:15+00:00 | Vulnerability · Source |
| CVE-2026-63816 | suse_vex | SUSE CVE CVE-2026-63816 | No product status | 2026-07-24T02:14:13+00:00 | Vulnerability · Source |
| CVE-2026-63833 | suse_vex | SUSE CVE CVE-2026-63833 | No product status | 2026-07-24T02:14:07+00:00 | Vulnerability · Source |
| CVE-2026-63889 | suse_vex | SUSE CVE CVE-2026-63889 | No product status | 2026-07-24T02:12:59+00:00 | Vulnerability · Source |
| CVE-2026-63890 | suse_vex | SUSE CVE CVE-2026-63890 | No product status | 2026-07-24T02:12:56+00:00 | Vulnerability · Source |
| CVE-2026-64122 | suse_vex | SUSE CVE CVE-2026-64122 | No product status | 2026-07-24T02:12:03+00:00 | Vulnerability · Source |
| CVE-2026-64125 | suse_vex | SUSE CVE CVE-2026-64125 | No product status | 2026-07-24T02:12:00+00:00 | Vulnerability · Source |
| CVE-2026-64132 | suse_vex | SUSE CVE CVE-2026-64132 | No product status | 2026-07-24T02:11:58+00:00 | Vulnerability · Source |
| CVE-2026-64136 | suse_vex | SUSE CVE CVE-2026-64136 | No product status | 2026-07-24T02:11:55+00:00 | Vulnerability · Source |
| CVE-2026-64142 | suse_vex | SUSE CVE CVE-2026-64142 | No product status | 2026-07-24T02:11:51+00:00 | Vulnerability · Source |
| CVE-2026-64150 | suse_vex | SUSE CVE CVE-2026-64150 | No product status | 2026-07-24T02:11:48+00:00 | Vulnerability · Source |
| CVE-2026-64160 | suse_vex | SUSE CVE CVE-2026-64160 | No product status | 2026-07-24T02:11:45+00:00 | Vulnerability · Source |
| CVE-2026-64162 | suse_vex | SUSE CVE CVE-2026-64162 | No product status | 2026-07-24T02:11:43+00:00 | Vulnerability · Source |
| CVE-2024-58077 | redhat_vex | kernel: ASoC: soc-pcm: don't use soc_pcm_ret() on .prepare callback | fixed: 612 known affected: 98 known not affected: 14 | 2026-07-23T23:57:04+00:00 | Vulnerability · Source |
| CVE-2025-21806 | redhat_vex | kernel: net: let net.core.dev_weight always be non-zero | fixed: 303 known affected: 188 | 2026-07-23T23:57:01+00:00 | Vulnerability · Source |
| CVE-2024-57993 | redhat_vex | kernel: HID: hid-thrustmaster: Fix warning in thrustmaster_probe by adding endpoint check | fixed: 303 known affected: 146 known not affected: 42 | 2026-07-23T23:56:59+00:00 | Vulnerability · Source |
| CVE-2025-21847 | redhat_vex | kernel: ASoC: SOF: stream-ipc: Check for cstream nullity in sof_ipc_msg_data() | fixed: 612 known affected: 70 known not affected: 42 | 2026-07-23T23:56:54+00:00 | Vulnerability · Source |
| CVE-2024-58012 | redhat_vex | kernel: ASoC: SOF: Intel: hda-dai: Ensure DAI widget is valid during params | fixed: 612 known affected: 70 known not affected: 42 | 2026-07-23T23:56:52+00:00 | Vulnerability · Source |
| CVE-2025-21853 | redhat_vex | kernel: bpf: avoid holding freeze_mutex during mmap operation | fixed: 612 known affected: 98 known not affected: 14 | 2026-07-23T23:56:44+00:00 | Vulnerability · Source |
| CVE-2024-58057 | redhat_vex | kernel: idpf: convert workqueues to unbound | fixed: 612 known affected: 70 known not affected: 42 | 2026-07-23T23:56:43+00:00 | Vulnerability · Source |
| CVE-2025-21728 | redhat_vex | kernel: bpf: Send signals asynchronously if !preemptible | fixed: 303 known affected: 174 known not affected: 14 | 2026-07-23T23:56:41+00:00 | Vulnerability · Source |
| CVE-2024-58088 | redhat_vex | kernel: bpf: Fix deadlock when freeing cgroup storage | fixed: 612 known affected: 22 known not affected: 90 | 2026-07-23T23:56:37+00:00 | Vulnerability · Source |
| CVE-2022-49353 | redhat_vex | kernel: powerpc/papr_scm: don't requests stats with '0' sized stats buffer | fixed: 303 known affected: 70 known not affected: 118 | 2026-07-23T23:51:42+00:00 | Vulnerability · Source |
| CVE-2022-49648 | redhat_vex | kernel: tracing/histograms: Fix memory leak problem | fixed: 303 known affected: 22 known not affected: 166 | 2026-07-23T23:51:39+00:00 | Vulnerability · Source |
| CVE-2024-53052 | redhat_vex | kernel: io_uring/rw: fix missing NOWAIT check for O_DIRECT start write | fixed: 303 known affected: 22 known not affected: 90 | 2026-07-23T23:51:27+00:00 | Vulnerability · Source |
| CVE-2024-46689 | redhat_vex | kernel: soc: qcom: cmd-db: Map shared memory as WC, not WB | fixed: 303 known affected: 98 known not affected: 14 | 2026-07-23T23:51:26+00:00 | Vulnerability · Source |
| CVE-2022-49443 | redhat_vex | kernel: list: fix a data-race around ep->rdllist | fixed: 303 known affected: 112 known not affected: 76 | 2026-07-23T23:46:55+00:00 | Vulnerability · Source |
| CVE-2025-21745 | redhat_vex | kernel: blk-cgroup: Fix class @block_class's subsystem refcount leakage | fixed: 303 known affected: 188 | 2026-07-23T23:46:46+00:00 | Vulnerability · Source |
| CVE-2025-21790 | redhat_vex | kernel: vxlan: check vxlan_vnigroup_init() return value | fixed: 612 known affected: 22 known not affected: 90 | 2026-07-23T23:46:44+00:00 | Vulnerability · Source |
| CVE-2025-21729 | redhat_vex | kernel: wifi: rtw89: fix race between cancel_hw_scan and hw_scan completion | fixed: 303 known affected: 146 known not affected: 42 | 2026-07-23T23:46:41+00:00 | Vulnerability · Source |
| CVE-2025-21746 | redhat_vex | kernel: Input: synaptics - fix crash when enabling pass-through port | fixed: 303 known affected: 140 known not affected: 48 | 2026-07-23T23:46:35+00:00 | Vulnerability · Source |
| CVE-2025-21848 | redhat_vex | kernel: nfp: bpf: Add check for nfp_app_ctrl_msg_alloc() | fixed: 303 known affected: 22 known not affected: 166 | 2026-07-23T23:46:32+00:00 | Vulnerability · Source |
| CVE-2025-21844 | redhat_vex | kernel: smb: client: Add check for next_buffer in receive_encrypted_standard() | fixed: 612 known affected: 70 known not affected: 42 | 2026-07-23T23:46:30+00:00 | Vulnerability · Source |
| CVE-2024-52332 | redhat_vex | kernel: igb: Fix potential invalid memory access in igb_init_module() | fixed: 612 known affected: 99 known not affected: 14 | 2026-07-23T23:46:27+00:00 | Vulnerability · Source |