BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2025-37945High confidence

net: phy: allow MDIO bus PM ops to start/stop state machine for phylink-controlled PHY

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 31 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Low, lowered one band.downgradedsince 8 Sep 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.19% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: No default targetRemediation target: Normal maintenance

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 31 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

25 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 21 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.25-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.170-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.25-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.25-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-fdeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-intelAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-tegraAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

3 current
CVE-2025-37945 · CSAF 2.0 · revision 43 · interimSUSE Product Security TeamCVE-2025-37945
201 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP7
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
Summary
In the Linux kernel, the following vulnerability has been resolved: net: phy: allow MDIO bus PM ops to start/stop state machine for phylink-controlled PHY DSA has 2 kinds of drivers: 1. Those who call dsa_switch_suspend() and dsa_switch_resume() from their device PM ops: qca8k-8xxx, bcm_sf2, microchip ksz 2. Those who don't: all others. The above methods should be optional. For type 1, dsa_switch_suspend() calls dsa_user_suspend() -> phylink_stop(), and dsa_switch_resume() calls dsa_user_resume() -> phylink_start(). These seem good candidates for setting mac_managed_pm = true because that is essentially its definition [1], but that does not seem to be the biggest problem for now, and is not what this change focuses on. Talking strictly about the 2nd category of DSA drivers here (which do not have MAC managed PM, meaning that for their attached PHYs, mdio_bus_phy_suspend() and mdio_bus_phy_resume() should run in full), I have noticed that the following warning from mdio_bus_phy_resume() is triggered: WARN_ON(phydev->state != PHY_HALTED && phydev->state != PHY_READY && phydev->state != PHY_UP); because the PHY state machine is running. It's running as a result of a previous dsa_user_open() -> ... -> phylink_start() -> phy_start() having been initiated by the user. The previous mdio_bus_phy_suspend() was supposed to have called phy_stop_machine(), but it didn't. So this is why the PHY is in state PHY_NOLINK by the time mdio_bus_phy_resume() runs. mdio_bus_phy_suspend() did not call phy_stop_machine() because for phylink, the phydev->adjust_link function pointer is NULL. This seems a technicality introduced by commit fddd91016d16 ("phylib: fix PAL state machine restart on resume"). That commit was written before phylink existed, and was intended to avoid crashing with consumer drivers which don't use the PHY state machine - phylink always does, when using a PHY. But phylink itself has historically not been developed with suspend/resume in mind, and apparently not tested too much in that scenario, allowing this bug to exist unnoticed for so long. Plus, prior to the WARN_ON(), it would have likely been invisible. This issue is not in fact restricted to type 2 DSA drivers (according to the above ad-hoc classification), but can be extrapolated to any MAC driver with phylink and MDIO-bus-managed PHY PM ops. DSA is just where the issue was reported. Assuming mac_managed_pm is set correctly, a quick search indicates the following other drivers might be affected: $ grep -Zlr PHYLINK_NETDEV drivers/ | xargs -0 grep -L mac_managed_pm drivers/net/ethernet/atheros/ag71xx.c drivers/net/ethernet/microchip/sparx5/sparx5_main.c drivers/net/ethernet/microchip/lan966x/lan966x_main.c drivers/net/ethernet/freescale/dpaa2/dpaa2-mac.c drivers/net/ethernet/freescale/fs_enet/fs_enet-main.c drivers/net/ethernet/freescale/dpaa/dpaa_eth.c drivers/net/ethernet/freescale/ucc_geth.c drivers/net/ethernet/freescale/enetc/enetc_pf_common.c drivers/net/ethernet/marvell/mvpp2/mvpp2_main.c drivers/net/ethernet/marvell/mvneta.c drivers/net/ethernet/marvell/prestera/prestera_main.c drivers/net/ethernet/mediatek/mtk_eth_soc.c drivers/net/ethernet/altera/altera_tse_main.c drivers/net/ethernet/wangxun/txgbe/txgbe_phy.c drivers/net/ethernet/meta/fbnic/fbnic_phylink.c drivers/net/ethernet/tehuti/tn40_phy.c drivers/net/ethernet/mscc/ocelot_net.c Make the existing conditions dependent on the PHY device having a phydev->phy_link_change() implementation equal to the default phy_link_change() provided by phylib. Otherwise, we implicitly know that the phydev has the phylink-provided phylink_phy_change() callback, and when phylink is used, the PHY state machine always needs to be stopped/ started on the suspend/resume path. The code is structured as such that if phydev->phy_link_change() is absent, it is a matter of time until the kernel will crash - no need to further complicate the test. Thus, for the situation where the PM is not managed b ---truncated---
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
SSA-019113 · CSAF 2.0 · revision 2 · interimSiemens ProductCERTSSA-019113: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP V3.1.6
5 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0) >= V3.1.6
  • SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0) >= V3.1.6
Summary
In the Linux kernel, the following vulnerability has been resolved: net: phy: allow MDIO bus PM ops to start/stop state machine for phylink-controlled PHY DSA has 2 kinds of drivers: 1. Those who call dsa_switch_suspend() and dsa_switch_resume() from their device PM ops: qca8k-8xxx, bcm_sf2, microchip ksz 2. Those who don't: all others. The above methods should be optional. For type 1, dsa_switch_suspend() calls dsa_user_suspend() -> phylink_stop(), and dsa_switch_resume() calls dsa_user_resume() -> phylink_start(). These seem good candidates for setting mac_managed_pm = true because that is essentially its definition [1], but that does not seem to be the biggest problem for now, and is not what this change focuses on. Talking strictly about the 2nd category of DSA drivers here (which do not have MAC managed PM, meaning that for their attached PHYs, mdio_bus_phy_suspend() and mdio_bus_phy_resume() should run in full), I have noticed that the following warning from mdio_bus_phy_resume() is triggered: WARN_ON(phydev->state != PHY_HALTED && phydev->state != PHY_READY && phydev->state != PHY_UP); because the PHY state machine is running. It's running as a result of a previous dsa_user_open() -> ... -> phylink_start() -> phy_start() having been initiated by the user. The previous mdio_bus_phy_suspend() was supposed to have called phy_stop_machine(), but it didn't. So this is why the PHY is in state PHY_NOLINK by the time mdio_bus_phy_resume() runs. mdio_bus_phy_suspend() did not call phy_stop_machine() because for phylink, the phydev->adjust_link function pointer is NULL. This seems a technicality introduced by commit fddd91016d16 ("phylib: fix PAL state machine restart on resume"). That commit was written before phylink existed, and was intended to avoid crashing with consumer drivers which don't use the PHY state machine - phylink always does, when using a PHY. But phylink itself has historically not been developed with suspend/resume in mind, and apparently not tested too much in that scenario, allowing this bug to exist unnoticed for so long. Plus, prior to the WARN_ON(), it would have likely been invisible. This issue is not in fact restricted to type 2 DSA drivers (according to the above ad-hoc classification), but can be extrapolated to any MAC driver with phylink and MDIO-bus-managed PHY PM ops. DSA is just where the issue was reported. Assuming mac_managed_pm is set correctly, a quick search indicates the following other drivers might be affected: $ grep -Zlr PHYLINK_NETDEV drivers/ | xargs -0 grep -L mac_managed_pm drivers/net/ethernet/atheros/ag71xx.c drivers/net/ethernet/microchip/sparx5/sparx5_main.c drivers/net/ethernet/microchip/lan966x/lan966x_main.c drivers/net/ethernet/freescale/dpaa2/dpaa2-mac.c drivers/net/ethernet/freescale/fs_enet/fs_enet-main.c drivers/net/ethernet/freescale/dpaa/dpaa_eth.c drivers/net/ethernet/freescale/ucc_geth.c drivers/net/ethernet/freescale/enetc/enetc_pf_common.c drivers/net/ethernet/marvell/mvpp2/mvpp2_main.c drivers/net/ethernet/marvell/mvneta.c drivers/net/ethernet/marvell/prestera/prestera_main.c drivers/net/ethernet/mediatek/mtk_eth_soc.c drivers/net/ethernet/altera/altera_tse_main.c drivers/net/ethernet/wangxun/txgbe/txgbe_phy.c drivers/net/ethernet/meta/fbnic/fbnic_phylink.c drivers/net/ethernet/tehuti/tn40_phy.c drivers/net/ethernet/mscc/ocelot_net.c Make the existing conditions dependent on the PHY device having a phydev->phy_link_change() implementation equal to the default phy_link_change() provided by phylib. Otherwise, we implicitly know that the phydev has the phylink-provided phylink_phy_change() callback, and when phylink is used, the PHY state machine always needs to be stopped/ started on the suspend/resume path. The code is structured as such that if phydev->phy_link_change() is absent, it is a matter of time until the kernel will crash - no need to further complicate the test. Thus, for the situation where the PM is not managed b ---truncated---
Remediation
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
SSA-082556 · CSAF 2.0 · revision 7 · interimSiemens ProductCERTSSA-082556: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP V3.1.5
5 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0) >= V3.1.5
  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0) >= V3.1.5
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0) >= V3.1.5
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0) >= V3.1.5
  • SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0) >= V3.1.5
