BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2024
CVE-2024-49998High confidence

net: dsa: improve shutdown sequence

Linux · Linux

4.7MediumCVSS 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 27 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.17% 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 27 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.

21 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 17 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.11.4-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.11.4-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.11.4-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-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-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-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-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-2024-49998 · CSAF 2.0 · revision 63 · interimSUSE Product Security TeamCVE-2024-49998
110 known affected

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

  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP5
  • kernel-default-devel as component of SUSE Linux Enterprise Desktop 15 SP5
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP5
  • kernel-devel as component of SUSE Linux Enterprise Desktop 15 SP5
  • kernel-macros as component of SUSE Linux Enterprise Desktop 15 SP5
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP5
  • 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 High Availability Extension 15 SP5
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP5
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5
Summary
In the Linux kernel, the following vulnerability has been resolved: net: dsa: improve shutdown sequence Alexander Sverdlin presents 2 problems during shutdown with the lan9303 driver. One is specific to lan9303 and the other just happens to reproduce there. The first problem is that lan9303 is unique among DSA drivers in that it calls dev_get_drvdata() at "arbitrary runtime" (not probe, not shutdown, not remove): phy_state_machine() -> ... -> dsa_user_phy_read() -> ds->ops->phy_read() -> lan9303_phy_read() -> chip->ops->phy_read() -> lan9303_mdio_phy_read() -> dev_get_drvdata() But we never stop the phy_state_machine(), so it may continue to run after dsa_switch_shutdown(). Our common pattern in all DSA drivers is to set drvdata to NULL to suppress the remove() method that may come afterwards. But in this case it will result in an NPD. The second problem is that the way in which we set dp->conduit->dsa_ptr = NULL; is concurrent with receive packet processing. dsa_switch_rcv() checks once whether dev->dsa_ptr is NULL, but afterwards, rather than continuing to use that non-NULL value, dev->dsa_ptr is dereferenced again and again without NULL checks: dsa_conduit_find_user() and many other places. In between dereferences, there is no locking to ensure that what was valid once continues to be valid. Both problems have the common aspect that closing the conduit interface solves them. In the first case, dev_close(conduit) triggers the NETDEV_GOING_DOWN event in dsa_user_netdevice_event() which closes user ports as well. dsa_port_disable_rt() calls phylink_stop(), which synchronously stops the phylink state machine, and ds->ops->phy_read() will thus no longer call into the driver after this point. In the second case, dev_close(conduit) should do this, as per Documentation/networking/driver.rst: | Quiescence | ---------- | | After the ndo_stop routine has been called, the hardware must | not receive or transmit any data. All in flight packets must | be aborted. If necessary, poll or wait for completion of | any reset commands. So it should be sufficient to ensure that later, when we zeroize conduit->dsa_ptr, there will be no concurrent dsa_switch_rcv() call on this conduit. The addition of the netif_device_detach() function is to ensure that ioctls, rtnetlinks and ethtool requests on the user ports no longer propagate down to the driver - we're no longer prepared to handle them. The race condition actually did not exist when commit 0650bf52b31f ("net: dsa: be compatible with masters which unregister on shutdown") first introduced dsa_switch_shutdown(). It was created later, when we stopped unregistering the user interfaces from a bad spot, and we just replaced that sequence with a racy zeroization of conduit->dsa_ptr (one which doesn't ensure that the interfaces aren't up).
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: dsa: improve shutdown sequence Alexander Sverdlin presents 2 problems during shutdown with the lan9303 driver. One is specific to lan9303 and the other just happens to reproduce there. The first problem is that lan9303 is unique among DSA drivers in that it calls dev_get_drvdata() at "arbitrary runtime" (not probe, not shutdown, not remove): phy_state_machine() -> ... -> dsa_user_phy_read() -> ds->ops->phy_read() -> lan9303_phy_read() -> chip->ops->phy_read() -> lan9303_mdio_phy_read() -> dev_get_drvdata() But we never stop the phy_state_machine(), so it may continue to run after dsa_switch_shutdown(). Our common pattern in all DSA drivers is to set drvdata to NULL to suppress the remove() method that may come afterwards. But in this case it will result in an NPD. The second problem is that the way in which we set dp->conduit->dsa_ptr = NULL; is concurrent with receive packet processing. dsa_switch_rcv() checks once whether dev->dsa_ptr is NULL, but afterwards, rather than continuing to use that non-NULL value, dev->dsa_ptr is dereferenced again and again without NULL checks: dsa_conduit_find_user() and many other places. In between dereferences, there is no locking to ensure that what was valid once continues to be valid. Both problems have the common aspect that closing the conduit interface solves them. In the first case, dev_close(conduit) triggers the NETDEV_GOING_DOWN event in dsa_user_netdevice_event() which closes user ports as well. dsa_port_disable_rt() calls phylink_stop(), which synchronously stops the phylink state machine, and ds->ops->phy_read() will thus no longer call into the driver after this point. In the second case, dev_close(conduit) should do this, as per Documentation/networking/driver.rst: | Quiescence | ---------- | | After the ndo_stop routine has been called, the hardware must | not receive or transmit any data. All in flight packets must | be aborted. If necessary, poll or wait for completion of | any reset commands. So it should be sufficient to ensure that later, when we zeroize conduit->dsa_ptr, there will be no concurrent dsa_switch_rcv() call on this conduit. The addition of the netif_device_detach() function is to ensure that ioctls, rtnetlinks and ethtool requests on the user ports no longer propagate down to the driver - we're no longer prepared to handle them. The race condition actually did not exist when commit 0650bf52b31f ("net: dsa: be compatible with masters which unregister on shutdown") first introduced dsa_switch_shutdown(). It was created later, when we stopped unregistering the user interfaces from a bad spot, and we just replaced that sequence with a racy zeroization of conduit->dsa_ptr (one which doesn't ensure that the interfaces aren't up).
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: dsa: improve shutdown sequence Alexander Sverdlin presents 2 problems during shutdown with the lan9303 driver. One is specific to lan9303 and the other just happens to reproduce there. The first problem is that lan9303 is unique among DSA drivers in that it calls dev_get_drvdata() at "arbitrary runtime" (not probe, not shutdown, not remove): phy_state_machine() -> ... -> dsa_user_phy_read() -> ds->ops->phy_read() -> lan9303_phy_read() -> chip->ops->phy_read() -> lan9303_mdio_phy_read() -> dev_get_drvdata() But we never stop the phy_state_machine(), so it may continue to run after dsa_switch_shutdown(). Our common pattern in all DSA drivers is to set drvdata to NULL to suppress the remove() method that may come afterwards. But in this case it will result in an NPD. The second problem is that the way in which we set dp->conduit->dsa_ptr = NULL; is concurrent with receive packet processing. dsa_switch_rcv() checks once whether dev->dsa_ptr is NULL, but afterwards, rather than continuing to use that non-NULL value, dev->dsa_ptr is dereferenced again and again without NULL checks: dsa_conduit_find_user() and many other places. In between dereferences, there is no locking to ensure that what was valid once continues to be valid. Both problems have the common aspect that closing the conduit interface solves them. In the first case, dev_close(conduit) triggers the NETDEV_GOING_DOWN event in dsa_user_netdevice_event() which closes user ports as well. dsa_port_disable_rt() calls phylink_stop(), which synchronously stops the phylink state machine, and ds->ops->phy_read() will thus no longer call into the driver after this point. In the second case, dev_close(conduit) should do this, as per Documentation/networking/driver.rst: | Quiescence | ---------- | | After the ndo_stop routine has been called, the hardware must | not receive or transmit any data. All in flight packets must | be aborted. If necessary, poll or wait for completion of | any reset commands. So it should be sufficient to ensure that later, when we zeroize conduit->dsa_ptr, there will be no concurrent dsa_switch_rcv() call on this conduit. The addition of the netif_device_detach() function is to ensure that ioctls, rtnetlinks and ethtool requests on the user ports no longer propagate down to the driver - we're no longer prepared to handle them. The race condition actually did not exist when commit 0650bf52b31f ("net: dsa: be compatible with masters which unregister on shutdown") first introduced dsa_switch_shutdown(). It was created later, when we stopped unregistering the user interfaces from a bad spot, and we just replaced that sequence with a racy zeroization of conduit->dsa_ptr (one which doesn't ensure that the interfaces aren't up).
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-2024-43672

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: net: dsa: improve shutdown sequence Alexander Sverdlin presents 2 problems during shutdown with the lan9303 driver. One is specific to lan9303 and the other just happens to reproduce there. The first problem is that lan9303 is unique among DSA drivers in that it calls dev_get_drvdata() at "arbitrary runtime" (not probe, not shutdown, not remove): phy_state_machine() -> ... -> dsa_user_phy_read() -> ds->ops->phy_read() -> lan9303_phy_read() -> chip->ops->phy_read() -> lan9303_mdio_phy_read() -> dev_get_drvdata() But we never stop the phy_state_machine(), so it may continue to run after dsa_switch_shutdown(). Our common pattern in all DSA drivers is to set drvdata to NULL to suppress the remove() method that may come afterwards. But in this case it will result in an NPD. The second problem is that the way in which we set dp->conduit->dsa_ptr = NULL; is concurrent with receive packet processing. dsa_switch_rcv() checks once whether dev->dsa_ptr is NULL, but afterwards, rather than continuing to use that non-NULL value, dev->dsa_ptr is dereferenced again and again without NULL checks: dsa_conduit_find_user() and many other places. In between dereferences, there is no locking to ensure that what was valid once continues to be valid. Both problems have the common aspect that closing the conduit interface solves them. In the first case, dev_close(conduit) triggers the NETDEV_GOING_DOWN event in dsa_user_netdevice_event() which closes user ports as well. dsa_port_disable_rt() calls phylink_stop(), which synchronously stops the phylink state machine, and ds->ops->phy_read() will thus no longer call into the driver after this point. In the second case, dev_close(conduit) should do this, as per Documentation/networking/driver.rst: | Quiescence | ---------- | | After the ndo_stop routine has been called, the hardware must | not receive or transmit any data. All in flight packets must | be aborted. If necessary, poll or wait for completion of | any reset commands. So it should be sufficient to ensure that later, when we zeroize conduit->dsa_ptr, there will be no concurrent dsa_switch_rcv() call on this conduit. The addition of the netif_device_detach() function is to ensure that ioctls, rtnetlinks and ethtool requests on the user ports no longer propagate down to the driver - we're no longer prepared to handle them. The race condition actually did not exist when commit 0650bf52b31f ("net: dsa: be compatible with masters which unregister on shutdown") first introduced dsa_switch_shutdown(). It was created later, when we stopped unregistering the user interfaces from a bad spot, and we just replaced that sequence with a racy zeroization of conduit->dsa_ptr (one which doesn't ensure that the interfaces aren't up).

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 27 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: dsa: improve shutdown sequence Alexander Sverdlin presents 2 problems during shutdown with the lan9303 driver. One is specific to lan9303 and the other just happens to reproduce there. The first problem is that lan9303 is unique among DSA drivers in that it calls dev_get_drvdata() at "arbitrary runtime" (not probe, not shutdown, not remove): phy_state_machine() -> ... -> dsa_user_phy_read() -> ds->ops->phy_read() -> lan9303_phy_read() -> chip->ops->phy_read() -> lan9303_mdio_phy_read() -> dev_get_drvdata() But we never stop the phy_state_machine(), so it may continue to run after dsa_switch_shutdown(). Our common pattern in all DSA drivers is to set drvdata to NULL to suppress the remove() method that may come afterwards. But in this case it will result in an NPD. The second problem is that the way in which we set dp->conduit->dsa_ptr = NULL; is concurrent with receive packet processing. dsa_switch_rcv() checks once whether dev->dsa_ptr is NULL, but afterwards, rather than continuing to use that non-NULL value, dev->dsa_ptr is dereferenced again and again without NULL checks: dsa_conduit_find_user() and many other places. In between dereferences, there is no locking to ensure that what was valid once continues to be valid. Both problems have the common aspect that closing the conduit interface solves them. In the first case, dev_close(conduit) triggers the NETDEV_GOING_DOWN event in dsa_user_netdevice_event() which closes user ports as well. dsa_port_disable_rt() calls phylink_stop(), which synchronously stops the phylink state machine, and ds->ops->phy_read() will thus no longer call into the driver after this point. In the second case, dev_close(conduit) should do this, as per Documentation/networking/driver.rst: | Quiescence | ---------- | | After the ndo_stop routine has been called, the hardware must | not receive or transmit any data. All in flight packets must | be aborted. If necessary, poll or wait for completion of | any reset commands. So it should be sufficient to ensure that later, when we zeroize conduit->dsa_ptr, there will be no concurrent dsa_switch_rcv() call on this conduit. The addition of the netif_device_detach() function is to ensure that ioctls, rtnetlinks and ethtool requests on the user ports no longer propagate down to the driver - we're no longer prepared to handle them. The race condition actually did not exist when commit 0650bf52b31f ("net: dsa: be compatible with masters which unregister on shutdown") first introduced dsa_switch_shutdown(). It was created later, when we stopped unregistering the user interfaces from a bad spot, and we just replaced that sequence with a racy zeroization of conduit->dsa_ptr (one which doesn't ensure that the interfaces aren't up).

