<?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 15:50:55 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-36887 — e1000e: change usleep_range to udelay in PHY mdic access</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-36887</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;e1000e: change usleep_range to udelay in PHY mdic access&lt;/p&gt;
&lt;p&gt;This is a partial revert of commit 6dbdd4de0362 (&amp;#34;e1000e: Workaround
for sporadic MDI error on Meteor Lake systems&amp;#34;). The referenced commit
used usleep_range inside the PHY access routines, which are sometimes
called from an atomic context. This can lead to a kernel panic in some
scenarios, such as cable disconnection and reconnection on vPro systems.&lt;/p&gt;
&lt;p&gt;Solve this by changing the usleep_range calls back to udelay.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;e1000e: change usleep_range to udelay in PHY mdic access&lt;/p&gt;
&lt;p&gt;This is a partial revert of commit 6dbdd4de0362 (&amp;#34;e1000e: Workaround
for sporadic MDI error on Meteor Lake systems&amp;#34;). The referenced commit
used usleep_range inside the PHY access routines, which are sometimes
called from an atomic context. This can lead to a kernel panic in some
scenarios, such as cable disconnection and reconnection on vPro systems.&lt;/p&gt;
&lt;p&gt;Solve this by changing the usleep_range calls back to udelay.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-36887</guid>
    </item>
  </channel>
</rss>
