CVE-2024-49998: Linux kernel · net: dsa: improve shutdown sequence
Affects Linux kernelSource GCVE Database
Not known to be exploited.
Data as of 10 Nov 2026, 14:49 UTC
Rated Medium by Threat Radar's AI analysis · No CVSS score from NVD or the CNA
Thin evidence
One scorer or noneExploitation evidence
Disclosed: evidence found.
CVE published 21 Oct 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux | Affected
| Fixed in– |
AI-suggested
A fix is available that improves the shutdown sequence in the lan9303 DSA driver by properly closing the conduit interface and stopping the phylink state machine synchronously. Users should upgrade to fixed Linux kernel versions that include this patch. Until then, avoid scenarios that trigger device shutdown sequences on affected versions. No additional mitigations are specified.
Description
CVE-2024-49998 addresses two shutdown sequence issues in the Linux kernel's Distributed Switch Architecture (DSA) subsystem, specifically affecting the lan9303 driver. The first issue involves the lan9303 driver calling dev_get_drvdata() at arbitrary runtime without stopping the phy_state_machine(), potentially causing use-after-free or null pointer dereference during shutdown. The second issue is a race condition where dsa_ptr is set to NULL concurrently with packet receive processing, leading to unsafe dereferences without proper locking. Both problems are mitigated by properly closing the conduit interface during shutdown, ensuring the phylink state machine stops and no further driver calls occur. The fix involves improving the shutdown sequence to prevent these race conditions and unsafe accesses.
References
- git.kernel.org/stable/c/87bd909a7014e32790e8c759d5b7694a95778ca5 (opens in a new tab)
- git.kernel.org/stable/c/ab9e90619b6339becc5415647ae154a9a46a044d (opens in a new tab)
- git.kernel.org/stable/c/2e93bf719462ac6d23c881c8b93e5dc9bf5ab7f5 (opens in a new tab)
- git.kernel.org/stable/c/ab5d3420a1120950703dbdc33698b28a6ebc3d23 (opens in a new tab)
- git.kernel.org/stable/c/b4a65d479213fe84ecb14e328271251eebe69492 (opens in a new tab)
- git.kernel.org/stable/c/6c24a03a61a245fe34d47582898331fa034b6ccd (opens in a new tab)
- cert-portal.siemens.com/productcert/html/ssa-082556.html (opens in a new tab)
- cert-portal.siemens.com/productcert/html/ssa-019113.html (opens in a new tab)
- cert-portal.siemens.com/productcert/html/ssa-457936.html (opens in a new tab)
- cert-portal.siemens.com/productcert/html/ssa-784472.html (opens in a new tab)