What

In the Linux kernel, the following vulnerability has been resolved: net: dsa: improve shutdown sequence Alexander Sverdlin presents 2 problems during shutdown with the lan9303 driver. One is specific to lan9303 and the other just happens to reproduce there. The first problem is that lan9303 is unique among DSA drivers in that it calls dev_get_drvdata() at "arbitrary runtime" (not probe, not shutdown, not remove): phy_state_machine() -> ... -> dsa_user_phy_read() -> ds->ops->phy_read() -> lan9303_phy_read() -> chip->ops->phy_read() -> lan9303_mdio_phy_read() -> dev_get_drvdata() But we never stop the phy_state_machine(), so it may continue to run after dsa_switch_shutdown(). Our common pattern in all DSA drivers is to set drvdata to NULL to suppress the remove() method that may come afterwards. But in this case it will result in an NPD. The second problem is that the way in which we set dp->conduit->dsa_ptr = NULL; is concurrent with receive packet processing. dsa_switch_rcv() checks once whether dev->dsa_ptr is NULL, but afterwards, rather than continuing to use that non-NULL value, dev->dsa_ptr is dereferenced again and again without NULL checks: dsa_conduit_find_user() and many other places. In between dereferences, there is no locking to ensure that what was valid once continues to be valid. Both problems have the common aspect that closing the conduit interface solves them. In the first case, dev_close(conduit) triggers the NETDEV_GOING_DOWN event in dsa_user_netdevice_event() which closes user ports as well. dsa_port_disable_rt() calls phylink_stop(), which synchronously stops the phylink state machine, and ds->ops->phy_read() will thus no longer call into the driver after this point. In the second case, dev_close(conduit) should do this, as per Documentation/networking/driver.rst: | Quiescence | ---------- | | After the ndo_stop routine has been called, the hardware must | not receive or transmit any data. All in flight packets must | be aborted. If necessary, poll or wait for completion of | any reset commands. So it should be sufficient to ensure that later, when we zeroize conduit->dsa_ptr, there will be no concurrent dsa_switch_rcv() call on this conduit. The addition of the netif_device_detach() function is to ensure that ioctls, rtnetlinks and ethtool requests on the user ports no longer propagate down to the driver - we're no longer prepared to handle them. The race condition actually did not exist when commit 0650bf52b31f ("net: dsa: be compatible with masters which unregister on shutdown") first introduced dsa_switch_shutdown(). It was created later, when we stopped unregistering the user interfaces from a bad spot, and we just replaced that sequence with a racy zeroization of conduit->dsa_ptr (one which doesn't ensure that the interfaces aren't up).

