Vulnerabilidades explotables hoy
349,525en la vista actual
Score único combinando CVSS, membresía KEV y EPSS. Cada CVE con su ficha propia — timeline desde publicación hasta explotación activa.
En catálogo KEV1,647
Nuevos KEV · 24H0
Exploit Today ≥ 701,582
Distribución · última ventana
- Crítico1,333
- Alto4,369
- Medio3,738
- Bajo297
Ventana
Severidad
Filtros
CVECVSSEPSSKEVRExplotTítuloVis.
CVE-2022-47483—0.5%
——0——CVE-2024-20045—0.5%
——0——CVE-2023-20813—0.5%
——0——CVE-2023-21080—0.5%
——0——CVE-2022-48453—0.5%
——0——CVE-2022-47481—0.5%
——0——CVE-2022-48376—0.5%
——0——CVE-2022-47480—0.5%
——0——CVE-2025-66433—0.5%
——0——CVE-2023-21378—0.5%
——0——CVE-2021-0948—0.5%
——0——CVE-2022-48377—0.5%
——0——CVE-2022-48375—0.5%
——0——CVE-2023-21376—0.5%
——0——CVE-2025-22434—0.5%
——0——CVE-2022-48379—0.5%
——0——CVE-2023-20828—0.5%
——0——CVE-2023-38553—0.5%
——0——CVE-2026-532315.5 MED0.5%
——0In the Linux kernel, the following vulnerability has been resolved:
net: phy: don't try to setup PHY-driven SFP cages when using genphy
We don't have support for PHY-driver SFP cages with the genphy code.
On top of that, it was found by sashiko that running
sfp_bus_add_upstream() for genphy deadlocks, as for genphy the PHY
probing runs under RTNL, which isn't the case for non-genphy drivers.
This problem was reproduced, and does lead to a deadlock on RTNL.
Before the blamed commit, the phy_sfp_probe() call was made by
individual PHY drivers, so there was no way to get to the SFP probing
path when using genphy.
Let's therefore only run phy_sfp_probe when not using genphy.17dCVE-2022-47490—0.5%
——0——CVE-2026-35154—0.5%
——0——CVE-2025-48066—0.5%
——0——CVE-2026-24311—0.5%
——0——CVE-2022-47492—0.5%
——0——CVE-2025-21456—0.4%
——0——CVE-2025-21426—0.5%
——0——CVE-2026-26334—0.5%
——0——CVE-2025-22409—0.5%
——0——CVE-2026-8049—0.5%
——0——CVE-2023-20821—0.5%
——0——CVE-2022-20267—0.5%
——0——CVE-2023-20822—0.5%
——0——CVE-2023-32822—0.5%
——0——CVE-2022-47352—0.5%
——0——CVE-2025-39941—0.5%
——0——CVE-2025-27043—0.4%
——0——CVE-2026-23295—0.5%
——0——CVE-2025-27044—0.5%
——0——CVE-2023-21055—0.5%
——0——CVE-2024-51515—0.5%
——0——