Summary
In the Linux kernel, the following vulnerability has been resolved: net: phy: allow MDIO bus PM ops to start/stop state machine for phylink-controlled PHY DSA has 2 kinds of drivers: 1. Those who call dsa_switch_suspend() and dsa_switch_resume() from their device PM ops: qca8k-8xxx, bcm_sf2, microchip ksz 2. Those who don't: all others. The above methods should be optional. For type 1, dsa_switch_suspend() calls dsa_user_suspend() -> phylink_stop(), and dsa_switch_resume() calls dsa_user_resume() -> phylink_start(). These seem good candidates for setting mac_managed_pm = true because that is essentially its definition [1], but that does not seem to be the biggest problem for now, and is not what this change focuses on. Talking strictly about the 2nd category of DSA drivers here (which do not have MAC managed PM, meaning that for their attached PHYs, mdio_bus_phy_suspend() and mdio_bus_phy_resume() should run in full), I have noticed that the following warning from mdio_bus_phy_resume() is triggered: WARN_ON(phydev->state != PHY_HALTED && phydev->state != PHY_READY && phydev->state != PHY_UP); because the PHY state machine is running. It's running as a result of a previous dsa_user_open() -> ... -> phylink_start() -> phy_start() having been initiated by the user. The previous mdio_bus_phy_suspend() was supposed to have called phy_stop_machine(), but it didn't. So this is why the PHY is in state PHY_NOLINK by the time mdio_bus_phy_resume() runs. mdio_bus_phy_suspend() did not call phy_stop_machine() because for phylink, the phydev->adjust_link function pointer is NULL. This seems a technicality introduced by commit fddd91016d16 ("phylib: fix PAL state machine restart on resume"). That commit was written before phylink existed, and was intended to avoid crashing with consumer drivers which don't use the PHY state machine - phylink always does, when using a PHY. But phylink itself has historically not been developed with suspend/resume in mind, and apparently not tested too much in that scenario, allowing this bug to exist unnoticed for so long. Plus, prior to the WARN_ON(), it would have likely been invisible. This issue is not in fact restricted to type 2 DSA drivers (according to the above ad-hoc classification), but can be extrapolated to any MAC driver with phylink and MDIO-bus-managed PHY PM ops. DSA is just where the issue was reported. Assuming mac_managed_pm is set correctly, a quick search indicates the following other drivers might be affected: $ grep -Zlr PHYLINK_NETDEV drivers/ | xargs -0 grep -L mac_managed_pm drivers/net/ethernet/atheros/ag71xx.c drivers/net/ethernet/microchip/sparx5/sparx5_main.c drivers/net/ethernet/microchip/lan966x/lan966x_main.c drivers/net/ethernet/freescale/dpaa2/dpaa2-mac.c drivers/net/ethernet/freescale/fs_enet/fs_enet-main.c drivers/net/ethernet/freescale/dpaa/dpaa_eth.c drivers/net/ethernet/freescale/ucc_geth.c drivers/net/ethernet/freescale/enetc/enetc_pf_common.c drivers/net/ethernet/marvell/mvpp2/mvpp2_main.c drivers/net/ethernet/marvell/mvneta.c drivers/net/ethernet/marvell/prestera/prestera_main.c drivers/net/ethernet/mediatek/mtk_eth_soc.c drivers/net/ethernet/altera/altera_tse_main.c drivers/net/ethernet/wangxun/txgbe/txgbe_phy.c drivers/net/ethernet/meta/fbnic/fbnic_phylink.c drivers/net/ethernet/tehuti/tn40_phy.c drivers/net/ethernet/mscc/ocelot_net.c Make the existing conditions dependent on the PHY device having a phydev->phy_link_change() implementation equal to the default phy_link_change() provided by phylib. Otherwise, we implicitly know that the phydev has the phylink-provided phylink_phy_change() callback, and when phylink is used, the PHY state machine always needs to be stopped/ started on the suspend/resume path. The code is structured as such that if phydev->phy_link_change() is absent, it is a matter of time until the kernel will crash - no need to further complicate the test. Thus, for the situation where the PM is not managed b ---truncated---
Remediation
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2025-15839

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: net: phy: allow MDIO bus PM ops to start/stop state machine for phylink-controlled PHY DSA has 2 kinds of drivers: 1. Those who call dsa_switch_suspend() and dsa_switch_resume() from their device PM ops: qca8k-8xxx, bcm_sf2, microchip ksz 2. Those who don't: all others. The above methods should be optional. For type 1, dsa_switch_suspend() calls dsa_user_suspend() -> phylink_stop(), and dsa_switch_resume() calls dsa_user_resume() -> phylink_start(). These seem good candidates for setting mac_managed_pm = true because that is essentially its definition [1], but that does not seem to be the biggest problem for now, and is not what this change focuses on. Talking strictly about the 2nd category of DSA drivers here (which do not have MAC managed PM, meaning that for their attached PHYs, mdio_bus_phy_suspend() and mdio_bus_phy_resume() should run in full), I have noticed that the following warning from mdio_bus_phy_resume() is triggered: WARN_ON(phydev->state != PHY_HALTED && phydev->state != PHY_READY && phydev->state != PHY_UP); because the PHY state machine is running. It's running as a result of a previous dsa_user_open() -> ... -> phylink_start() -> phy_start() having been initiated by the user. The previous mdio_bus_phy_suspend() was supposed to have called phy_stop_machine(), but it didn't. So this is why the PHY is in state PHY_NOLINK by the time mdio_bus_phy_resume() runs. mdio_bus_phy_suspend() did not call phy_stop_machine() because for phylink, the phydev->adjust_link function pointer is NULL. This seems a technicality introduced by commit fddd91016d16 ("phylib: fix PAL state machine restart on resume"). That commit was written before phylink existed, and was intended to avoid crashing with consumer drivers which don't use the PHY state machine - phylink always does, when using a PHY. But phylink itself has historically not been developed with suspend/resume in mind, and apparently not tested too much in that scenario, allowing this bug to exist unnoticed for so long. Plus, prior to the WARN_ON(), it would have likely been invisible. This issue is not in fact restricted to type 2 DSA drivers (according to the above ad-hoc classification), but can be extrapolated to any MAC driver with phylink and MDIO-bus-managed PHY PM ops. DSA is just where the issue was reported. Assuming mac_managed_pm is set correctly, a quick search indicates the following other drivers might be affected: $ grep -Zlr PHYLINK_NETDEV drivers/ | xargs -0 grep -L mac_managed_pm drivers/net/ethernet/atheros/ag71xx.c drivers/net/ethernet/microchip/sparx5/sparx5_main.c drivers/net/ethernet/microchip/lan966x/lan966x_main.c drivers/net/ethernet/freescale/dpaa2/dpaa2-mac.c drivers/net/ethernet/freescale/fs_enet/fs_enet-main.c drivers/net/ethernet/freescale/dpaa/dpaa_eth.c drivers/net/ethernet/freescale/ucc_geth.c drivers/net/ethernet/freescale/enetc/enetc_pf_common.c drivers/net/ethernet/marvell/mvpp2/mvpp2_main.c drivers/net/ethernet/marvell/mvneta.c drivers/net/ethernet/marvell/prestera/prestera_main.c drivers/net/ethernet/mediatek/mtk_eth_soc.c drivers/net/ethernet/altera/altera_tse_main.c drivers/net/ethernet/wangxun/txgbe/txgbe_phy.c drivers/net/ethernet/meta/fbnic/fbnic_phylink.c drivers/net/ethernet/tehuti/tn40_phy.c drivers/net/ethernet/mscc/ocelot_net.c Make the existing conditions dependent on the PHY device having a phydev->phy_link_change() implementation equal to the default phy_link_change() provided by phylib. Otherwise, we implicitly know that the phydev has the phylink-provided phylink_phy_change() callback, and when phylink is used, the PHY state machine always needs to be stopped/ started on the suspend/resume path. The code is structured as such that if phydev->phy_link_change() is absent, it is a matter of time until the kernel will crash - no need to further complicate the test. Thus, for the situation where the PM is not managed b ---truncated---

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
0.0
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 31 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: net: phy: allow MDIO bus PM ops to start/stop state machine for phylink-controlled PHY DSA has 2 kinds of drivers: 1. Those who call dsa_switch_suspend() and dsa_switch_resume() from their device PM ops: qca8k-8xxx, bcm_sf2, microchip ksz 2. Those who don't: all others. The above methods should be optional. For type 1, dsa_switch_suspend() calls dsa_user_suspend() -> phylink_stop(), and dsa_switch_resume() calls dsa_user_resume() -> phylink_start(). These seem good candidates for setting mac_managed_pm = true because that is essentially its definition [1], but that does not seem to be the biggest problem for now, and is not what this change focuses on. Talking strictly about the 2nd category of DSA drivers here (which do not have MAC managed PM, meaning that for their attached PHYs, mdio_bus_phy_suspend() and mdio_bus_phy_resume() should run in full), I have noticed that the following warning from mdio_bus_phy_resume() is triggered: WARN_ON(phydev->state != PHY_HALTED && phydev->state != PHY_READY && phydev->state != PHY_UP); because the PHY state machine is running. It's running as a result of a previous dsa_user_open() -> ... -> phylink_start() -> phy_start() having been initiated by the user. The previous mdio_bus_phy_suspend() was supposed to have called phy_stop_machine(), but it didn't. So this is why the PHY is in state PHY_NOLINK by the time mdio_bus_phy_resume() runs. mdio_bus_phy_suspend() did not call phy_stop_machine() because for phylink, the phydev->adjust_link function pointer is NULL. This seems a technicality introduced by commit fddd91016d16 ("phylib: fix PAL state machine restart on resume"). That commit was written before phylink existed, and was intended to avoid crashing with consumer drivers which don't use the PHY state machine - phylink always does, when using a PHY. But phylink itself has historically not been developed with suspend/resume in mind, and apparently not tested too much in that scenario, allowing this bug to exist unnoticed for so long. Plus, prior to the WARN_ON(), it would have likely been invisible. This issue is not in fact restricted to type 2 DSA drivers (according to the above ad-hoc classification), but can be extrapolated to any MAC driver with phylink and MDIO-bus-managed PHY PM ops. DSA is just where the issue was reported. Assuming mac_managed_pm is set correctly, a quick search indicates the following other drivers might be affected: $ grep -Zlr PHYLINK_NETDEV drivers/ | xargs -0 grep -L mac_managed_pm drivers/net/ethernet/atheros/ag71xx.c drivers/net/ethernet/microchip/sparx5/sparx5_main.c drivers/net/ethernet/microchip/lan966x/lan966x_main.c drivers/net/ethernet/freescale/dpaa2/dpaa2-mac.c drivers/net/ethernet/freescale/fs_enet/fs_enet-main.c drivers/net/ethernet/freescale/dpaa/dpaa_eth.c drivers/net/ethernet/freescale/ucc_geth.c drivers/net/ethernet/freescale/enetc/enetc_pf_common.c drivers/net/ethernet/marvell/mvpp2/mvpp2_main.c drivers/net/ethernet/marvell/mvneta.c drivers/net/ethernet/marvell/prestera/prestera_main.c drivers/net/ethernet/mediatek/mtk_eth_soc.c drivers/net/ethernet/altera/altera_tse_main.c drivers/net/ethernet/wangxun/txgbe/txgbe_phy.c drivers/net/ethernet/meta/fbnic/fbnic_phylink.c drivers/net/ethernet/tehuti/tn40_phy.c drivers/net/ethernet/mscc/ocelot_net.c Make the existing conditions dependent on the PHY device having a phydev->phy_link_change() implementation equal to the default phy_link_change() provided by phylib. Otherwise, we implicitly know that the phydev has the phylink-provided phylink_phy_change() callback, and when phylink is used, the PHY state machine always needs to be stopped/ started on the suspend/resume path. The code is structured as such that if phydev->phy_link_change() is absent, it is a matter of time until the kernel will crash - no need to further complicate the test. Thus, for the situation where the PM is not managed b ---truncated---