Why

The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In the Linux kernel, the following vulnerability has been resolved: net: dsa: improve shutdown sequence Alexander Sverdlin presents 2 problems during shutdown with the lan9303 driver. One is specific to lan9303 and the other just happens to reproduce there. The first problem is that lan9303 is unique among DSA drivers in that it calls dev_get_drvdata() at "arbitrary runtime" (not probe, not shutdown, not remove): phy_state_machine() -> ... -> dsa_user_phy_read() -> ds->ops->phy_read() -> lan9303_phy_read() -> chip->ops->phy_read() -> lan9303_mdio_phy_read() -> dev_get_drvdata() But we never stop the phy_state_machine(), so it may continue to run after dsa_switch_shutdown(). Our common pattern in all DSA drivers is to set drvdata to NULL to suppress the remove() method that may come afterwards. But in this case it will result in an NPD. The second problem is that the way in which we set dp->conduit->dsa_ptr = NULL; is concurrent with receive packet processing. dsa_switch_rcv() checks once whether dev->dsa_ptr is NULL, but afterwards, rather than continuing to use that non-NULL value, dev->dsa_ptr is dereferenced again and again without NULL checks: dsa_conduit_find_user() and many other places. In between dereferences, there is no locking to ensure that what was valid once continues to be valid. Both problems have the common aspect that closing the conduit interface solves them. In the first case, dev_close(conduit) triggers the NETDEV_GOING_DOWN event in dsa_user_netdevice_event() which closes user ports as well. dsa_port_disable_rt() calls phylink_stop(), which synchronously stops the phylink state machine, and ds->ops->phy_read() will thus no longer call into the driver after this point. In the second case, dev_close(conduit) should do this, as per Documentation/networking/driver.rst: | Quiescence | ---------- | | After the ndo_stop routine has been called, the hardware must | not receive or transmit any data. All in flight packets must | be aborted. If necessary, poll or wait for completion of | any reset commands. So it should be sufficient to ensure that later, when we zeroize conduit->dsa_ptr, there will be no concurrent dsa_switch_rcv() call on this conduit. The addition of the netif_device_detach() function is to ensure that ioctls, rtnetlinks and ethtool requests on the user ports no longer propagate down to the driver - we're no longer prepared to handle them. The race condition actually did not exist when commit 0650bf52b31f ("net: dsa: be compatible with masters which unregister on shutdown") first introduced dsa_switch_shutdown(). It was created later, when we stopped unregistering the user interfaces from a bad spot, and we just replaced that sequence with a racy zeroization of conduit->dsa_ptr (one which doesn't ensure that the interfaces aren't up).

