<?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>Tue, 29 Sep 2026 07:33:14 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-23240 — tls: Fix race condition in tls_sw_cancel_work_tx()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-23240</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;tls: Fix race condition in tls_sw_cancel_work_tx()&lt;/p&gt;
&lt;p&gt;This issue was discovered during a code audit.&lt;/p&gt;
&lt;p&gt;After cancel_delayed_work_sync() is called from tls_sk_proto_close(),
tx_work_handler() can still be scheduled from paths such as the
Delayed ACK handler or ksoftirqd.
As a result, the tx_work_handler() worker may dereference a freed
TLS object.&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;tls_sk_proto_close()
  tls_sw_cancel_work_tx()
                                 tls_write_space()
                                   tls_sw_write_space()
                                     if (!test_and_set_bit(BIT_TX_SCHEDULED, &amp;amp;tx_ctx-&amp;gt;tx_bitmask))
    set_bit(BIT_TX_SCHEDULED, &amp;amp;ctx-&amp;gt;tx_bitmask);
    cancel_delayed_work_sync(&amp;amp;ctx-&amp;gt;tx_work.work);
                                     schedule_delayed_work(&amp;amp;tx_ctx-&amp;gt;tx_work.work, 0);&lt;/p&gt;
&lt;p&gt;To prevent this race condition, cancel_delayed_work_sync() is
replaced with disable_delayed_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;tls: Fix race condition in tls_sw_cancel_work_tx()&lt;/p&gt;
&lt;p&gt;This issue was discovered during a code audit.&lt;/p&gt;
&lt;p&gt;After cancel_delayed_work_sync() is called from tls_sk_proto_close(),
tx_work_handler() can still be scheduled from paths such as the
Delayed ACK handler or ksoftirqd.
As a result, the tx_work_handler() worker may dereference a freed
TLS object.&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;tls_sk_proto_close()
  tls_sw_cancel_work_tx()
                                 tls_write_space()
                                   tls_sw_write_space()
                                     if (!test_and_set_bit(BIT_TX_SCHEDULED, &amp;amp;tx_ctx-&amp;gt;tx_bitmask))
    set_bit(BIT_TX_SCHEDULED, &amp;amp;ctx-&amp;gt;tx_bitmask);
    cancel_delayed_work_sync(&amp;amp;ctx-&amp;gt;tx_work.work);
                                     schedule_delayed_work(&amp;amp;tx_ctx-&amp;gt;tx_work.work, 0);&lt;/p&gt;
&lt;p&gt;To prevent this race condition, cancel_delayed_work_sync() is
replaced with disable_delayed_work_sync().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-23240</guid>
    </item>
  </channel>
</rss>