What

In the Linux kernel, the following vulnerability has been resolved: net: phy: allow MDIO bus PM ops to start/stop state machine for phylink-controlled PHY DSA has 2 kinds of drivers: 1. Those who call dsa_switch_suspend() and dsa_switch_resume() from their device PM ops: qca8k-8xxx, bcm_sf2, microchip ksz 2. Those who don't: all others. The above methods should be optional. For type 1, dsa_switch_suspend() calls dsa_user_suspend() -> phylink_stop(), and dsa_switch_resume() calls dsa_user_resume() -> phylink_start(). These seem good candidates for setting mac_managed_pm = true because that is essentially its definition [1], but that does not seem to be the biggest problem for now, and is not what this change focuses on. Talking strictly about the 2nd category of DSA drivers here (which do not have MAC managed PM, meaning that for their attached PHYs, mdio_bus_phy_suspend() and mdio_bus_phy_resume() should run in full), I have noticed that the following warning from mdio_bus_phy_resume() is triggered: WARN_ON(phydev->state != PHY_HALTED && phydev->state != PHY_READY && phydev->state != PHY_UP); because the PHY state machine is running. It's running as a result of a previous dsa_user_open() -> ... -> phylink_start() -> phy_start() having been initiated by the user. The previous mdio_bus_phy_suspend() was supposed to have called phy_stop_machine(), but it didn't. So this is why the PHY is in state PHY_NOLINK by the time mdio_bus_phy_resume() runs. mdio_bus_phy_suspend() did not call phy_stop_machine() because for phylink, the phydev->adjust_link function pointer is NULL. This seems a technicality introduced by commit fddd91016d16 ("phylib: fix PAL state machine restart on resume"). That commit was written before phylink existed, and was intended to avoid crashing with consumer drivers which don't use the PHY state machine - phylink always does, when using a PHY. But phylink itself has historically not been developed with suspend/resume in mind, and apparently not tested too much in that scenario, allowing this bug to exist unnoticed for so long. Plus, prior to the WARN_ON(), it would have likely been invisible. This issue is not in fact restricted to type 2 DSA drivers (according to the above ad-hoc classification), but can be extrapolated to any MAC driver with phylink and MDIO-bus-managed PHY PM ops. DSA is just where the issue was reported. Assuming mac_managed_pm is set correctly, a quick search indicates the following other drivers might be affected: $ grep -Zlr PHYLINK_NETDEV drivers/ | xargs -0 grep -L mac_managed_pm drivers/net/ethernet/atheros/ag71xx.c drivers/net/ethernet/microchip/sparx5/sparx5_main.c drivers/net/ethernet/microchip/lan966x/lan966x_main.c drivers/net/ethernet/freescale/dpaa2/dpaa2-mac.c drivers/net/ethernet/freescale/fs_enet/fs_enet-main.c drivers/net/ethernet/freescale/dpaa/dpaa_eth.c drivers/net/ethernet/freescale/ucc_geth.c drivers/net/ethernet/freescale/enetc/enetc_pf_common.c drivers/net/ethernet/marvell/mvpp2/mvpp2_main.c drivers/net/ethernet/marvell/mvneta.c drivers/net/ethernet/marvell/prestera/prestera_main.c drivers/net/ethernet/mediatek/mtk_eth_soc.c drivers/net/ethernet/altera/altera_tse_main.c drivers/net/ethernet/wangxun/txgbe/txgbe_phy.c drivers/net/ethernet/meta/fbnic/fbnic_phylink.c drivers/net/ethernet/tehuti/tn40_phy.c drivers/net/ethernet/mscc/ocelot_net.c Make the existing conditions dependent on the PHY device having a phydev->phy_link_change() implementation equal to the default phy_link_change() provided by phylib. Otherwise, we implicitly know that the phydev has the phylink-provided phylink_phy_change() callback, and when phylink is used, the PHY state machine always needs to be stopped/ started on the suspend/resume path. The code is structured as such that if phydev->phy_link_change() is absent, it is a matter of time until the kernel will crash - no need to further complicate the test. Thus, for the situation where the PM is not managed b ---truncated---