Why

The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

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 → Time-of-check Time-of-use (TOCTOU) Race Condition → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
High: exploitation depends on specific conditions
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-367 ↗

CWE-367: Time-of-check Time-of-use (TOCTOU) Race Condition. The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check.

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:H/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.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.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.
CWE-367
A

Official authority intelligence

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

ENISA EUVD · EUVD-2024-43672Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: net: dsa: improve shutdown sequence Alexander Sverdlin presents 2 problems during shutdown with the lan9303 driver. One is specific to lan9303 and the other just happens to reproduce there. The first problem is that lan9303 is unique among DSA drivers in that it calls dev_get_drvdata() at "arbitrary runtime" (not probe, not shutdown, not remove): phy_state_machine() -> ... -> dsa_user_phy_read() -> ds->ops->phy_read() -> lan9303_phy_read() -> chip->ops->phy_read() -> lan9303_mdio_phy_read() -> dev_get_drvdata() But we never stop the phy_state_machine(), so it may continue to run after dsa_switch_shutdown(). Our common pattern in all DSA drivers is to set drvdata to NULL to suppress the remove() method that may come afterwards. But in this case it will result in an NPD. The second problem is that the way in which we set dp->conduit->dsa_ptr = NULL; is concurrent with receive packet processing. dsa_switch_rcv() checks once whether dev->dsa_ptr is NULL, but afterwards, rather than continuing to use that non-NULL value, dev->dsa_ptr is dereferenced again and again without NULL checks: dsa_conduit_find_user() and many other places. In between dereferences, there is no locking to ensure that what was valid once continues to be valid. Both problems have the common aspect that closing the conduit interface solves them. In the first case, dev_close(conduit) triggers the NETDEV_GOING_DOWN event in dsa_user_netdevice_event() which closes user ports as well. dsa_port_disable_rt() calls phylink_stop(), which synchronously stops the phylink state machine, and ds->ops->phy_read() will thus no longer call into the driver after this point. In the second case, dev_close(conduit) should do this, as per Documentation/networking/driver.rst: | Quiescence | ---------- | | After the ndo_stop routine has been called, the hardware must | not receive or transmit any data. All in flight packets must | be aborted. If necessary, poll or wait for completion of | any reset commands. So it should be sufficient to ensure that later, when we zeroize conduit->dsa_ptr, there will be no concurrent dsa_switch_rcv() call on this conduit. The addition of the netif_device_detach() function is to ensure that ioctls, rtnetlinks and ethtool requests on the user ports no longer propagate down to the driver - we're no longer prepared to handle them. The race condition actually did not exist when commit 0650bf52b31f ("net: dsa: be compatible with masters which unregister on shutdown") first introduced dsa_switch_shutdown(). It was created later, when we stopped unregistering the user interfaces from a bad spot, and we just replaced that sequence with a racy zeroization of conduit->dsa_ptr (one which doesn't ensure that the interfaces aren't up).

Official EUVD record ↗
BSI · German · WID-SEC-2024-3251Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service

Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere, nicht näher bekannte Auswirkungen zu erzielen..

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20241023Security Bulletin 23 Oct 2024

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 23 Oct 2024, published on 23 October 2024. Open the linked bulletin for the product, severity and reference information published in that issue.

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

fidentialité des données Contournement de la politique de sécurité Déni de service à distance Exécution de code arbitraire à distance Non spécifié par l'éditeur Élévation de privilèges Systèmes affectés Desigo CC toutes versions Desigo CC toutes versions pour la vulnérabilité CVE-2025-15467 Desigo CC versions antérieures à 9.0.1 SIMATIC S7-1500 versions supérieures ou égales à 3.1.6 pour les vulnérabilités CVE-2021-41617, CVE-2023-28531, CVE-2023-51384, CVE-2023-52927, CVE-2024-26783, CVE-2024-27056, CVE-2024-28956, CVE-2024-36903, CVE-2024-36927, CVE-2024-42079, CVE-2024-46786, CVE-2024-47736, CVE-2024-47809, CVE-2024-49968, CVE-2024-49994, CVE-2024-49998, CVE-2024-50014, CVE-2024-50063, CVE-2024-50164, CVE-2024-50298, CVE-2024-53124, CVE-2024-53170, CVE-2024-54458, CVE-2024-56631, CVE-2024-56703, CVE-2024-56719, CVE-2024-57917, CVE-2024-57924, CVE-2024-57973, CVE-2024-57977, CVE-2024-57979, CVE-2024-58011, CVE-2024-58016, CVE-2024-58020, CVE-2024-58056, CVE-2024-58058, CVE-2024-58061, CVE-2024-58086, CVE-2025-21645, CVE-2025-21648, CVE-2025-21655, CVE-2025-21676, CVE-2025-21682, CVE-2025-21702, CVE-2025-21705, CVE-2025-21706, CVE-2025-21707, CVE-2025-21718, CVE-2025-21731, CVE-2025-21745, CVE-2025-21758, CVE-2025-21760, CVE-2025-21764, CVE-2025-21765, CVE-2025-21780, CVE-2025-21795, CVE-2025

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

