VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291277 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-20368 | suse_vex | SUSE CVE CVE-2022-20368 | known affected: 173 recommended: 1756 | 2026-08-14T01:30:21+00:00 | Vulnerability · Source |
| CVE-2022-20421 | suse_vex | SUSE CVE CVE-2022-20421 | known not affected: 197 | 2026-08-14T01:30:19+00:00 | Vulnerability · Source |
| CVE-2022-21271 | suse_vex | SUSE CVE CVE-2022-21271 | known affected: 395 recommended: 372 | 2026-08-14T01:30:14+00:00 | Vulnerability · Source |
| CVE-2022-21366 | suse_vex | SUSE CVE CVE-2022-21366 | known affected: 394 known not affected: 294 recommended: 775 | 2026-08-14T01:30:09+00:00 | Vulnerability · Source |
| CVE-2026-68150 | redhat_vex | kernel: fs/super: fix emergency thaw double-unlock of s_umount | known not affected: 276 | 2026-08-14T01:30:07+00:00 | Vulnerability · Source |
| CVE-2022-21499 | suse_vex | SUSE CVE CVE-2022-21499 | known affected: 216 known not affected: 28 recommended: 1363 | 2026-08-14T01:30:02+00:00 | Vulnerability · Source |
| CVE-2022-22576 | suse_vex | SUSE CVE CVE-2022-22576 | known affected: 263 known not affected: 56 recommended: 342 | 2026-08-14T01:29:55+00:00 | Vulnerability · Source |
| CVE-2022-22941 | suse_vex | SUSE CVE CVE-2022-22941 | known affected: 394 known not affected: 116 recommended: 799 | 2026-08-14T01:29:43+00:00 | Vulnerability · Source |
| CVE-2022-23038 | suse_vex | SUSE CVE CVE-2022-23038 | known affected: 344 known not affected: 61 recommended: 1327 | 2026-08-14T01:29:40+00:00 | Vulnerability · Source |
| CVE-2022-23477 | suse_vex | SUSE CVE CVE-2022-23477 | known affected: 394 known not affected: 60 recommended: 168 | 2026-08-14T01:29:38+00:00 | Vulnerability · Source |
| CVE-2022-23773 | suse_vex | SUSE CVE CVE-2022-23773 | recommended: 180 | 2026-08-14T01:29:33+00:00 | Vulnerability · Source |
| CVE-2022-23825 | suse_vex | SUSE CVE CVE-2022-23825 | recommended: 432 | 2026-08-14T01:29:30+00:00 | Vulnerability · Source |
| CVE-2022-23830 | suse_vex | SUSE CVE CVE-2022-23830 | known affected: 22 recommended: 1346 | 2026-08-14T01:29:28+00:00 | Vulnerability · Source |
| CVE-2022-24122 | suse_vex | SUSE CVE CVE-2022-24122 | known not affected: 390 recommended: 364 | 2026-08-14T01:29:23+00:00 | Vulnerability · Source |
| CVE-2022-24599 | suse_vex | SUSE CVE CVE-2022-24599 | known affected: 220 recommended: 42 | 2026-08-14T01:29:21+00:00 | Vulnerability · Source |
| CVE-2022-24836 | suse_vex | SUSE CVE CVE-2022-24836 | known affected: 394 recommended: 55 | 2026-08-14T01:29:14+00:00 | Vulnerability · Source |
| CVE-2022-24959 | suse_vex | SUSE CVE CVE-2022-24959 | known affected: 344 known not affected: 148 recommended: 1224 | 2026-08-14T01:29:11+00:00 | Vulnerability · Source |
| CVE-2022-26358 | suse_vex | SUSE CVE CVE-2022-26358 | known affected: 349 known not affected: 46 recommended: 446 | 2026-08-14T01:29:04+00:00 | Vulnerability · Source |
| CVE-2022-26360 | suse_vex | SUSE CVE CVE-2022-26360 | known affected: 349 known not affected: 46 recommended: 446 | 2026-08-14T01:29:01+00:00 | Vulnerability · Source |
| CVE-2022-26490 | suse_vex | SUSE CVE CVE-2022-26490 | known affected: 209 known not affected: 21 recommended: 1749 | 2026-08-14T01:28:57+00:00 | Vulnerability · Source |
| CVE-2022-27536 | suse_vex | SUSE CVE CVE-2022-27536 | known not affected: 194 recommended: 126 | 2026-08-14T01:28:47+00:00 | Vulnerability · Source |
| CVE-2022-27672 | suse_vex | SUSE CVE CVE-2022-27672 | known affected: 293 known not affected: 188 recommended: 218 | 2026-08-14T01:28:45+00:00 | Vulnerability · Source |
| CVE-2022-28131 | suse_vex | SUSE CVE CVE-2022-28131 | known not affected: 51 recommended: 281 | 2026-08-14T01:28:41+00:00 | Vulnerability · Source |
| CVE-2022-28389 | suse_vex | SUSE CVE CVE-2022-28389 | known affected: 347 known not affected: 82 recommended: 1261 | 2026-08-14T01:28:37+00:00 | Vulnerability · Source |
| CVE-2022-28796 | suse_vex | SUSE CVE CVE-2022-28796 | known not affected: 388 | 2026-08-14T01:28:33+00:00 | Vulnerability · Source |
| CVE-2022-29500 | suse_vex | SUSE CVE CVE-2022-29500 | known affected: 394 recommended: 3234 | 2026-08-14T01:28:29+00:00 | Vulnerability · Source |
| CVE-2022-29901 | suse_vex | SUSE CVE CVE-2022-29901 | known affected: 219 recommended: 1811 | 2026-08-14T01:28:27+00:00 | Vulnerability · Source |
| CVE-2022-30580 | suse_vex | SUSE CVE CVE-2022-30580 | known affected: 13 known not affected: 114 recommended: 201 | 2026-08-14T01:28:24+00:00 | Vulnerability · Source |
| CVE-2022-30630 | suse_vex | SUSE CVE CVE-2022-30630 | known not affected: 51 recommended: 288 | 2026-08-14T01:28:23+00:00 | Vulnerability · Source |
| CVE-2022-30635 | suse_vex | SUSE CVE CVE-2022-30635 | known not affected: 51 recommended: 285 | 2026-08-14T01:28:22+00:00 | Vulnerability · Source |
| CVE-2022-30787 | suse_vex | SUSE CVE CVE-2022-30787 | recommended: 124 | 2026-08-14T01:28:20+00:00 | Vulnerability · Source |
| CVE-2022-30790 | suse_vex | SUSE CVE CVE-2022-30790 | recommended: 407 | 2026-08-14T01:28:18+00:00 | Vulnerability · Source |
| CVE-2022-31256 | suse_vex | SUSE CVE CVE-2022-31256 | known not affected: 1 recommended: 83 | 2026-08-14T01:28:16+00:00 | Vulnerability · Source |
| CVE-2022-31622 | suse_vex | SUSE CVE CVE-2022-31622 | known not affected: 326 recommended: 32 | 2026-08-14T01:28:15+00:00 | Vulnerability · Source |
| CVE-2022-31623 | suse_vex | SUSE CVE CVE-2022-31623 | known not affected: 326 recommended: 32 | 2026-08-14T01:28:13+00:00 | Vulnerability · Source |
| CVE-2022-32215 | suse_vex | SUSE CVE CVE-2022-32215 | recommended: 627 | 2026-08-14T01:28:09+00:00 | Vulnerability · Source |
| CVE-2022-32250 | suse_vex | SUSE CVE CVE-2022-32250 | known affected: 237 recommended: 1400 | 2026-08-14T01:28:07+00:00 | Vulnerability · Source |
| CVE-2022-33743 | suse_vex | SUSE CVE CVE-2022-33743 | known affected: 259 known not affected: 639 recommended: 646 | 2026-08-14T01:28:00+00:00 | Vulnerability · Source |
| CVE-2022-34169 | suse_vex | SUSE CVE CVE-2022-34169 | known affected: 397 known not affected: 25 recommended: 1419 | 2026-08-14T01:27:57+00:00 | Vulnerability · Source |
| CVE-2022-34472 | suse_vex | SUSE CVE CVE-2022-34472 | known affected: 1 recommended: 482 | 2026-08-14T01:27:55+00:00 | Vulnerability · Source |
| CVE-2022-35977 | suse_vex | SUSE CVE CVE-2022-35977 | recommended: 30 | 2026-08-14T01:27:51+00:00 | Vulnerability · Source |
| CVE-2022-36402 | suse_vex | SUSE CVE CVE-2022-36402 | known affected: 388 known not affected: 439 recommended: 409 | 2026-08-14T01:27:49+00:00 | Vulnerability · Source |
| CVE-2022-36440 | suse_vex | SUSE CVE CVE-2022-36440 | known not affected: 227 recommended: 2 | 2026-08-14T01:27:47+00:00 | Vulnerability · Source |
| CVE-2022-37866 | suse_vex | SUSE CVE CVE-2022-37866 | recommended: 150 | 2026-08-14T01:27:45+00:00 | Vulnerability · Source |
| CVE-2022-38457 | suse_vex | SUSE CVE CVE-2022-38457 | known not affected: 140 recommended: 291 | 2026-08-14T01:27:42+00:00 | Vulnerability · Source |
| CVE-2022-38928 | suse_vex | SUSE CVE CVE-2022-38928 | known not affected: 330 | 2026-08-14T01:27:38+00:00 | Vulnerability · Source |
| CVE-2022-39317 | suse_vex | SUSE CVE CVE-2022-39317 | recommended: 145 | 2026-08-14T01:27:34+00:00 | Vulnerability · Source |
| CVE-2022-41222 | suse_vex | SUSE CVE CVE-2022-41222 | known affected: 376 known not affected: 232 recommended: 692 | 2026-08-14T01:27:28+00:00 | Vulnerability · Source |
| CVE-2022-41848 | suse_vex | SUSE CVE CVE-2022-41848 | known affected: 253 known not affected: 20 recommended: 1493 | 2026-08-14T01:27:25+00:00 | Vulnerability · Source |
| CVE-2022-41849 | suse_vex | SUSE CVE CVE-2022-41849 | known affected: 253 known not affected: 175 recommended: 1125 | 2026-08-14T01:27:24+00:00 | Vulnerability · Source |