<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Wed, 30 Sep 2026 06:28:43 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-46679 — ethtool: check device is present when getting link settings</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-46679</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens RUGGEDCOM RST2428P, Siemens SCALANCE XC-300/XR-300/XC-400/XR-500WG/XR-500 family, Siemens SCALANCE XCM-/XRM-/XCH-/XRH-300 family, Siemens SIMATIC S7-1500 TM MFP - GNU/Linux subsystem&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ethtool: check device is present when getting link settings&lt;/p&gt;
&lt;p&gt;A sysfs reader can race with a device reset or removal, attempting to
read device state when the device is not actually present. eg:&lt;/p&gt;
&lt;p&gt;[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&lt;/p&gt;
&lt;p&gt;crash&amp;gt; struct net_device.state ffff9a9d21336000
    state = 5,&lt;/p&gt;
&lt;p&gt;state 5 is __LINK_STATE_START (0b1) and __LINK_STATE_NOCARRIER (0b100).
The device is not present, note lack of __LINK_STATE_PRESENT (0b10).&lt;/p&gt;
&lt;p&gt;This is the same sort of panic as observed in commit 4224cfd7fb65
(&amp;#34;net-sysfs: add check for netdevice being present to speed_show&amp;#34;).&lt;/p&gt;
&lt;p&gt;There are many other callers of __ethtool_get_link_ksettings() which
don&amp;#39;t have a device presence check.&lt;/p&gt;
&lt;p&gt;Move this check into ethtool to protect all callers.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens RUGGEDCOM RST2428P, Siemens SCALANCE XC-300/XR-300/XC-400/XR-500WG/XR-500 family, Siemens SCALANCE XCM-/XRM-/XCH-/XRH-300 family, Siemens SIMATIC S7-1500 TM MFP - GNU/Linux subsystem&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ethtool: check device is present when getting link settings&lt;/p&gt;
&lt;p&gt;A sysfs reader can race with a device reset or removal, attempting to
read device state when the device is not actually present. eg:&lt;/p&gt;
&lt;p&gt;[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&lt;/p&gt;
&lt;p&gt;crash&amp;gt; struct net_device.state ffff9a9d21336000
    state = 5,&lt;/p&gt;
&lt;p&gt;state 5 is __LINK_STATE_START (0b1) and __LINK_STATE_NOCARRIER (0b100).
The device is not present, note lack of __LINK_STATE_PRESENT (0b10).&lt;/p&gt;
&lt;p&gt;This is the same sort of panic as observed in commit 4224cfd7fb65
(&amp;#34;net-sysfs: add check for netdevice being present to speed_show&amp;#34;).&lt;/p&gt;
&lt;p&gt;There are many other callers of __ethtool_get_link_ksettings() which
don&amp;#39;t have a device presence check.&lt;/p&gt;
&lt;p&gt;Move this check into ethtool to protect all callers.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-46679</guid>
    </item>
  </channel>
</rss>