Why

The product dereferences a pointer that it expects to be valid but is NULL.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may disrupt the affected service.

What

In the Linux kernel, the following vulnerability has been resolved: net: phy: allow MDIO bus PM ops to start/stop state machine for phylink-controlled PHY DSA has 2 kinds of drivers: 1. Those who call dsa_switch_suspend() and dsa_switch_resume() from their device PM ops: qca8k-8xxx, bcm_sf2, microchip ksz 2. Those who don't: all others. The above methods should be optional. For type 1, dsa_switch_suspend() calls dsa_user_suspend() -> phylink_stop(), and dsa_switch_resume() calls dsa_user_resume() -> phylink_start(). These seem good candidates for setting mac_managed_pm = true because that is essentially its definition [1], but that does not seem to be the biggest problem for now, and is not what this change focuses on. Talking strictly about the 2nd category of DSA drivers here (which do not have MAC managed PM, meaning that for their attached PHYs, mdio_bus_phy_suspend() and mdio_bus_phy_resume() should run in full), I have noticed that the following warning from mdio_bus_phy_resume() is triggered: WARN_ON(phydev->state != PHY_HALTED && phydev->state != PHY_READY && phydev->state != PHY_UP); because the PHY state machine is running. It's running as a result of a previous dsa_user_open() -> ... -> phylink_start() -> phy_start() having been initiated by the user. The previous mdio_bus_phy_suspend() was supposed to have called phy_stop_machine(), but it didn't. So this is why the PHY is in state PHY_NOLINK by the time mdio_bus_phy_resume() runs. mdio_bus_phy_suspend() did not call phy_stop_machine() because for phylink, the phydev->adjust_link function pointer is NULL. This seems a technicality introduced by commit fddd91016d16 ("phylib: fix PAL state machine restart on resume"). That commit was written before phylink existed, and was intended to avoid crashing with consumer drivers which don't use the PHY state machine - phylink always does, when using a PHY. But phylink itself has historically not been developed with suspend/resume in mind, and apparently not tested too much in that scenario, allowing this bug to exist unnoticed for so long. Plus, prior to the WARN_ON(), it would have likely been invisible. This issue is not in fact restricted to type 2 DSA drivers (according to the above ad-hoc classification), but can be extrapolated to any MAC driver with phylink and MDIO-bus-managed PHY PM ops. DSA is just where the issue was reported. Assuming mac_managed_pm is set correctly, a quick search indicates the following other drivers might be affected: $ grep -Zlr PHYLINK_NETDEV drivers/ | xargs -0 grep -L mac_managed_pm drivers/net/ethernet/atheros/ag71xx.c drivers/net/ethernet/microchip/sparx5/sparx5_main.c drivers/net/ethernet/microchip/lan966x/lan966x_main.c drivers/net/ethernet/freescale/dpaa2/dpaa2-mac.c drivers/net/ethernet/freescale/fs_enet/fs_enet-main.c drivers/net/ethernet/freescale/dpaa/dpaa_eth.c drivers/net/ethernet/freescale/ucc_geth.c drivers/net/ethernet/freescale/enetc/enetc_pf_common.c drivers/net/ethernet/marvell/mvpp2/mvpp2_main.c drivers/net/ethernet/marvell/mvneta.c drivers/net/ethernet/marvell/prestera/prestera_main.c drivers/net/ethernet/mediatek/mtk_eth_soc.c drivers/net/ethernet/altera/altera_tse_main.c drivers/net/ethernet/wangxun/txgbe/txgbe_phy.c drivers/net/ethernet/meta/fbnic/fbnic_phylink.c drivers/net/ethernet/tehuti/tn40_phy.c drivers/net/ethernet/mscc/ocelot_net.c Make the existing conditions dependent on the PHY device having a phydev->phy_link_change() implementation equal to the default phy_link_change() provided by phylib. Otherwise, we implicitly know that the phydev has the phylink-provided phylink_phy_change() callback, and when phylink is used, the PHY state machine always needs to be stopped/ started on the suspend/resume path. The code is structured as such that if phydev->phy_link_change() is absent, it is a matter of time until the kernel will crash - no need to further complicate the test. Thus, for the situation where the PM is not managed b ---truncated---

Why

The product dereferences a pointer that it expects to be valid but is NULL.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may disrupt the affected service.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → NULL Pointer Dereference → disrupt the affected service
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-476 ↗

CWE-476: NULL Pointer Dereference. The product dereferences a pointer that it expects to be valid but is NULL.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
Denial of serviceCWE-476
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2025-15839Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: net: phy: allow MDIO bus PM ops to start/stop state machine for phylink-controlled PHY DSA has 2 kinds of drivers: 1. Those who call dsa_switch_suspend() and dsa_switch_resume() from their device PM ops: qca8k-8xxx, bcm_sf2, microchip ksz 2. Those who don't: all others. The above methods should be optional. For type 1, dsa_switch_suspend() calls dsa_user_suspend() -> phylink_stop(), and dsa_switch_resume() calls dsa_user_resume() -> phylink_start(). These seem good candidates for setting mac_managed_pm = true because that is essentially its definition [1], but that does not seem to be the biggest problem for now, and is not what this change focuses on. Talking strictly about the 2nd category of DSA drivers here (which do not have MAC managed PM, meaning that for their attached PHYs, mdio_bus_phy_suspend() and mdio_bus_phy_resume() should run in full), I have noticed that the following warning from mdio_bus_phy_resume() is triggered: WARN_ON(phydev->state != PHY_HALTED && phydev->state != PHY_READY && phydev->state != PHY_UP); because the PHY state machine is running. It's running as a result of a previous dsa_user_open() -> ... -> phylink_start() -> phy_start() having been initiated by the user. The previous mdio_bus_phy_suspend() was supposed to have called phy_stop_machine(), but it didn't. So this is why the PHY is in state PHY_NOLINK by the time mdio_bus_phy_resume() runs. mdio_bus_phy_suspend() did not call phy_stop_machine() because for phylink, the phydev->adjust_link function pointer is NULL. This seems a technicality introduced by commit fddd91016d16 ("phylib: fix PAL state machine restart on resume"). That commit was written before phylink existed, and was intended to avoid crashing with consumer drivers which don't use the PHY state machine - phylink always does, when using a PHY. But phylink itself has historically not been developed with suspend/resume in mind, and apparently not tested too much in that scenario, allowing this bug to exist unnoticed for so long. Plus, prior to the WARN_ON(), it would have likely been invisible. This issue is not in fact restricted to type 2 DSA drivers (according to the above ad-hoc classification), but can be extrapolated to any MAC driver with phylink and MDIO-bus-managed PHY PM ops. DSA is just where the issue was reported. Assuming mac_managed_pm is set correctly, a quick search indicates the following other drivers might be affected: $ grep -Zlr PHYLINK_NETDEV drivers/ | xargs -0 grep -L mac_managed_pm drivers/net/ethernet/atheros/ag71xx.c drivers/net/ethernet/microchip/sparx5/sparx5_main.c drivers/net/ethernet/microchip/lan966x/lan966x_main.c drivers/net/ethernet/freescale/dpaa2/dpaa2-mac.c drivers/net/ethernet/freescale/fs_enet/fs_enet-main.c drivers/net/ethernet/freescale/dpaa/dpaa_eth.c drivers/net/ethernet/freescale/ucc_geth.c drivers/net/ethernet/freescale/enetc/enetc_pf_common.c drivers/net/ethernet/marvell/mvpp2/mvpp2_main.c drivers/net/ethernet/marvell/mvneta.c drivers/net/ethernet/marvell/prestera/prestera_main.c drivers/net/ethernet/mediatek/mtk_eth_soc.c drivers/net/ethernet/altera/altera_tse_main.c drivers/net/ethernet/wangxun/txgbe/txgbe_phy.c drivers/net/ethernet/meta/fbnic/fbnic_phylink.c drivers/net/ethernet/tehuti/tn40_phy.c drivers/net/ethernet/mscc/ocelot_net.c Make the existing conditions dependent on the PHY device having a phydev->phy_link_change() implementation equal to the default phy_link_change() provided by phylib. Otherwise, we implicitly know that the phydev has the phylink-provided phylink_phy_change() callback, and when phylink is used, the PHY state machine always needs to be stopped/ started on the suspend/resume path. The code is structured as such that if phydev->phy_link_change() is absent, it is a matter of time until the kernel will crash - no need to further complicate the test. Thus, for the situation where the PM is not managed b ---truncated---

