<?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://cve.radiocsirt.org</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>Sat, 10 Oct 2026 22:27:35 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-26831 — net/handshake: Fix handshake_req_destroy_test1</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2024-26831</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;net/handshake: Fix handshake_req_destroy_test1&lt;/p&gt;
&lt;p&gt;Recently, handshake_req_destroy_test1 started failing:&lt;/p&gt;
&lt;p&gt;Expected handshake_req_destroy_test == req, but
    handshake_req_destroy_test == 0000000000000000
    req == 0000000060f99b40
not ok 11 req_destroy works&lt;/p&gt;
&lt;p&gt;This is because &amp;#34;sock_release(sock)&amp;#34; was replaced with &amp;#34;fput(filp)&amp;#34;
to address a memory leak. Note that sock_release() is synchronous
but fput() usually delays the final close and clean-up.&lt;/p&gt;
&lt;p&gt;The delay is not consequential in the other cases that were changed
but handshake_req_destroy_test1 is testing that handshake_req_cancel()
followed by closing the file actually does call the -&amp;gt;hp_destroy
method. Thus the PTR_EQ test at the end has to be sure that the
final close is complete before it checks the pointer.&lt;/p&gt;
&lt;p&gt;We cannot use a completion here because if -&amp;gt;hp_destroy is never
called (ie, there is an API bug) then the test will hang.&lt;/p&gt;
&lt;p&gt;Reported by: Guenter Roeck &amp;lt;linux@roeck-us.net&amp;gt;&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;net/handshake: Fix handshake_req_destroy_test1&lt;/p&gt;
&lt;p&gt;Recently, handshake_req_destroy_test1 started failing:&lt;/p&gt;
&lt;p&gt;Expected handshake_req_destroy_test == req, but
    handshake_req_destroy_test == 0000000000000000
    req == 0000000060f99b40
not ok 11 req_destroy works&lt;/p&gt;
&lt;p&gt;This is because &amp;#34;sock_release(sock)&amp;#34; was replaced with &amp;#34;fput(filp)&amp;#34;
to address a memory leak. Note that sock_release() is synchronous
but fput() usually delays the final close and clean-up.&lt;/p&gt;
&lt;p&gt;The delay is not consequential in the other cases that were changed
but handshake_req_destroy_test1 is testing that handshake_req_cancel()
followed by closing the file actually does call the -&amp;gt;hp_destroy
method. Thus the PTR_EQ test at the end has to be sure that the
final close is complete before it checks the pointer.&lt;/p&gt;
&lt;p&gt;We cannot use a completion here because if -&amp;gt;hp_destroy is never
called (ie, there is an API bug) then the test will hang.&lt;/p&gt;
&lt;p&gt;Reported by: Guenter Roeck &amp;lt;linux@roeck-us.net&amp;gt;&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2024-26831</guid>
    </item>
  </channel>
</rss>
