<?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 01:09:22 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-35911 — ice: fix memory corruption bug with suspend and rebuild</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-35911</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;ice: fix memory corruption bug with suspend and rebuild&lt;/p&gt;
&lt;p&gt;The ice driver would previously panic after suspend. This is caused
from the driver *only* calling the ice_vsi_free_q_vectors() function by
itself, when it is suspending. Since commit b3e7b3a6ee92 (&amp;#34;ice: prevent
NULL pointer deref during reload&amp;#34;) the driver has zeroed out
num_q_vectors, and only restored it in ice_vsi_cfg_def().&lt;/p&gt;
&lt;p&gt;This further causes the ice_rebuild() function to allocate a zero length
buffer, after which num_q_vectors is updated, and then the new value of
num_q_vectors is used to index into the zero length buffer, which
corrupts memory.&lt;/p&gt;
&lt;p&gt;The fix entails making sure all the code referencing num_q_vectors only
does so after it has been reset via ice_vsi_cfg_def().&lt;/p&gt;
&lt;p&gt;I didn&amp;#39;t perform a full bisect, but I was able to test against 6.1.77
kernel and that ice driver works fine for suspend/resume with no panic,
so sometime since then, this problem was introduced.&lt;/p&gt;
&lt;p&gt;Also clean up an un-needed init of a local variable in the function
being modified.&lt;/p&gt;
&lt;p&gt;PANIC from 6.8.0-rc1:&lt;/p&gt;
&lt;p&gt;[1026674.915596] PM: suspend exit
[1026675.664697] ice 0000:17:00.1: PTP reset successful
[1026675.664707] ice 0000:17:00.1: 2755 msecs passed between update to cached PHC time
[1026675.667660] ice 0000:b1:00.0: PTP reset successful
[1026675.675944] ice 0000:b1:00.0: 2832 msecs passed between update to cached PHC time
[1026677.137733] ixgbe 0000:31:00.0 ens787: NIC Link is Up 1…&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;ice: fix memory corruption bug with suspend and rebuild&lt;/p&gt;
&lt;p&gt;The ice driver would previously panic after suspend. This is caused
from the driver *only* calling the ice_vsi_free_q_vectors() function by
itself, when it is suspending. Since commit b3e7b3a6ee92 (&amp;#34;ice: prevent
NULL pointer deref during reload&amp;#34;) the driver has zeroed out
num_q_vectors, and only restored it in ice_vsi_cfg_def().&lt;/p&gt;
&lt;p&gt;This further causes the ice_rebuild() function to allocate a zero length
buffer, after which num_q_vectors is updated, and then the new value of
num_q_vectors is used to index into the zero length buffer, which
corrupts memory.&lt;/p&gt;
&lt;p&gt;The fix entails making sure all the code referencing num_q_vectors only
does so after it has been reset via ice_vsi_cfg_def().&lt;/p&gt;
&lt;p&gt;I didn&amp;#39;t perform a full bisect, but I was able to test against 6.1.77
kernel and that ice driver works fine for suspend/resume with no panic,
so sometime since then, this problem was introduced.&lt;/p&gt;
&lt;p&gt;Also clean up an un-needed init of a local variable in the function
being modified.&lt;/p&gt;
&lt;p&gt;PANIC from 6.8.0-rc1:&lt;/p&gt;
&lt;p&gt;[1026674.915596] PM: suspend exit
[1026675.664697] ice 0000:17:00.1: PTP reset successful
[1026675.664707] ice 0000:17:00.1: 2755 msecs passed between update to cached PHC time
[1026675.667660] ice 0000:b1:00.0: PTP reset successful
[1026675.675944] ice 0000:b1:00.0: 2832 msecs passed between update to cached PHC time
[1026677.137733] ixgbe 0000:31:00.0 ens787: NIC Link is Up 1…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-35911</guid>
    </item>
  </channel>
</rss>