Official EUVD record ↗
BSI · German · WID-SEC-2025-1114Linux Kernel: Mehrere Schwachstellen

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff und weitere nicht spezifizierte Angriffe durchzuführen.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0880Multiples vulnérabilités dans les produits Siemens

25-21731, CVE-2025-21745, CVE-2025-21758, CVE-2025-21760, CVE-2025-21764, CVE-2025-21765, CVE-2025-21780, CVE-2025-21795, CVE-2025-21796, CVE-2025-21802, CVE-2025-21814, CVE-2025-21846, CVE-2025-21853, CVE-2025-21861, CVE-2025-21864, CVE-2025-21867, CVE-2025-21875, CVE-2025-21887, CVE-2025-21913, CVE-2025-21919, CVE-2025-21925, CVE-2025-21926, CVE-2025-21938, CVE-2025-21959, CVE-2025-21999, CVE-2025-22005, CVE-2025-22015, CVE-2025-22055, CVE-2025-22056, CVE-2025-22060, CVE-2025-22083, CVE-2025-22090, CVE-2025-22095, CVE-2025-22107, CVE-2025-22111, CVE-2025-22121, CVE-2025-23136, CVE-2025-23143, CVE-2025-37785, CVE-2025-37909, CVE-2025-37917, CVE-2025-37945, CVE-2025-37959, CVE-2025-37964, CVE-2025-37972, CVE-2025-37980, CVE-2025-38125, CVE-2025-38162, CVE-2025-38192, CVE-2025-38201, CVE-2025-38232, CVE-2025-38322, CVE-2025-38591, CVE-2025-38614, CVE-2025-38681, CVE-2025-38704, CVE-2025-38721, CVE-2025-38725, CVE-2025-38727, CVE-2025-38732, CVE-2025-38736, CVE-2025-39681, CVE-2025-39691, CVE-2025-39721, CVE-2025-39748, CVE-2025-39756, CVE-2025-39764, CVE-2025-39770, CVE-2025-39773, CVE-2025-39782, CVE-2025-39795, CVE-2025-39826, CVE-2025-39827, CVE-2025-39845, CVE-2025-39866, CVE-2025-39871, CVE-2025-39931, CVE-2025-39953, CVE-2025-39955, CVE-2025-39964, CVE-2025-39977, CVE-2025-39978, CVE-2025

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0547Multiples vulnérabilités dans le noyau Linux de Debian LTS

d?id=CVE-2023-53510 Référence CVE CVE-2023-53545 https://www.cve.org/CVERecord?id=CVE-2023-53545 Référence CVE CVE-2024-47736 https://www.cve.org/CVERecord?id=CVE-2024-47736 Référence CVE CVE-2024-47809 https://www.cve.org/CVERecord?id=CVE-2024-47809 Référence CVE CVE-2024-49998 https://www.cve.org/CVERecord?id=CVE-2024-49998 Référence CVE CVE-2024-50298 https://www.cve.org/CVERecord?id=CVE-2024-50298 Référence CVE CVE-2024-56719 https://www.cve.org/CVERecord?id=CVE-2024-56719 Référence CVE CVE-2025-21676 https://www.cve.org/CVERecord?id=CVE-2025-21676 Référence CVE CVE-2025-21682 https://www.cve.org/CVERecord?id=CVE-2025-21682 Référence CVE CVE-2025-37945 https://www.cve.org/CVERecord?id=CVE-2025-37945 Référence CVE CVE-2025-37980 https://www.cve.org/CVERecord?id=CVE-2025-37980 Référence CVE CVE-2025-38105 https://www.cve.org/CVERecord?id=CVE-2025-38105 Référence CVE CVE-2025-38162 https://www.cve.org/CVERecord?id=CVE-2025-38162 Référence CVE CVE-2025-38192 https://www.cve.org/CVERecord?id=CVE-2025-38192 Référence CVE CVE-2025-38250 https://www.cve.org/CVERecord?id=CVE-2025-38250 Référence CVE CVE-2025-38303 https://www.cve.org/CVERecord?id=CVE-2025-38303 Référence CVE CVE-2025-38436 https://www.cve.org/CVERecord?id=CVE-2025-38436 Référence CVE CVE-2025-38626 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0548Multiples vulnérabilités dans le noyau Linux de Debian

d?id=CVE-2024-47809 Référence CVE CVE-2024-49998 https://www.cve.org/CVERecord?id=CVE-2024-49998 Référence CVE CVE-2024-50298 https://www.cve.org/CVERecord?id=CVE-2024-50298 Référence CVE CVE-2024-56719 https://www.cve.org/CVERecord?id=CVE-2024-56719 Référence CVE CVE-2025-21676 https://www.cve.org/CVERecord?id=CVE-2025-21676 Référence CVE CVE-2025-21682 https://www.cve.org/CVERecord?id=CVE-2025-21682 Référence CVE CVE-2025-21709 https://www.cve.org/CVERecord?id=CVE-2025-21709 Référence CVE CVE-2025-22116 https://www.cve.org/CVERecord?id=CVE-2025-22116 Référence CVE CVE-2025-22117 https://www.cve.org/CVERecord?id=CVE-2025-22117 Référence CVE CVE-2025-37945 https://www.cve.org/CVERecord?id=CVE-2025-37945 Référence CVE CVE-2025-37980 https://www.cve.org/CVERecord?id=CVE-2025-37980 Référence CVE CVE-2025-38105 https://www.cve.org/CVERecord?id=CVE-2025-38105 Référence CVE CVE-2025-38162 https://www.cve.org/CVERecord?id=CVE-2025-38162 Référence CVE CVE-2025-38192 https://www.cve.org/CVERecord?id=CVE-2025-38192 Référence CVE CVE-2025-38250 https://www.cve.org/CVERecord?id=CVE-2025-38250 Référence CVE CVE-2025-38303 https://www.cve.org/CVERecord?id=CVE-2025-38303 Référence CVE CVE-2025-38426 https://www.cve.org/CVERecord?id=CVE-2025-38426 Référence CVE CVE-2025-38436 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0326Multiples vulnérabilités dans les produits VMware

d?id=CVE-2025-37907 Référence CVE CVE-2025-37920 https://www.cve.org/CVERecord?id=CVE-2025-37920 Référence CVE CVE-2025-37924 https://www.cve.org/CVERecord?id=CVE-2025-37924 Référence CVE CVE-2025-37926 https://www.cve.org/CVERecord?id=CVE-2025-37926 Référence CVE CVE-2025-37928 https://www.cve.org/CVERecord?id=CVE-2025-37928 Référence CVE CVE-2025-37931 https://www.cve.org/CVERecord?id=CVE-2025-37931 Référence CVE CVE-2025-37938 https://www.cve.org/CVERecord?id=CVE-2025-37938 Référence CVE CVE-2025-37943 https://www.cve.org/CVERecord?id=CVE-2025-37943 Référence CVE CVE-2025-37944 https://www.cve.org/CVERecord?id=CVE-2025-37944 Référence CVE CVE-2025-37945 https://www.cve.org/CVERecord?id=CVE-2025-37945 Référence CVE CVE-2025-37947 https://www.cve.org/CVERecord?id=CVE-2025-37947 Référence CVE CVE-2025-37951 https://www.cve.org/CVERecord?id=CVE-2025-37951 Référence CVE CVE-2025-37952 https://www.cve.org/CVERecord?id=CVE-2025-37952 Référence CVE CVE-2025-37954 https://www.cve.org/CVERecord?id=CVE-2025-37954 Référence CVE CVE-2025-37956 https://www.cve.org/CVERecord?id=CVE-2025-37956 Référence CVE CVE-2025-37957 https://www.cve.org/CVERecord?id=CVE-2025-37957 Référence CVE CVE-2025-37959 https://www.cve.org/CVERecord?id=CVE-2025-37959 Référence CVE CVE-2025-37961 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0316Multiples vulnérabilités dans les produits VMware

