<?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>Wed, 07 Oct 2026 20:14:13 +0000</lastBuildDate>
    <item>
      <title>CVE-2021-47496 — net/tls: Fix flipped sign in tls_err_abort() calls</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2021-47496</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/tls: Fix flipped sign in tls_err_abort() calls&lt;/p&gt;
&lt;p&gt;sk-&amp;gt;sk_err appears to expect a positive value, a convention that ktls
doesn&amp;#39;t always follow and that leads to memory corruption in other code.
For instance,&lt;/p&gt;
&lt;p&gt;[kworker]
    tls_encrypt_done(..., err=&amp;lt;negative error from crypto request&amp;gt;)
      tls_err_abort(.., err)
        sk-&amp;gt;sk_err = err;&lt;/p&gt;
&lt;p&gt;[task]
    splice_from_pipe_feed
      ...
        tls_sw_do_sendpage
          if (sk-&amp;gt;sk_err) {
            ret = -sk-&amp;gt;sk_err;  // ret is positive&lt;/p&gt;
&lt;p&gt;splice_from_pipe_feed (continued)
      ret = actor(...)  // ret is still positive and interpreted as bytes
                        // written, resulting in underflow of buf-&amp;gt;len and
                        // sd-&amp;gt;len, leading to huge buf-&amp;gt;offset and bogus
                        // addresses computed in later calls to actor()&lt;/p&gt;
&lt;p&gt;Fix all tls_err_abort() callers to pass a negative error code
consistently and centralize the error-prone sign flip there, throwing in
a warning to catch future misuse and uninlining the function so it
really does only warn once.&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/tls: Fix flipped sign in tls_err_abort() calls&lt;/p&gt;
&lt;p&gt;sk-&amp;gt;sk_err appears to expect a positive value, a convention that ktls
doesn&amp;#39;t always follow and that leads to memory corruption in other code.
For instance,&lt;/p&gt;
&lt;p&gt;[kworker]
    tls_encrypt_done(..., err=&amp;lt;negative error from crypto request&amp;gt;)
      tls_err_abort(.., err)
        sk-&amp;gt;sk_err = err;&lt;/p&gt;
&lt;p&gt;[task]
    splice_from_pipe_feed
      ...
        tls_sw_do_sendpage
          if (sk-&amp;gt;sk_err) {
            ret = -sk-&amp;gt;sk_err;  // ret is positive&lt;/p&gt;
&lt;p&gt;splice_from_pipe_feed (continued)
      ret = actor(...)  // ret is still positive and interpreted as bytes
                        // written, resulting in underflow of buf-&amp;gt;len and
                        // sd-&amp;gt;len, leading to huge buf-&amp;gt;offset and bogus
                        // addresses computed in later calls to actor()&lt;/p&gt;
&lt;p&gt;Fix all tls_err_abort() callers to pass a negative error code
consistently and centralize the error-prone sign flip there, throwing in
a warning to catch future misuse and uninlining the function so it
really does only warn once.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2021-47496</guid>
    </item>
  </channel>
</rss>
