Known Exploited Vulnerabilities (KEV)
ndaal KEV
| ID | Title | Severity | CVSS | EPSS | Source | Updated |
|---|---|---|---|---|---|---|
| cve-2026-43281 | kernel: mailbox: Prevent out-of-bounds access in fw_mbox_index_xlate() | HIGH | 7.1 | N/A | cvelistv5 | 2026-07-22 |
| cve-2026-43279 | SUSE CVE CVE-2026-43279 | MEDIUM | 5.5 | N/A | cvelistv5 | 2026-08-31 |
| cve-2026-43278 | SUSE CVE CVE-2026-43278 | MEDIUM | 5.5 | N/A | cvelistv5 | 2026-08-31 |
| cve-2026-43277 | SUSE CVE CVE-2026-43277 | MEDIUM | 5.5 | N/A | cvelistv5 | 2026-09-11 |
| cve-2026-43276 | SUSE CVE CVE-2026-43276 | MEDIUM | 5.5 | N/A | cvelistv5 | 2026-09-18 |
| cve-2026-43275 | kernel: scsi: ufs: core: Flush exception handling work when RPM level is zero | MEDIUM | 5.5 | N/A | cvelistv5 | 2026-06-28 |
| cve-2026-43273 | SUSE CVE CVE-2026-43273 | MEDIUM | 5.5 | N/A | cvelistv5 | 2026-09-18 |
| cve-2026-43271 | SUSE CVE CVE-2026-43271 | MEDIUM | 5.3 | N/A | cvelistv5 | 2026-09-18 |
| cve-2026-43266 | SUSE CVE CVE-2026-43266 | MEDIUM | 5.5 | N/A | cvelistv5 | 2026-09-11 |
| cve-2026-43265 | kernel: KVM: x86: Ignore -EBUSY when checking nested events from vcpu_block() | MEDIUM | 5.5 | N/A | cvelistv5 | 2026-06-28 |
| cve-2026-43264 | SUSE CVE CVE-2026-43264 | LOW | 3.3 | N/A | cvelistv5 | 2026-08-31 |
| cve-2026-43262 | SUSE CVE CVE-2026-43262 | MEDIUM | 5.5 | N/A | cvelistv5 | 2026-09-11 |
| cve-2026-43261 | SUSE CVE CVE-2026-43261 | MEDIUM | 5.5 | N/A | cvelistv5 | 2026-08-31 |
| cve-2026-43260 | SUSE CVE CVE-2026-43260 | MEDIUM | 5.5 | N/A | cvelistv5 | 2026-08-31 |
| cve-2026-43257 | SUSE CVE CVE-2026-43257 | MEDIUM | 5.5 | N/A | cvelistv5 | 2026-09-11 |
| cve-2026-43255 | SUSE CVE CVE-2026-43255 | MEDIUM | 4.7 | N/A | cvelistv5 | 2026-09-16 |
| cve-2026-43253 | SUSE CVE CVE-2026-43253 | MEDIUM | 5.5 | N/A | cvelistv5 | 2026-09-16 |
| cve-2026-43252 | SUSE CVE CVE-2026-43252 | MEDIUM | 5.5 | N/A | cvelistv5 | 2026-09-11 |
| cve-2026-43251 | kernel: HID: prodikeys: Check presence of pm->input_ep82 | MEDIUM | 5.5 | N/A | cvelistv5 | 2026-07-02 |
| cve-2026-43248 | SUSE CVE CVE-2026-43248 | MEDIUM | 5.5 | N/A | cvelistv5 | 2026-09-19 |
| cve-2026-43246 | SUSE CVE CVE-2026-43246 | MEDIUM | 5.5 | N/A | cvelistv5 | 2026-09-11 |
| cve-2026-43243 | SUSE CVE CVE-2026-43243 | MEDIUM | 5.5 | N/A | cvelistv5 | 2026-08-31 |
| cve-2026-43239 | SUSE CVE CVE-2026-43239 | MEDIUM | 5.5 | N/A | cvelistv5 | 2026-09-11 |
| cve-2026-43238 | SUSE CVE CVE-2026-43238 | MEDIUM | 5.5 | N/A | cvelistv5 | 2026-09-11 |
| cve-2026-43233 | SUSE CVE CVE-2026-43233 | MEDIUM | 5.5 | N/A | cvelistv5 | 2026-09-11 |
| cve-2026-43231 | SUSE CVE CVE-2026-43231 | MEDIUM | 5.5 | N/A | cvelistv5 | 2026-08-31 |
| cve-2026-43223 | SUSE CVE CVE-2026-43223 | MEDIUM | 4.3 | N/A | cvelistv5 | 2026-08-31 |
| cve-2026-43220 | kernel: iommu/amd: serialize sequence allocation under concurrent TLB invalidations | UNKNOWN | N/A | N/A | cvelistv5 | 2026-06-28 |
| cve-2026-43218 | SUSE CVE CVE-2026-43218 | LOW | 3.3 | N/A | cvelistv5 | 2026-08-31 |
| cve-2026-43215 | SUSE CVE CVE-2026-43215 | MEDIUM | 5.8 | N/A | cvelistv5 | 2026-08-31 |