d?id=CVE-2025-37907 Référence CVE CVE-2025-37920 https://www.cve.org/CVERecord?id=CVE-2025-37920 Référence CVE CVE-2025-37924 https://www.cve.org/CVERecord?id=CVE-2025-37924 Référence CVE CVE-2025-37926 https://www.cve.org/CVERecord?id=CVE-2025-37926 Référence CVE CVE-2025-37928 https://www.cve.org/CVERecord?id=CVE-2025-37928 Référence CVE CVE-2025-37931 https://www.cve.org/CVERecord?id=CVE-2025-37931 Référence CVE CVE-2025-37938 https://www.cve.org/CVERecord?id=CVE-2025-37938 Référence CVE CVE-2025-37943 https://www.cve.org/CVERecord?id=CVE-2025-37943 Référence CVE CVE-2025-37944 https://www.cve.org/CVERecord?id=CVE-2025-37944 Référence CVE CVE-2025-37945 https://www.cve.org/CVERecord?id=CVE-2025-37945 Référence CVE CVE-2025-37947 https://www.cve.org/CVERecord?id=CVE-2025-37947 Référence CVE CVE-2025-37951 https://www.cve.org/CVERecord?id=CVE-2025-37951 Référence CVE CVE-2025-37952 https://www.cve.org/CVERecord?id=CVE-2025-37952 Référence CVE CVE-2025-37954 https://www.cve.org/CVERecord?id=CVE-2025-37954 Référence CVE CVE-2025-37956 https://www.cve.org/CVERecord?id=CVE-2025-37956 Référence CVE CVE-2025-37957 https://www.cve.org/CVERecord?id=CVE-2025-37957 Référence CVE CVE-2025-37959 https://www.cve.org/CVERecord?id=CVE-2025-37959 Référence CVE CVE-2025-37961 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0246Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2025-37930 Référence CVE CVE-2025-37931 https://www.cve.org/CVERecord?id=CVE-2025-37931 Référence CVE CVE-2025-37933 https://www.cve.org/CVERecord?id=CVE-2025-37933 Référence CVE CVE-2025-37935 https://www.cve.org/CVERecord?id=CVE-2025-37935 Référence CVE CVE-2025-37936 https://www.cve.org/CVERecord?id=CVE-2025-37936 Référence CVE CVE-2025-37938 https://www.cve.org/CVERecord?id=CVE-2025-37938 Référence CVE CVE-2025-37940 https://www.cve.org/CVERecord?id=CVE-2025-37940 Référence CVE CVE-2025-37943 https://www.cve.org/CVERecord?id=CVE-2025-37943 Référence CVE CVE-2025-37944 https://www.cve.org/CVERecord?id=CVE-2025-37944 Référence CVE CVE-2025-37945 https://www.cve.org/CVERecord?id=CVE-2025-37945 Référence CVE CVE-2025-37947 https://www.cve.org/CVERecord?id=CVE-2025-37947 Référence CVE CVE-2025-37948 https://www.cve.org/CVERecord?id=CVE-2025-37948 Référence CVE CVE-2025-37949 https://www.cve.org/CVERecord?id=CVE-2025-37949 Référence CVE CVE-2025-37951 https://www.cve.org/CVERecord?id=CVE-2025-37951 Référence CVE CVE-2025-37952 https://www.cve.org/CVERecord?id=CVE-2025-37952 Référence CVE CVE-2025-37956 https://www.cve.org/CVERecord?id=CVE-2025-37956 Référence CVE CVE-2025-37957 https://www.cve.org/CVERecord?id=CVE-2025-37957 Référence CVE CVE-2025-37959 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0227Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2025-37930 Référence CVE CVE-2025-37931 https://www.cve.org/CVERecord?id=CVE-2025-37931 Référence CVE CVE-2025-37933 https://www.cve.org/CVERecord?id=CVE-2025-37933 Référence CVE CVE-2025-37935 https://www.cve.org/CVERecord?id=CVE-2025-37935 Référence CVE CVE-2025-37936 https://www.cve.org/CVERecord?id=CVE-2025-37936 Référence CVE CVE-2025-37938 https://www.cve.org/CVERecord?id=CVE-2025-37938 Référence CVE CVE-2025-37940 https://www.cve.org/CVERecord?id=CVE-2025-37940 Référence CVE CVE-2025-37943 https://www.cve.org/CVERecord?id=CVE-2025-37943 Référence CVE CVE-2025-37944 https://www.cve.org/CVERecord?id=CVE-2025-37944 Référence CVE CVE-2025-37945 https://www.cve.org/CVERecord?id=CVE-2025-37945 Référence CVE CVE-2025-37947 https://www.cve.org/CVERecord?id=CVE-2025-37947 Référence CVE CVE-2025-37948 https://www.cve.org/CVERecord?id=CVE-2025-37948 Référence CVE CVE-2025-37949 https://www.cve.org/CVERecord?id=CVE-2025-37949 Référence CVE CVE-2025-37951 https://www.cve.org/CVERecord?id=CVE-2025-37951 Référence CVE CVE-2025-37952 https://www.cve.org/CVERecord?id=CVE-2025-37952 Référence CVE CVE-2025-37954 https://www.cve.org/CVERecord?id=CVE-2025-37954 Référence CVE CVE-2025-37956 https://www.cve.org/CVERecord?id=CVE-2025-37956 Référence CVE CVE-2025-37957 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0218Multiples vulnérabilités dans les produits VMware

