linux
oracle- Software type
- —
- Catalog vulnerabilities
- 230
Severity across 1 analyzed records
Verify to analyze this security profile
A short verification protects source data and prevents automated AI requests.
en
Severity across 1 analyzed records
A short verification protects source data and prevents automated AI requests.
The GCVE catalog currently lists 230 vulnerability records affecting linux.
Among the 1 records analyzed by CyStack, 1 are High or Critical and 1 appear in the CISA KEV catalog.
Compare the version you run with each vulnerability and the provider guidance below. The data only includes records analyzed so far.
| CVE | Exploitation status | Fix | Published | Severity |
|---|---|---|---|---|
CVE-2026-35233CVE-2026-35233 | Exploitation statusNot known exploited | FixNot confirmed | Published05/01/2026 | SeverityMedium |
CVE-2026-21996CVE-2026-21996 | Exploitation statusNot known exploited | FixNot confirmed | Published05/01/2026 | SeverityLow |
CVE-2026-21991CVE-2026-21991 | Exploitation statusNot known exploited | FixNot confirmed | Published03/16/2026 | SeverityMedium |
CVE-2025-4598Systemd-coredump: race condition that allows a local attacker to crash a suid program and gain read access to the resulting core dump | Exploitation statusPublic exploit | FixYes | Published05/30/2025 | SeverityMedium |
CVE-2022-21505CVE-2022-21505 | Exploitation statusNot known exploited | FixNot confirmed | Published12/24/2024 | SeverityMedium |
CVE-2023-22024CVE-2023-22024 | Exploitation statusNot known exploited | FixNot confirmed | Published09/20/2023 | SeverityMedium |
CVE-2022-21385CVE-2022-21385 | Exploitation statusNot known exploited | FixNot confirmed | Published08/29/2022 | SeverityMedium |
CVE-2022-21504CVE-2022-21504 | Exploitation statusNot known exploited | FixNot confirmed | Published06/14/2022 | SeverityMedium |
CVE-2022-21499CVE-2022-21499 | Exploitation statusNot known exploited | FixNot confirmed | Published06/09/2022 | SeverityMedium |
CVE-2021-3551CVE-2021-3551 | Exploitation statusNot confirmed | FixNot confirmed | Published02/16/2022 | SeverityUnknown |
CVE-2021-2464CVE-2021-2464 | Exploitation statusNot known exploited | FixNot confirmed | Published09/24/2021 | SeverityHigh |
CVE-2018-17962CVE-2018-17962 | Exploitation statusNot confirmed | FixNot confirmed | Published10/09/2018 | SeverityUnknown |
CVE-2015-7701CVE-2015-7701 | Exploitation statusNot confirmed | FixNot confirmed | Published08/07/2017 | SeverityUnknown |
CVE-2015-7691CVE-2015-7691 | Exploitation statusNot confirmed | FixNot confirmed | Published08/07/2017 | SeverityUnknown |
CVE-2015-7852CVE-2015-7852 | Exploitation statusNot confirmed | FixNot confirmed | Published08/07/2017 | SeverityUnknown |
CVE-2015-7692CVE-2015-7692 | Exploitation statusNot confirmed | FixNot confirmed | Published08/07/2017 | SeverityUnknown |
CVE-2015-7702CVE-2015-7702 | Exploitation statusNot confirmed | FixNot confirmed | Published08/07/2017 | SeverityUnknown |
CVE-2015-7703CVE-2015-7703 | Exploitation statusNot confirmed | FixNot confirmed | Published07/24/2017 | SeverityUnknown |
CVE-2015-5219CVE-2015-5219 | Exploitation statusNot confirmed | FixNot confirmed | Published07/21/2017 | SeverityUnknown |
CVE-2016-1908CVE-2016-1908 | Exploitation statusNot known exploited | FixNot confirmed | Published04/11/2017 | SeverityCritical |
CVE-2015-8896CVE-2015-8896 | Exploitation statusNot confirmed | FixNot confirmed | Published03/15/2017 | SeverityUnknown |
CVE-2016-2518CVE-2016-2518 | Exploitation statusNot confirmed | FixNot confirmed | Published01/30/2017 | SeverityUnknown |
CVE-2015-7977CVE-2015-7977 | Exploitation statusNot confirmed | FixNot confirmed | Published01/30/2017 | SeverityUnknown |
CVE-2016-7039CVE-2016-7039 | Exploitation statusNot confirmed | FixNot confirmed | Published10/16/2016 | SeverityUnknown |
CVE-2016-0617CVE-2016-0617 | Exploitation statusNot known exploited | FixNot confirmed | Published09/30/2016 | SeverityUnknown |
CVE-2016-2776CVE-2016-2776 | Exploitation statusPublic exploit | FixNot confirmed | Published09/28/2016 | SeverityUnknown |
CVE-2016-7166CVE-2016-7166 | Exploitation statusNot confirmed | FixNot confirmed | Published09/21/2016 | SeverityUnknown |
CVE-2016-4809CVE-2016-4809 | Exploitation statusNot confirmed | FixNot confirmed | Published09/21/2016 | SeverityUnknown |
CVE-2016-5844CVE-2016-5844 | Exploitation statusNot confirmed | FixNot confirmed | Published09/21/2016 | SeverityUnknown |
CVE-2016-6250CVE-2016-6250 | Exploitation statusNot confirmed | FixNot confirmed | Published09/21/2016 | SeverityUnknown |
CVE-2016-5418CVE-2016-5418 | Exploitation statusNot confirmed | FixNot confirmed | Published09/21/2016 | SeverityUnknown |
CVE-2015-8922CVE-2015-8922 | Exploitation statusNot confirmed | FixNot confirmed | Published09/20/2016 | SeverityUnknown |
CVE-2016-6302CVE-2016-6302 | Exploitation statusNot confirmed | FixNot confirmed | Published09/16/2016 | SeverityUnknown |
CVE-2016-2182CVE-2016-2182 | Exploitation statusNot confirmed | FixNot confirmed | Published09/16/2016 | SeverityUnknown |
CVE-2016-2179CVE-2016-2179 | Exploitation statusNot confirmed | FixNot confirmed | Published09/16/2016 | SeverityUnknown |
CVE-2016-2181CVE-2016-2181 | Exploitation statusNot confirmed | FixNot confirmed | Published09/16/2016 | SeverityUnknown |
CVE-2016-5404CVE-2016-5404 | Exploitation statusNot confirmed | FixNot confirmed | Published09/07/2016 | SeverityUnknown |
CVE-2016-5408CVE-2016-5408 | Exploitation statusNot confirmed | FixNot confirmed | Published08/10/2016 | SeverityUnknown |
CVE-2016-6198CVE-2016-6198 | Exploitation statusNot confirmed | FixNot confirmed | Published08/06/2016 | SeverityUnknown |
CVE-2016-6197CVE-2016-6197 | Exploitation statusNot confirmed | FixNot confirmed | Published08/06/2016 | SeverityUnknown |
CVE-2016-2837CVE-2016-2837 | Exploitation statusNot confirmed | FixNot confirmed | Published08/05/2016 | SeverityUnknown |
CVE-2016-5264CVE-2016-5264 | Exploitation statusNot confirmed | FixNot confirmed | Published08/05/2016 | SeverityUnknown |
CVE-2016-5262CVE-2016-5262 | Exploitation statusNot confirmed | FixNot confirmed | Published08/05/2016 | SeverityUnknown |
CVE-2016-5254CVE-2016-5254 | Exploitation statusNot confirmed | FixNot confirmed | Published08/05/2016 | SeverityUnknown |
CVE-2016-5263CVE-2016-5263 | Exploitation statusNot confirmed | FixNot confirmed | Published08/05/2016 | SeverityUnknown |
CVE-2016-5265CVE-2016-5265 | Exploitation statusNot confirmed | FixNot confirmed | Published08/05/2016 | SeverityUnknown |
CVE-2016-5259CVE-2016-5259 | Exploitation statusNot confirmed | FixNot confirmed | Published08/05/2016 | SeverityUnknown |
CVE-2016-5252CVE-2016-5252 | Exploitation statusNot confirmed | FixNot confirmed | Published08/05/2016 | SeverityUnknown |
CVE-2016-5258CVE-2016-5258 | Exploitation statusNot confirmed | FixNot confirmed | Published08/05/2016 | SeverityUnknown |
CVE-2016-5403CVE-2016-5403 | Exploitation statusNot confirmed | FixNot confirmed | Published08/02/2016 | SeverityUnknown |
CVE-2016-2180CVE-2016-2180 | Exploitation statusNot confirmed | FixNot confirmed | Published08/01/2016 | SeverityUnknown |
CVE-2016-3477CVE-2016-3477 | Exploitation statusNot known exploited | FixNot confirmed | Published07/21/2016 | SeverityUnknown |
CVE-2016-5440CVE-2016-5440 | Exploitation statusNot known exploited | FixNot confirmed | Published07/21/2016 | SeverityUnknown |
CVE-2016-3508CVE-2016-3508 | Exploitation statusNot known exploited | FixNot confirmed | Published07/21/2016 | SeverityUnknown |
CVE-2016-3587CVE-2016-3587 | Exploitation statusNot known exploited | FixNot confirmed | Published07/21/2016 | SeverityUnknown |
CVE-2016-3521CVE-2016-3521 | Exploitation statusNot known exploited | FixNot confirmed | Published07/21/2016 | SeverityUnknown |
CVE-2016-3615CVE-2016-3615 | Exploitation statusNot known exploited | FixNot confirmed | Published07/21/2016 | SeverityUnknown |
CVE-2016-3606CVE-2016-3606 | Exploitation statusNot known exploited | FixNot confirmed | Published07/21/2016 | SeverityUnknown |
CVE-2016-3610CVE-2016-3610 | Exploitation statusNot known exploited | FixNot confirmed | Published07/21/2016 | SeverityUnknown |
CVE-2016-5444CVE-2016-5444 | Exploitation statusNot known exploited | FixNot confirmed | Published07/21/2016 | SeverityUnknown |
CVE-2016-3452CVE-2016-3452 | Exploitation statusNot known exploited | FixNot confirmed | Published07/21/2016 | SeverityUnknown |
CVE-2016-3458CVE-2016-3458 | Exploitation statusNot known exploited | FixNot confirmed | Published07/21/2016 | SeverityUnknown |
CVE-2016-3598CVE-2016-3598 | Exploitation statusNot known exploited | FixNot confirmed | Published07/21/2016 | SeverityUnknown |
CVE-2016-3500CVE-2016-3500 | Exploitation statusNot known exploited | FixNot confirmed | Published07/21/2016 | SeverityUnknown |
CVE-2016-3550CVE-2016-3550 | Exploitation statusNot known exploited | FixNot confirmed | Published07/21/2016 | SeverityUnknown |
CVE-2016-5385CVE-2016-5385 | Exploitation statusNot confirmed | FixNot confirmed | Published07/19/2016 | SeverityUnknown |
CVE-2016-5388CVE-2016-5388 | Exploitation statusNot confirmed | FixNot confirmed | Published07/19/2016 | SeverityUnknown |
CVE-2016-5387CVE-2016-5387 | Exploitation statusNot confirmed | FixNot confirmed | Published07/19/2016 | SeverityUnknown |
CVE-2016-5386CVE-2016-5386 | Exploitation statusNot confirmed | FixNot confirmed | Published07/19/2016 | SeverityUnknown |
CVE-2016-4998CVE-2016-4998 | Exploitation statusNot confirmed | FixNot confirmed | Published07/03/2016 | SeverityUnknown |
CVE-2016-4997CVE-2016-4997 | Exploitation statusPublic exploit | FixNot confirmed | Published07/03/2016 | SeverityUnknown |
CVE-2016-4470CVE-2016-4470 | Exploitation statusNot confirmed | FixNot confirmed | Published06/27/2016 | SeverityUnknown |
CVE-2016-2178CVE-2016-2178 | Exploitation statusNot confirmed | FixNot confirmed | Published06/20/2016 | SeverityUnknown |
CVE-2016-2177CVE-2016-2177 | Exploitation statusNot confirmed | FixNot confirmed | Published06/20/2016 | SeverityUnknown |
CVE-2016-5118CVE-2016-5118 | Exploitation statusNot confirmed | FixNot confirmed | Published06/10/2016 | SeverityUnknown |
CVE-2016-4448CVE-2016-4448 | Exploitation statusNot confirmed | FixNot confirmed | Published06/09/2016 | SeverityUnknown |
CVE-2016-5126CVE-2016-5126 | Exploitation statusNot confirmed | FixNot confirmed | Published06/01/2016 | SeverityUnknown |
CVE-2016-4805CVE-2016-4805 | Exploitation statusNot confirmed | FixNot confirmed | Published05/23/2016 | SeverityUnknown |
CVE-2016-4581CVE-2016-4581 | Exploitation statusNot confirmed | FixNot confirmed | Published05/23/2016 | SeverityUnknown |
CVE-2016-4913CVE-2016-4913 | Exploitation statusNot confirmed | FixNot confirmed | Published05/23/2016 | SeverityUnknown |
CVE-2016-4951CVE-2016-4951 | Exploitation statusNot confirmed | FixNot confirmed | Published05/23/2016 | SeverityUnknown |
CVE-2015-4643CVE-2015-4643 | Exploitation statusNot confirmed | FixNot confirmed | Published05/16/2016 | SeverityUnknown |
CVE-2016-3710CVE-2016-3710 | Exploitation statusNot confirmed | FixNot confirmed | Published05/11/2016 | SeverityUnknown |
CVE-2016-4554CVE-2016-4554 | Exploitation statusNot confirmed | FixNot confirmed | Published05/10/2016 | SeverityUnknown |
CVE-2016-4553CVE-2016-4553 | Exploitation statusNot confirmed | FixNot confirmed | Published05/10/2016 | SeverityUnknown |
CVE-2016-4555CVE-2016-4555 | Exploitation statusNot confirmed | FixNot confirmed | Published05/10/2016 | SeverityUnknown |
CVE-2016-4556CVE-2016-4556 | Exploitation statusNot confirmed | FixNot confirmed | Published05/10/2016 | SeverityUnknown |
CVE-2016-3715CVE-2016-3715 | Exploitation statusKEV | FixNot confirmed | Published05/05/2016 | SeverityMedium |
CVE-2016-3718CVE-2016-3718 | Exploitation statusKEV | FixNot confirmed | Published05/05/2016 | SeverityMedium |
CVE-2016-2143CVE-2016-2143 | Exploitation statusNot confirmed | FixNot confirmed | Published04/27/2016 | SeverityUnknown |
CVE-2016-4051CVE-2016-4051 | Exploitation statusNot confirmed | FixNot confirmed | Published04/25/2016 | SeverityUnknown |
CVE-2016-4053CVE-2016-4053 | Exploitation statusNot confirmed | FixNot confirmed | Published04/25/2016 | SeverityUnknown |
CVE-2016-4054CVE-2016-4054 | Exploitation statusNot confirmed | FixNot confirmed | Published04/25/2016 | SeverityUnknown |
CVE-2016-0648CVE-2016-0648 | Exploitation statusNot known exploited | FixNot confirmed | Published04/21/2016 | SeverityUnknown |
CVE-2016-0666CVE-2016-0666 | Exploitation statusNot known exploited | FixNot confirmed | Published04/21/2016 | SeverityUnknown |
CVE-2016-0650CVE-2016-0650 | Exploitation statusNot known exploited | FixNot confirmed | Published04/21/2016 | SeverityUnknown |
CVE-2016-3427CVE-2016-3427 | Exploitation statusKEV | FixNot confirmed | Published04/21/2016 | SeverityCritical |
CVE-2016-0649CVE-2016-0649 | Exploitation statusNot known exploited | FixNot confirmed | Published04/21/2016 | SeverityUnknown |
CVE-2016-0646CVE-2016-0646 | Exploitation statusNot known exploited | FixNot confirmed | Published04/21/2016 | SeverityUnknown |
CVE-2016-0644CVE-2016-0644 | Exploitation statusNot known exploited | FixNot confirmed | Published04/21/2016 | SeverityUnknown |
CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.
Explore CyStack VulnScan