tion Bulletin de sécurité Debian LTS msg00004 du 02 mai 2026 https://lists.debian.org/debian-lts-announce/2026/05/msg00004.html Bulletin de sécurité Debian LTS msg00005 du 02 mai 2026 https://lists.debian.org/debian-lts-announce/2026/05/msg00005.html Référence CVE CVE-2023-53228 https://www.cve.org/CVERecord?id=CVE-2023-53228 Référence CVE CVE-2023-53510 https://www.cve.org/CVERecord?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=

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

bian.org/debian-security-announce/2026/msg00148.html Bulletin de sécurité Debian msg00154 du 01 mai 2026 https://lists.debian.org/debian-security-announce/2026/msg00154.html Référence CVE CVE-2023-53228 https://www.cve.org/CVERecord?id=CVE-2023-53228 Référence CVE CVE-2023-53510 https://www.cve.org/CVERecord?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-14027 https://www.cve.org/CVERecord?id=CVE-2024-14027 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-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=

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

d?id=CVE-2024-49985 Référence CVE CVE-2024-49987 https://www.cve.org/CVERecord?id=CVE-2024-49987 Référence CVE CVE-2024-49988 https://www.cve.org/CVERecord?id=CVE-2024-49988 Référence CVE CVE-2024-49989 https://www.cve.org/CVERecord?id=CVE-2024-49989 Référence CVE CVE-2024-49991 https://www.cve.org/CVERecord?id=CVE-2024-49991 Référence CVE CVE-2024-49992 https://www.cve.org/CVERecord?id=CVE-2024-49992 Référence CVE CVE-2024-49994 https://www.cve.org/CVERecord?id=CVE-2024-49994 Référence CVE CVE-2024-49996 https://www.cve.org/CVERecord?id=CVE-2024-49996 Référence CVE CVE-2024-49997 https://www.cve.org/CVERecord?id=CVE-2024-49997 Référence CVE CVE-2024-49998 https://www.cve.org/CVERecord?id=CVE-2024-49998 Référence CVE CVE-2024-50000 https://www.cve.org/CVERecord?id=CVE-2024-50000 Référence CVE CVE-2024-50001 https://www.cve.org/CVERecord?id=CVE-2024-50001 Référence CVE CVE-2024-50002 https://www.cve.org/CVERecord?id=CVE-2024-50002 Référence CVE CVE-2024-50006 https://www.cve.org/CVERecord?id=CVE-2024-50006 Référence CVE CVE-2024-50007 https://www.cve.org/CVERecord?id=CVE-2024-50007 Référence CVE CVE-2024-50008 https://www.cve.org/CVERecord?id=CVE-2024-50008 Référence CVE CVE-2024-50009 https://www.cve.org/CVERecord?id=CVE-2024-50009 Référence CVE CVE-2024-50010 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-49920 Référence CVE CVE-2024-49921 https://www.cve.org/CVERecord?id=CVE-2024-49921 Référence CVE CVE-2024-49925 https://www.cve.org/CVERecord?id=CVE-2024-49925 Référence CVE CVE-2024-49936 https://www.cve.org/CVERecord?id=CVE-2024-49936 Référence CVE CVE-2024-49950 https://www.cve.org/CVERecord?id=CVE-2024-49950 Référence CVE CVE-2024-49968 https://www.cve.org/CVERecord?id=CVE-2024-49968 Référence CVE CVE-2024-49972 https://www.cve.org/CVERecord?id=CVE-2024-49972 Référence CVE CVE-2024-49974 https://www.cve.org/CVERecord?id=CVE-2024-49974 Référence CVE CVE-2024-49996 https://www.cve.org/CVERecord?id=CVE-2024-49996 Référence CVE CVE-2024-49998 https://www.cve.org/CVERecord?id=CVE-2024-49998 Référence CVE CVE-2024-50009 https://www.cve.org/CVERecord?id=CVE-2024-50009 Référence CVE CVE-2024-50010 https://www.cve.org/CVERecord?id=CVE-2024-50010 Référence CVE CVE-2024-50019 https://www.cve.org/CVERecord?id=CVE-2024-50019 Référence CVE CVE-2024-50020 https://www.cve.org/CVERecord?id=CVE-2024-50020 Référence CVE CVE-2024-50021 https://www.cve.org/CVERecord?id=CVE-2024-50021 Référence CVE CVE-2024-50022 https://www.cve.org/CVERecord?id=CVE-2024-50022 Référence CVE CVE-2024-50023 https://www.cve.org/CVERecord?id=CVE-2024-50023 Référence CVE CVE-2024-50024 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-47730 Référence CVE CVE-2024-48881 https://www.cve.org/CVERecord?id=CVE-2024-48881 Référence CVE CVE-2024-49571 https://www.cve.org/CVERecord?id=CVE-2024-49571 Référence CVE CVE-2024-49925 https://www.cve.org/CVERecord?id=CVE-2024-49925 Référence CVE CVE-2024-49948 https://www.cve.org/CVERecord?id=CVE-2024-49948 Référence CVE CVE-2024-49950 https://www.cve.org/CVERecord?id=CVE-2024-49950 Référence CVE CVE-2024-49952 https://www.cve.org/CVERecord?id=CVE-2024-49952 Référence CVE CVE-2024-49974 https://www.cve.org/CVERecord?id=CVE-2024-49974 Référence CVE CVE-2024-49996 https://www.cve.org/CVERecord?id=CVE-2024-49996 Référence CVE CVE-2024-49998 https://www.cve.org/CVERecord?id=CVE-2024-49998 Référence CVE CVE-2024-50051 https://www.cve.org/CVERecord?id=CVE-2024-50051 Référence CVE CVE-2024-50055 https://www.cve.org/CVERecord?id=CVE-2024-50055 Référence CVE CVE-2024-50121 https://www.cve.org/CVERecord?id=CVE-2024-50121 Référence CVE CVE-2024-50167 https://www.cve.org/CVERecord?id=CVE-2024-50167 Référence CVE CVE-2024-50242 https://www.cve.org/CVERecord?id=CVE-2024-50242 Référence CVE CVE-2024-50265 https://www.cve.org/CVERecord?id=CVE-2024-50265 Référence CVE CVE-2024-50275 https://www.cve.org/CVERecord?id=CVE-2024-50275 Référence CVE CVE-2024-50283 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-49987 Référence CVE CVE-2024-49988 https://www.cve.org/CVERecord?id=CVE-2024-49988 Référence CVE CVE-2024-49989 https://www.cve.org/CVERecord?id=CVE-2024-49989 Référence CVE CVE-2024-49991 https://www.cve.org/CVERecord?id=CVE-2024-49991 Référence CVE CVE-2024-49992 https://www.cve.org/CVERecord?id=CVE-2024-49992 Référence CVE CVE-2024-49994 https://www.cve.org/CVERecord?id=CVE-2024-49994 Référence CVE CVE-2024-49995 https://www.cve.org/CVERecord?id=CVE-2024-49995 Référence CVE CVE-2024-49996 https://www.cve.org/CVERecord?id=CVE-2024-49996 Référence CVE CVE-2024-49997 https://www.cve.org/CVERecord?id=CVE-2024-49997 Référence CVE CVE-2024-49998 https://www.cve.org/CVERecord?id=CVE-2024-49998 Référence CVE CVE-2024-49999 https://www.cve.org/CVERecord?id=CVE-2024-49999 Référence CVE CVE-2024-50000 https://www.cve.org/CVERecord?id=CVE-2024-50000 Référence CVE CVE-2024-50001 https://www.cve.org/CVERecord?id=CVE-2024-50001 Référence CVE CVE-2024-50002 https://www.cve.org/CVERecord?id=CVE-2024-50002 Référence CVE CVE-2024-50005 https://www.cve.org/CVERecord?id=CVE-2024-50005 Référence CVE CVE-2024-50006 https://www.cve.org/CVERecord?id=CVE-2024-50006 Référence CVE CVE-2024-50007 https://www.cve.org/CVERecord?id=CVE-2024-50007 Référence CVE CVE-2024-50008 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-49987 Référence CVE CVE-2024-49988 https://www.cve.org/CVERecord?id=CVE-2024-49988 Référence CVE CVE-2024-49989 https://www.cve.org/CVERecord?id=CVE-2024-49989 Référence CVE CVE-2024-49991 https://www.cve.org/CVERecord?id=CVE-2024-49991 Référence CVE CVE-2024-49992 https://www.cve.org/CVERecord?id=CVE-2024-49992 Référence CVE CVE-2024-49994 https://www.cve.org/CVERecord?id=CVE-2024-49994 Référence CVE CVE-2024-49995 https://www.cve.org/CVERecord?id=CVE-2024-49995 Référence CVE CVE-2024-49996 https://www.cve.org/CVERecord?id=CVE-2024-49996 Référence CVE CVE-2024-49997 https://www.cve.org/CVERecord?id=CVE-2024-49997 Référence CVE CVE-2024-49998 https://www.cve.org/CVERecord?id=CVE-2024-49998 Référence CVE CVE-2024-49999 https://www.cve.org/CVERecord?id=CVE-2024-49999 Référence CVE CVE-2024-50000 https://www.cve.org/CVERecord?id=CVE-2024-50000 Référence CVE CVE-2024-50001 https://www.cve.org/CVERecord?id=CVE-2024-50001 Référence CVE CVE-2024-50002 https://www.cve.org/CVERecord?id=CVE-2024-50002 Référence CVE CVE-2024-50003 https://www.cve.org/CVERecord?id=CVE-2024-50003 Référence CVE CVE-2024-50005 https://www.cve.org/CVERecord?id=CVE-2024-50005 Référence CVE CVE-2024-50006 https://www.cve.org/CVERecord?id=CVE-2024-50006 Référence CVE CVE-2024-50007 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-49987 Référence CVE CVE-2024-49988 https://www.cve.org/CVERecord?id=CVE-2024-49988 Référence CVE CVE-2024-49989 https://www.cve.org/CVERecord?id=CVE-2024-49989 Référence CVE CVE-2024-49991 https://www.cve.org/CVERecord?id=CVE-2024-49991 Référence CVE CVE-2024-49992 https://www.cve.org/CVERecord?id=CVE-2024-49992 Référence CVE CVE-2024-49994 https://www.cve.org/CVERecord?id=CVE-2024-49994 Référence CVE CVE-2024-49995 https://www.cve.org/CVERecord?id=CVE-2024-49995 Référence CVE CVE-2024-49996 https://www.cve.org/CVERecord?id=CVE-2024-49996 Référence CVE CVE-2024-49997 https://www.cve.org/CVERecord?id=CVE-2024-49997 Référence CVE CVE-2024-49998 https://www.cve.org/CVERecord?id=CVE-2024-49998 Référence CVE CVE-2024-49999 https://www.cve.org/CVERecord?id=CVE-2024-49999 Référence CVE CVE-2024-50000 https://www.cve.org/CVERecord?id=CVE-2024-50000 Référence CVE CVE-2024-50001 https://www.cve.org/CVERecord?id=CVE-2024-50001 Référence CVE CVE-2024-50002 https://www.cve.org/CVERecord?id=CVE-2024-50002 Référence CVE CVE-2024-50005 https://www.cve.org/CVERecord?id=CVE-2024-50005 Référence CVE CVE-2024-50006 https://www.cve.org/CVERecord?id=CVE-2024-50006 Référence CVE CVE-2024-50007 https://www.cve.org/CVERecord?id=CVE-2024-50007 Référence CVE CVE-2024-50008 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-49987 Référence CVE CVE-2024-49988 https://www.cve.org/CVERecord?id=CVE-2024-49988 Référence CVE CVE-2024-49989 https://www.cve.org/CVERecord?id=CVE-2024-49989 Référence CVE CVE-2024-49991 https://www.cve.org/CVERecord?id=CVE-2024-49991 Référence CVE CVE-2024-49992 https://www.cve.org/CVERecord?id=CVE-2024-49992 Référence CVE CVE-2024-49994 https://www.cve.org/CVERecord?id=CVE-2024-49994 Référence CVE CVE-2024-49995 https://www.cve.org/CVERecord?id=CVE-2024-49995 Référence CVE CVE-2024-49996 https://www.cve.org/CVERecord?id=CVE-2024-49996 Référence CVE CVE-2024-49997 https://www.cve.org/CVERecord?id=CVE-2024-49997 Référence CVE CVE-2024-49998 https://www.cve.org/CVERecord?id=CVE-2024-49998 Référence CVE CVE-2024-49999 https://www.cve.org/CVERecord?id=CVE-2024-49999 Référence CVE CVE-2024-50000 https://www.cve.org/CVERecord?id=CVE-2024-50000 Référence CVE CVE-2024-50001 https://www.cve.org/CVERecord?id=CVE-2024-50001 Référence CVE CVE-2024-50002 https://www.cve.org/CVERecord?id=CVE-2024-50002 Référence CVE CVE-2024-50003 https://www.cve.org/CVERecord?id=CVE-2024-50003 Référence CVE CVE-2024-50005 https://www.cve.org/CVERecord?id=CVE-2024-50005 Référence CVE CVE-2024-50006 https://www.cve.org/CVERecord?id=CVE-2024-50006 Référence CVE CVE-2024-50007 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-47141 Référence CVE CVE-2024-47143 https://www.cve.org/CVERecord?id=CVE-2024-47143 Référence CVE CVE-2024-47809 https://www.cve.org/CVERecord?id=CVE-2024-47809 Référence CVE CVE-2024-48873 https://www.cve.org/CVERecord?id=CVE-2024-48873 Référence CVE CVE-2024-48881 https://www.cve.org/CVERecord?id=CVE-2024-48881 Référence CVE CVE-2024-49569 https://www.cve.org/CVERecord?id=CVE-2024-49569 Référence CVE CVE-2024-49948 https://www.cve.org/CVERecord?id=CVE-2024-49948 Référence CVE CVE-2024-49951 https://www.cve.org/CVERecord?id=CVE-2024-49951 Référence CVE CVE-2024-49978 https://www.cve.org/CVERecord?id=CVE-2024-49978 Référence CVE CVE-2024-49998 https://www.cve.org/CVERecord?id=CVE-2024-49998 Référence CVE CVE-2024-50051 https://www.cve.org/CVERecord?id=CVE-2024-50051 Référence CVE CVE-2024-50106 https://www.cve.org/CVERecord?id=CVE-2024-50106 Référence CVE CVE-2024-50136 https://www.cve.org/CVERecord?id=CVE-2024-50136 Référence CVE CVE-2024-50142 https://www.cve.org/CVERecord?id=CVE-2024-50142 Référence CVE CVE-2024-50151 https://www.cve.org/CVERecord?id=CVE-2024-50151 Référence CVE CVE-2024-50195 https://www.cve.org/CVERecord?id=CVE-2024-50195 Référence CVE CVE-2024-50199 https://www.cve.org/CVERecord?id=CVE-2024-50199 Référence CVE CVE-2024-50210 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-47143 Référence CVE CVE-2024-47684 https://www.cve.org/CVERecord?id=CVE-2024-47684 Référence CVE CVE-2024-47809 https://www.cve.org/CVERecord?id=CVE-2024-47809 Référence CVE CVE-2024-48873 https://www.cve.org/CVERecord?id=CVE-2024-48873 Référence CVE CVE-2024-48881 https://www.cve.org/CVERecord?id=CVE-2024-48881 Référence CVE CVE-2024-49569 https://www.cve.org/CVERecord?id=CVE-2024-49569 Référence CVE CVE-2024-49948 https://www.cve.org/CVERecord?id=CVE-2024-49948 Référence CVE CVE-2024-49951 https://www.cve.org/CVERecord?id=CVE-2024-49951 Référence CVE CVE-2024-49978 https://www.cve.org/CVERecord?id=CVE-2024-49978 Référence CVE CVE-2024-49998 https://www.cve.org/CVERecord?id=CVE-2024-49998 Référence CVE CVE-2024-50051 https://www.cve.org/CVERecord?id=CVE-2024-50051 Référence CVE CVE-2024-50106 https://www.cve.org/CVERecord?id=CVE-2024-50106 Référence CVE CVE-2024-50151 https://www.cve.org/CVERecord?id=CVE-2024-50151 Référence CVE CVE-2024-50199 https://www.cve.org/CVERecord?id=CVE-2024-50199 Référence CVE CVE-2024-50251 https://www.cve.org/CVERecord?id=CVE-2024-50251 Référence CVE CVE-2024-50258 https://www.cve.org/CVERecord?id=CVE-2024-50258 Référence CVE CVE-2024-50299 https://www.cve.org/CVERecord?id=CVE-2024-50299 Référence CVE CVE-2024-50304 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-48881 Référence CVE CVE-2024-49569 https://www.cve.org/CVERecord?id=CVE-2024-49569 Référence CVE CVE-2024-49854 https://www.cve.org/CVERecord?id=CVE-2024-49854 Référence CVE CVE-2024-49884 https://www.cve.org/CVERecord?id=CVE-2024-49884 Référence CVE CVE-2024-49915 https://www.cve.org/CVERecord?id=CVE-2024-49915 Référence CVE CVE-2024-49925 https://www.cve.org/CVERecord?id=CVE-2024-49925 Référence CVE CVE-2024-49944 https://www.cve.org/CVERecord?id=CVE-2024-49944 Référence CVE CVE-2024-49951 https://www.cve.org/CVERecord?id=CVE-2024-49951 Référence CVE CVE-2024-49952 https://www.cve.org/CVERecord?id=CVE-2024-49952 Référence CVE CVE-2024-49998 https://www.cve.org/CVERecord?id=CVE-2024-49998 Référence CVE CVE-2024-50016 https://www.cve.org/CVERecord?id=CVE-2024-50016 Référence CVE CVE-2024-50018 https://www.cve.org/CVERecord?id=CVE-2024-50018 Référence CVE CVE-2024-50039 https://www.cve.org/CVERecord?id=CVE-2024-50039 Référence CVE CVE-2024-50047 https://www.cve.org/CVERecord?id=CVE-2024-50047 Référence CVE CVE-2024-50051 https://www.cve.org/CVERecord?id=CVE-2024-50051 Référence CVE CVE-2024-50106 https://www.cve.org/CVERecord?id=CVE-2024-50106 Référence CVE CVE-2024-50143 https://www.cve.org/CVERecord?id=CVE-2024-50143 Référence CVE CVE-2024-50151 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-011794Linux の Linux Kernel における Time-of-check Time-of-use (TOCTOU) 競合状態の脆弱性