d?id=CVE-2025-37930 Référence CVE CVE-2025-37931 https://www.cve.org/CVERecord?id=CVE-2025-37931 Référence CVE CVE-2025-37933 https://www.cve.org/CVERecord?id=CVE-2025-37933 Référence CVE CVE-2025-37935 https://www.cve.org/CVERecord?id=CVE-2025-37935 Référence CVE CVE-2025-37936 https://www.cve.org/CVERecord?id=CVE-2025-37936 Référence CVE CVE-2025-37938 https://www.cve.org/CVERecord?id=CVE-2025-37938 Référence CVE CVE-2025-37940 https://www.cve.org/CVERecord?id=CVE-2025-37940 Référence CVE CVE-2025-37943 https://www.cve.org/CVERecord?id=CVE-2025-37943 Référence CVE CVE-2025-37944 https://www.cve.org/CVERecord?id=CVE-2025-37944 Référence CVE CVE-2025-37945 https://www.cve.org/CVERecord?id=CVE-2025-37945 Référence CVE CVE-2025-37947 https://www.cve.org/CVERecord?id=CVE-2025-37947 Référence CVE CVE-2025-37948 https://www.cve.org/CVERecord?id=CVE-2025-37948 Référence CVE CVE-2025-37949 https://www.cve.org/CVERecord?id=CVE-2025-37949 Référence CVE CVE-2025-37951 https://www.cve.org/CVERecord?id=CVE-2025-37951 Référence CVE CVE-2025-37952 https://www.cve.org/CVERecord?id=CVE-2025-37952 Référence CVE CVE-2025-37954 https://www.cve.org/CVERecord?id=CVE-2025-37954 Référence CVE CVE-2025-37956 https://www.cve.org/CVERecord?id=CVE-2025-37956 Référence CVE CVE-2025-37957 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0194Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2025-37930 Référence CVE CVE-2025-37931 https://www.cve.org/CVERecord?id=CVE-2025-37931 Référence CVE CVE-2025-37933 https://www.cve.org/CVERecord?id=CVE-2025-37933 Référence CVE CVE-2025-37935 https://www.cve.org/CVERecord?id=CVE-2025-37935 Référence CVE CVE-2025-37936 https://www.cve.org/CVERecord?id=CVE-2025-37936 Référence CVE CVE-2025-37938 https://www.cve.org/CVERecord?id=CVE-2025-37938 Référence CVE CVE-2025-37940 https://www.cve.org/CVERecord?id=CVE-2025-37940 Référence CVE CVE-2025-37943 https://www.cve.org/CVERecord?id=CVE-2025-37943 Référence CVE CVE-2025-37944 https://www.cve.org/CVERecord?id=CVE-2025-37944 Référence CVE CVE-2025-37945 https://www.cve.org/CVERecord?id=CVE-2025-37945 Référence CVE CVE-2025-37947 https://www.cve.org/CVERecord?id=CVE-2025-37947 Référence CVE CVE-2025-37948 https://www.cve.org/CVERecord?id=CVE-2025-37948 Référence CVE CVE-2025-37949 https://www.cve.org/CVERecord?id=CVE-2025-37949 Référence CVE CVE-2025-37951 https://www.cve.org/CVERecord?id=CVE-2025-37951 Référence CVE CVE-2025-37952 https://www.cve.org/CVERecord?id=CVE-2025-37952 Référence CVE CVE-2025-37954 https://www.cve.org/CVERecord?id=CVE-2025-37954 Référence CVE CVE-2025-37956 https://www.cve.org/CVERecord?id=CVE-2025-37956 Référence CVE CVE-2025-37957 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0169Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2025-37930 Référence CVE CVE-2025-37931 https://www.cve.org/CVERecord?id=CVE-2025-37931 Référence CVE CVE-2025-37933 https://www.cve.org/CVERecord?id=CVE-2025-37933 Référence CVE CVE-2025-37935 https://www.cve.org/CVERecord?id=CVE-2025-37935 Référence CVE CVE-2025-37936 https://www.cve.org/CVERecord?id=CVE-2025-37936 Référence CVE CVE-2025-37938 https://www.cve.org/CVERecord?id=CVE-2025-37938 Référence CVE CVE-2025-37940 https://www.cve.org/CVERecord?id=CVE-2025-37940 Référence CVE CVE-2025-37943 https://www.cve.org/CVERecord?id=CVE-2025-37943 Référence CVE CVE-2025-37944 https://www.cve.org/CVERecord?id=CVE-2025-37944 Référence CVE CVE-2025-37945 https://www.cve.org/CVERecord?id=CVE-2025-37945 Référence CVE CVE-2025-37947 https://www.cve.org/CVERecord?id=CVE-2025-37947 Référence CVE CVE-2025-37948 https://www.cve.org/CVERecord?id=CVE-2025-37948 Référence CVE CVE-2025-37949 https://www.cve.org/CVERecord?id=CVE-2025-37949 Référence CVE CVE-2025-37951 https://www.cve.org/CVERecord?id=CVE-2025-37951 Référence CVE CVE-2025-37952 https://www.cve.org/CVERecord?id=CVE-2025-37952 Référence CVE CVE-2025-37954 https://www.cve.org/CVERecord?id=CVE-2025-37954 Référence CVE CVE-2025-37956 https://www.cve.org/CVERecord?id=CVE-2025-37956 Référence CVE CVE-2025-37957 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0723Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2025-37930 Référence CVE CVE-2025-37931 https://www.cve.org/CVERecord?id=CVE-2025-37931 Référence CVE CVE-2025-37932 https://www.cve.org/CVERecord?id=CVE-2025-37932 Référence CVE CVE-2025-37933 https://www.cve.org/CVERecord?id=CVE-2025-37933 Référence CVE CVE-2025-37936 https://www.cve.org/CVERecord?id=CVE-2025-37936 Référence CVE CVE-2025-37937 https://www.cve.org/CVERecord?id=CVE-2025-37937 Référence CVE CVE-2025-37938 https://www.cve.org/CVERecord?id=CVE-2025-37938 Référence CVE CVE-2025-37943 https://www.cve.org/CVERecord?id=CVE-2025-37943 Référence CVE CVE-2025-37944 https://www.cve.org/CVERecord?id=CVE-2025-37944 Référence CVE CVE-2025-37945 https://www.cve.org/CVERecord?id=CVE-2025-37945 Référence CVE CVE-2025-37946 https://www.cve.org/CVERecord?id=CVE-2025-37946 Référence CVE CVE-2025-37948 https://www.cve.org/CVERecord?id=CVE-2025-37948 Référence CVE CVE-2025-37951 https://www.cve.org/CVERecord?id=CVE-2025-37951 Référence CVE CVE-2025-37953 https://www.cve.org/CVERecord?id=CVE-2025-37953 Référence CVE CVE-2025-37954 https://www.cve.org/CVERecord?id=CVE-2025-37954 Référence CVE CVE-2025-37959 https://www.cve.org/CVERecord?id=CVE-2025-37959 Référence CVE CVE-2025-37961 https://www.cve.org/CVERecord?id=CVE-2025-37961 Référence CVE CVE-2025-37963 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0649Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2025-37909 Référence CVE CVE-2025-37917 https://www.cve.org/CVERecord?id=CVE-2025-37917 Référence CVE CVE-2025-37921 https://www.cve.org/CVERecord?id=CVE-2025-37921 Référence CVE CVE-2025-37923 https://www.cve.org/CVERecord?id=CVE-2025-37923 Référence CVE CVE-2025-37927 https://www.cve.org/CVERecord?id=CVE-2025-37927 Référence CVE CVE-2025-37932 https://www.cve.org/CVERecord?id=CVE-2025-37932 Référence CVE CVE-2025-37933 https://www.cve.org/CVERecord?id=CVE-2025-37933 Référence CVE CVE-2025-37936 https://www.cve.org/CVERecord?id=CVE-2025-37936 Référence CVE CVE-2025-37938 https://www.cve.org/CVERecord?id=CVE-2025-37938 Référence CVE CVE-2025-37945 https://www.cve.org/CVERecord?id=CVE-2025-37945 Référence CVE CVE-2025-37946 https://www.cve.org/CVERecord?id=CVE-2025-37946 Référence CVE CVE-2025-37953 https://www.cve.org/CVERecord?id=CVE-2025-37953 Référence CVE CVE-2025-37961 https://www.cve.org/CVERecord?id=CVE-2025-37961 Référence CVE CVE-2025-37967 https://www.cve.org/CVERecord?id=CVE-2025-37967 Référence CVE CVE-2025-37968 https://www.cve.org/CVERecord?id=CVE-2025-37968 Référence CVE CVE-2025-37973 https://www.cve.org/CVERecord?id=CVE-2025-37973 Référence CVE CVE-2025-37987 https://www.cve.org/CVERecord?id=CVE-2025-37987 Référence CVE CVE-2025-37992 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0607Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2025-37931 Référence CVE CVE-2025-37932 https://www.cve.org/CVERecord?id=CVE-2025-37932 Référence CVE CVE-2025-37933 https://www.cve.org/CVERecord?id=CVE-2025-37933 Référence CVE CVE-2025-37934 https://www.cve.org/CVERecord?id=CVE-2025-37934 Référence CVE CVE-2025-37936 https://www.cve.org/CVERecord?id=CVE-2025-37936 Référence CVE CVE-2025-37937 https://www.cve.org/CVERecord?id=CVE-2025-37937 Référence CVE CVE-2025-37938 https://www.cve.org/CVERecord?id=CVE-2025-37938 Référence CVE CVE-2025-37943 https://www.cve.org/CVERecord?id=CVE-2025-37943 Référence CVE CVE-2025-37944 https://www.cve.org/CVERecord?id=CVE-2025-37944 Référence CVE CVE-2025-37945 https://www.cve.org/CVERecord?id=CVE-2025-37945 Référence CVE CVE-2025-37946 https://www.cve.org/CVERecord?id=CVE-2025-37946 Référence CVE CVE-2025-37948 https://www.cve.org/CVERecord?id=CVE-2025-37948 Référence CVE CVE-2025-37951 https://www.cve.org/CVERecord?id=CVE-2025-37951 Référence CVE CVE-2025-37953 https://www.cve.org/CVERecord?id=CVE-2025-37953 Référence CVE CVE-2025-37954 https://www.cve.org/CVERecord?id=CVE-2025-37954 Référence CVE CVE-2025-37959 https://www.cve.org/CVERecord?id=CVE-2025-37959 Référence CVE CVE-2025-37961 https://www.cve.org/CVERecord?id=CVE-2025-37961 Référence CVE CVE-2025-37963 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0589Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2025-37932 Référence CVE CVE-2025-37937 https://www.cve.org/CVERecord?id=CVE-2025-37937 Référence CVE CVE-2025-37938 https://www.cve.org/CVERecord?id=CVE-2025-37938 Référence CVE CVE-2025-37939 https://www.cve.org/CVERecord?id=CVE-2025-37939 Référence CVE CVE-2025-37940 https://www.cve.org/CVERecord?id=CVE-2025-37940 Référence CVE CVE-2025-37941 https://www.cve.org/CVERecord?id=CVE-2025-37941 Référence CVE CVE-2025-37942 https://www.cve.org/CVERecord?id=CVE-2025-37942 Référence CVE CVE-2025-37943 https://www.cve.org/CVERecord?id=CVE-2025-37943 Référence CVE CVE-2025-37944 https://www.cve.org/CVERecord?id=CVE-2025-37944 Référence CVE CVE-2025-37945 https://www.cve.org/CVERecord?id=CVE-2025-37945 Référence CVE CVE-2025-37975 https://www.cve.org/CVERecord?id=CVE-2025-37975 Référence CVE CVE-2025-37977 https://www.cve.org/CVERecord?id=CVE-2025-37977 Référence CVE CVE-2025-37978 https://www.cve.org/CVERecord?id=CVE-2025-37978 Référence CVE CVE-2025-37979 https://www.cve.org/CVERecord?id=CVE-2025-37979 Référence CVE CVE-2025-37980 https://www.cve.org/CVERecord?id=CVE-2025-37980 Référence CVE CVE-2025-37981 https://www.cve.org/CVERecord?id=CVE-2025-37981 Référence CVE CVE-2025-37982 https://www.cve.org/CVERecord?id=CVE-2025-37982 Référence CVE CVE-2025-37983 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0587Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2025-37931 Référence CVE CVE-2025-37932 https://www.cve.org/CVERecord?id=CVE-2025-37932 Référence CVE CVE-2025-37933 https://www.cve.org/CVERecord?id=CVE-2025-37933 Référence CVE CVE-2025-37934 https://www.cve.org/CVERecord?id=CVE-2025-37934 Référence CVE CVE-2025-37936 https://www.cve.org/CVERecord?id=CVE-2025-37936 Référence CVE CVE-2025-37937 https://www.cve.org/CVERecord?id=CVE-2025-37937 Référence CVE CVE-2025-37938 https://www.cve.org/CVERecord?id=CVE-2025-37938 Référence CVE CVE-2025-37943 https://www.cve.org/CVERecord?id=CVE-2025-37943 Référence CVE CVE-2025-37944 https://www.cve.org/CVERecord?id=CVE-2025-37944 Référence CVE CVE-2025-37945 https://www.cve.org/CVERecord?id=CVE-2025-37945 Référence CVE CVE-2025-37946 https://www.cve.org/CVERecord?id=CVE-2025-37946 Référence CVE CVE-2025-37948 https://www.cve.org/CVERecord?id=CVE-2025-37948 Référence CVE CVE-2025-37951 https://www.cve.org/CVERecord?id=CVE-2025-37951 Référence CVE CVE-2025-37953 https://www.cve.org/CVERecord?id=CVE-2025-37953 Référence CVE CVE-2025-37954 https://www.cve.org/CVERecord?id=CVE-2025-37954 Référence CVE CVE-2025-37959 https://www.cve.org/CVERecord?id=CVE-2025-37959 Référence CVE CVE-2025-37961 https://www.cve.org/CVERecord?id=CVE-2025-37961 Référence CVE CVE-2025-37963 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0559Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2025-37932 Référence CVE CVE-2025-37937 https://www.cve.org/CVERecord?id=CVE-2025-37937 Référence CVE CVE-2025-37938 https://www.cve.org/CVERecord?id=CVE-2025-37938 Référence CVE CVE-2025-37939 https://www.cve.org/CVERecord?id=CVE-2025-37939 Référence CVE CVE-2025-37940 https://www.cve.org/CVERecord?id=CVE-2025-37940 Référence CVE CVE-2025-37941 https://www.cve.org/CVERecord?id=CVE-2025-37941 Référence CVE CVE-2025-37942 https://www.cve.org/CVERecord?id=CVE-2025-37942 Référence CVE CVE-2025-37943 https://www.cve.org/CVERecord?id=CVE-2025-37943 Référence CVE CVE-2025-37944 https://www.cve.org/CVERecord?id=CVE-2025-37944 Référence CVE CVE-2025-37945 https://www.cve.org/CVERecord?id=CVE-2025-37945 Référence CVE CVE-2025-37975 https://www.cve.org/CVERecord?id=CVE-2025-37975 Référence CVE CVE-2025-37977 https://www.cve.org/CVERecord?id=CVE-2025-37977 Référence CVE CVE-2025-37978 https://www.cve.org/CVERecord?id=CVE-2025-37978 Référence CVE CVE-2025-37979 https://www.cve.org/CVERecord?id=CVE-2025-37979 Référence CVE CVE-2025-37980 https://www.cve.org/CVERecord?id=CVE-2025-37980 Référence CVE CVE-2025-37981 https://www.cve.org/CVERecord?id=CVE-2025-37981 Référence CVE CVE-2025-37982 https://www.cve.org/CVERecord?id=CVE-2025-37982 Référence CVE CVE-2025-37983 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2025-019552Linux の Linux Kernel における NULL ポインタデリファレンスに関する脆弱性

