LiveActive security incident?Get immediate response
CVE Record

CVE-2024-46679: ethtool: check device is present when getting link settings

In the Linux kernel, the following vulnerability has been resolved: ethtool: check device is present when getting link settings A sysfs reader can race with a device reset or removal, attempting to read device state when the device is not actually present. eg: [exception RIP: qed_get_current_link+17] #8 [ffffb9e4f2907c48] qede_get_link_ksettings at ffffffffc07a994a [qede] #9 [ffffb9e4f2907cd8] __rh_call_get_link_ksettings at ffffffff992b01a3 #10 [ffffb9e4f2907d38] __ethtool_get_link_ksettings at ffffffff992b04e4 #11 [ffffb9e4f2907d90] duplex_show at ffffffff99260300 #12 [ffffb9e4f2907e38] dev_attr_show at ffffffff9905a01c #13 [ffffb9e4f2907e50] sysfs_kf_seq_show at ffffffff98e0145b #14 [ffffb9e4f2907e68] seq_read at ffffffff98d902e3 #15 [ffffb9e4f2907ec8] vfs_read at ffffffff98d657d1 #16 [ffffb9e4f2907f00] ksys_read at ffffffff98d65c3f #17 [ffffb9e4f2907f38] do_syscall_64 at ffffffff98a052fb crash> struct net_device.state ffff9a9d21336000 state = 5, state 5 is __LINK_STATE_START (0b1) and __LINK_STATE_NOCARRIER (0b100). The device is not present, note lack of __LINK_STATE_PRESENT (0b10). This is the same sort of panic as observed in commit 4224cfd7fb65 ("net-sysfs: add check for netdevice being present to speed_show"). There are many other callers of __ethtool_get_link_ksettings() which don't have a device presence check. Move this check into ethtool to protect all callers.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2024-46679 is a Linux kernel reliability flaw. A system reading network device settings through sysfs can race with device reset or removal and trigger a kernel panic. The business concern is unexpected host or appliance downtime, not confirmed data theft or remote compromise from the supplied evidence.

Executive priority

Schedule remediation through normal kernel patching, with higher priority for infrastructure where a kernel panic would interrupt critical services. There is no supplied evidence of active exploitation, but downtime impact can be material on production or industrial systems.

Technical view

The flaw is in Linux ethtool link settings handling. Callers of __ethtool_get_link_ksettings() could read network device state without verifying __LINK_STATE_PRESENT. During reset or removal, this can dereference unavailable device state and panic. Kernel stable fixes move the presence check into ethtool to protect callers.

Likely exposure

Exposure is likely on Linux systems using affected kernel versions, especially hosts or appliances with network device resets, removals, hotplug, driver faults, or management reads of sysfs network attributes. Debian and Siemens references indicate downstream product impact, but exact product applicability requires vendor-specific advisory review.

Exploitation context

The bundle does not show CISA KEV listing, public exploitation, or a remote attack path. The described trigger is a race between a sysfs reader and network device reset or removal. Treat it primarily as a local or operational denial-of-service risk unless vendor guidance says otherwise.

Researcher notes

Key evidence is the upstream kernel fix rationale and affected-version metadata. The record lacks CVSS, CWE, and exploitability detail. Analysis should avoid broadening impact beyond kernel panic/availability unless corroborated by downstream advisories or additional vendor statements.

Mitigation direction

  • Update to a Linux kernel containing the stable ethtool presence-check fix.
  • Apply relevant Debian or vendor-provided kernel/security updates where applicable.
  • Review Siemens advisories for affected industrial products and vendor-specific remediation.
  • Reduce unnecessary local access to sysfs network attributes on shared systems.
  • Prioritize systems where network device resets or hotplug events are common.

Validation and detection

  • Inventory Linux kernel versions across servers, appliances, and embedded systems.
  • Compare installed kernels against vendor advisories and patched stable releases.
  • Check whether Debian LTS or product advisories apply to your deployed platforms.
  • Review crash logs for panics involving ethtool, qede, sysfs, or link ksettings.
  • Confirm remediation by verifying the updated kernel package or vendor firmware level.
Prepared
Confidence
medium
Sources
12

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-46679 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
3ADP providers
13Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container
siemens-SADPADP container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxd519e17e2d01a0ee9abe083019532061b4438065, d519e17e2d01a0ee9abe083019532061b4438065, d519e17e2d01a0ee9abe083019532061b4438065, d519e17e2d01a0ee9abe083019532061b4438065, d519e17e2d01a0ee9abe083019532061b4438065, d519e17e2d01a0ee9abe083019532061b4438065, d519e17e2d01a0ee9abe083019532061b4438065unaffected
LinuxLinux2.6.33, 0, 5.4.283, 5.10.225, 5.15.166, 6.1.108, 6.6.49, 6.10.8, 6.11affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.