<?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 08:37:48 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-23239 — espintcp: Fix race condition in espintcp_close()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-23239</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;espintcp: Fix race condition in espintcp_close()&lt;/p&gt;
&lt;p&gt;This issue was discovered during a code audit.&lt;/p&gt;
&lt;p&gt;After cancel_work_sync() is called from espintcp_close(),
espintcp_tx_work() can still be scheduled from paths such as
the Delayed ACK handler or ksoftirqd.
As a result, the espintcp_tx_work() worker may dereference a
freed espintcp ctx or sk.&lt;/p&gt;
&lt;p&gt;The following is a simple race scenario:&lt;/p&gt;
&lt;p&gt;cpu0                             cpu1&lt;/p&gt;
&lt;p&gt;espintcp_close()
    cancel_work_sync(&amp;amp;ctx-&amp;gt;work);
                                     espintcp_write_space()
                                       schedule_work(&amp;amp;ctx-&amp;gt;work);&lt;/p&gt;
&lt;p&gt;To prevent this race condition, cancel_work_sync() is
replaced with disable_work_sync().&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;espintcp: Fix race condition in espintcp_close()&lt;/p&gt;
&lt;p&gt;This issue was discovered during a code audit.&lt;/p&gt;
&lt;p&gt;After cancel_work_sync() is called from espintcp_close(),
espintcp_tx_work() can still be scheduled from paths such as
the Delayed ACK handler or ksoftirqd.
As a result, the espintcp_tx_work() worker may dereference a
freed espintcp ctx or sk.&lt;/p&gt;
&lt;p&gt;The following is a simple race scenario:&lt;/p&gt;
&lt;p&gt;cpu0                             cpu1&lt;/p&gt;
&lt;p&gt;espintcp_close()
    cancel_work_sync(&amp;amp;ctx-&amp;gt;work);
                                     espintcp_write_space()
                                       schedule_work(&amp;amp;ctx-&amp;gt;work);&lt;/p&gt;
&lt;p&gt;To prevent this race condition, cancel_work_sync() is
replaced with disable_work_sync().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-23239</guid>
    </item>
  </channel>
</rss>