Linux の Linux Kernel には、NULL ポインタデリファレンスに関する脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Linux: < 6.0, 6.1.168 ≤ 6.1.*, 6.6.122 ≤ 6.6.*, 6.12.24 ≤ 6.12.*, 6.13.12 ≤ 6.13.*, 6.14.3 ≤ 6.14.*, 6.15 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 20 May 2025 · Last source change 8 Sept 2026, 08:41 UTC · CWE-476 · NULL Pointer Dereference

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2025-15839
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    744d23c71af39c7dc77ac7c3cac87ae86a181a85 < 17eef1e44883845b9567afc893dc41e004c08d65; 744d23c71af39c7dc77ac7c3cac87ae86a181a85 < 043aa41c43f8cb9cce75367ea07895ce68b5abb0; 744d23c71af39c7dc77ac7c3cac87ae86a181a85 < a6ed6f8ec81b8ca7100dcd9e62bdbc0dff1b2259; 744d23c71af39c7dc77ac7c3cac87ae86a181a85 < 54e5d00a8de6c13f6c01a94ed48025e882cd15f7; 744d23c71af39c7dc77ac7c3cac87ae86a181a85 < bd4037d51d3f6667636a1383e78e48a5b7b60755; 744d23c71af39c7dc77ac7c3cac87ae86a181a85 < fc75ea20ffb452652f0d4033f38fe88d7cfdae35; 47ac7b2f6a1ffef76e55a9ec146881a36673284b; 7dc0ed411de3450e75b2a9600b5742cbf0908167 · Fixed: < 6.0; 6.1.168 ≤ 6.1.*; 6.6.122 ≤ 6.6.*; 6.12.24 ≤ 6.12.*; 6.13.12 ≤ 6.13.*; 6.14.3 ≤ 6.14.*; 6.15 ≤ *
    After
    Linux: 744d23c71af39c7dc77ac7c3cac87ae86a181a85 < 17eef1e44883845b9567afc893dc41e004c08d65, 744d23c71af39c7dc77ac7c3cac87ae86a181a85 < 043aa41c43f8cb9cce75367ea07895ce68b5abb0, 744d23c71af39c7dc77ac7c3cac87ae86a181a85 < a6ed6f8ec81b8ca7100dcd9e62bdbc0dff1b2259, 744d23c71af39c7dc77ac7c3cac87ae86a181a85 < 54e5d00a8de6c13f6c01a94ed48025e882cd15f7, 744d23c71af39c7dc77ac7c3cac87ae86a181a85 < bd4037d51d3f6667636a1383e78e48a5b7b60755, 744d23c71af39c7dc77ac7c3cac87ae86a181a85 < fc75ea20ffb452652f0d4033f38fe88d7cfdae35, 47ac7b2f6a1ffef76e55a9ec146881a36673284b, 7dc0ed411de3450e75b2a9600b5742cbf0908167, 5.15.63 < 5.16, 5.19.4 < 5.20, 6.0 · Fixed: Linux: < 6.0, 6.1.168 ≤ 6.1.*, 6.6.122 ≤ 6.6.*, 6.12.24 ≤ 6.12.*, 6.13.12 ≤ 6.13.*, 6.14.3 ≤ 6.14.*, 6.15 ≤ *
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2025-15839↗Vendor CSAF · SUSE Product Security Team↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2025-37945 · cve.blacktree.nl