Total
276231 CVE
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2023-5290 | 2023-11-07 | N/A | ||
| DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate is unused by its CNA. Notes: none. | ||||
| CVE-2023-5129 | 1 Redhat | 5 Enterprise Linux, Rhel Aus, Rhel E4s and 2 more | 2023-11-07 | 0.0 Low |
| This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. Duplicate of CVE-2023-4863. | ||||
| CVE-2023-4881 | 2023-11-07 | 0.0 Low | ||
| CVE-2023-4881 was wrongly assigned to a bug that was deemed to be a non-security issue by the Linux kernel security team. | ||||
| CVE-2023-4705 | 2023-11-07 | N/A | ||
| CVE-2023-4705 was wrongly assigned to a bug that was deemed to be a non-security issue by the Linux kernel security team. | ||||
| CVE-2023-4701 | 2023-11-07 | N/A | ||
| This CVE ID has been rejected or withdrawn by its CVE Numbering Authority as the vendor eventually states that this issue is identical to CVE-2023-3935 | ||||
| CVE-2023-4621 | 2023-11-07 | N/A | ||
| This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is a duplicate of CVE-2023-4569. | ||||
| CVE-2023-4610 | 2023-11-07 | 0.0 Low | ||
| The SRCU code was added in upstream kernel v6.4-rc1 and removed before v6.4. This bug only existed in development kernels. Please see https://lore.kernel.org/all/ZTKVfoQZplpB8rki@casper.infradead.org and https://bugzilla.suse.com/show_bug.cgi?id=1215932 for more information. | ||||
| CVE-2023-4609 | 2023-11-07 | N/A | ||
| DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate is unused by its CNA. Notes: none. | ||||
| CVE-2023-4567 | 2023-11-07 | N/A | ||
| Issue has been found to be non-reproducible, therefore not a viable flaw. | ||||
| CVE-2023-4563 | 2023-11-07 | N/A | ||
| This was assigned as a duplicate of CVE-2023-4244. | ||||
| CVE-2023-4526 | 2023-11-07 | N/A | ||
| DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate is unused by its CNA. Notes: none. | ||||
| CVE-2023-4525 | 2023-11-07 | N/A | ||
| DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate is unused by its CNA. Notes: none. | ||||
| CVE-2023-4524 | 2023-11-07 | N/A | ||
| CVE reject in favor of CVE-2023-40547 | ||||
| CVE-2023-4413 | 2023-11-07 | N/A | ||
| ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: Permission to access the file is limited to administrative users only by default. | ||||
| CVE-2023-4330 | 2023-11-07 | N/A | ||
| Broadcom were unable to duplicate the attack as described by Intel DCG Team. | ||||
| CVE-2023-4275 | 2023-11-07 | N/A | ||
| It is invalid. | ||||
| CVE-2023-4205 | 2023-11-07 | N/A | ||
| This was deemed as a false positive both by the reporter and upstream kernel. | ||||
| CVE-2023-4026 | 2023-11-07 | N/A | ||
| ** REJECT ** DO NOT USE THIS CVE RECORD. ConsultIDs: CVE-2023-4024. Reason: This record is a duplicate of CVE-2023-4024. Notes: All CVE users should reference CVE-2023-4024 instead of this record. All references and descriptions in this record have been removed to prevent accidental usage. | ||||
| CVE-2023-46517 | 2023-11-07 | N/A | ||
| DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none. | ||||
| CVE-2023-46267 | 2023-11-07 | N/A | ||
| DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2023-5631. Reason: This candidate is a duplicate of CVE-2023-5631. Notes: All CVE users should reference CVE-2023-5631 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage. | ||||