Linux の Linux Kernel には、Time-of-check Time-of-use (TOCTOU) 競合状態の脆弱性、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: < 5.17, 5.15.176 ≤ 5.15.*, 6.1.167 ≤ 6.1.*, 6.6.117 ≤ 6.6.*, 6.10.14 ≤ 6.10.*, 6.11.3 ≤ 6.11.*, 6.12 ≤ *
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 21 Oct 2024 · Last source change 8 Sept 2026, 08:39 UTC · CWE-367 · Time-of-check Time-of-use (TOCTOU) Race Condition

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-2024-43672
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
    ff45899e732e57088985e3a497b1d9100571c0f5 < 87bd909a7014e32790e8c759d5b7694a95778ca5; ee534378f00561207656663d93907583958339ae < ab9e90619b6339becc5415647ae154a9a46a044d; ee534378f00561207656663d93907583958339ae < 2e93bf719462ac6d23c881c8b93e5dc9bf5ab7f5; ee534378f00561207656663d93907583958339ae < ab5d3420a1120950703dbdc33698b28a6ebc3d23; ee534378f00561207656663d93907583958339ae < b4a65d479213fe84ecb14e328271251eebe69492; ee534378f00561207656663d93907583958339ae < 6c24a03a61a245fe34d47582898331fa034b6ccd; 89b60402d43cdab4387dbbf24afebda5cf092ae7; 5.15.155 < 5.15.176 · Fixed: < 5.17; 5.15.176 ≤ 5.15.*; 6.1.167 ≤ 6.1.*; 6.6.117 ≤ 6.6.*; 6.10.14 ≤ 6.10.*; 6.11.3 ≤ 6.11.*; 6.12 ≤ *
    After
    Linux: ff45899e732e57088985e3a497b1d9100571c0f5 < 87bd909a7014e32790e8c759d5b7694a95778ca5, ee534378f00561207656663d93907583958339ae < ab9e90619b6339becc5415647ae154a9a46a044d, ee534378f00561207656663d93907583958339ae < 2e93bf719462ac6d23c881c8b93e5dc9bf5ab7f5, ee534378f00561207656663d93907583958339ae < ab5d3420a1120950703dbdc33698b28a6ebc3d23, ee534378f00561207656663d93907583958339ae < b4a65d479213fe84ecb14e328271251eebe69492, ee534378f00561207656663d93907583958339ae < 6c24a03a61a245fe34d47582898331fa034b6ccd, 89b60402d43cdab4387dbbf24afebda5cf092ae7, 5.15.155 < 5.15.176, 5.16.10 < 5.17, 5.17 · Fixed: Linux: < 5.17, 5.15.176 ≤ 5.15.*, 6.1.167 ≤ 6.1.*, 6.6.117 ≤ 6.6.*, 6.10.14 ≤ 6.10.*, 6.11.3 ≤ 6.11.*, 6.12 ≤ *
    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-2024-43672↗Vendor CSAF · SUSE Product Security Team↗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-2024-49998 · cve.blacktree.nl