<?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>Fri, 02 Oct 2026 11:41:44 +0000</lastBuildDate>
    <item>
      <title>bdu:2024-10595</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-10595</link>
      <description>bdu:2024-10595</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-10595</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0496 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2024-avi-0496</link>
      <description>certfr-2024-avi-0496</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0496</guid>
    </item>
    <item>
      <title>EUVD-2026-344499</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-344499</link>
      <description>EUVD-2026-344499</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-344499</guid>
    </item>
    <item>
      <title>fkie_cve-2021-47496</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-47496</link>
      <description>&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;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/fkie_cve-2021-47496</guid>
    </item>
    <item>
      <title>GHSA-c425-5ghg-6j48</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-c425-5ghg-6j48</link>
      <description>&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;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/ghsa-c425-5ghg-6j48</guid>
    </item>
    <item>
      <title>OESA-2024-1736 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2024-1736</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP4: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
PCI: aardvark: Fix kernel panic during PIO transfer&#13;
&#13;
Trying to start a new PIO transfer by writing value 0 in PIO_START register
when previous transfer has not yet completed (which is indicated by value 1
in PIO_START) causes an External Abort on CPU, which results in kernel
panic:&#13;
&#13;
    SError Interrupt on CPU0, code 0xbf000002 -- SError
    Kernel panic - not syncing: Asynchronous SError Interrupt&#13;
&#13;
To prevent kernel panic, it is required to reject a new PIO transfer when
previous one has not finished yet.&#13;
&#13;
If previous PIO transfer is not finished yet, the kernel may issue a new
PIO request only if the previous PIO transfer timed out.&#13;
&#13;
In the past the root cause of this issue was incorrectly identified (as it
often happens during link retraining or after link down event) and special
hack was implemented in Trusted Firmware to catch all SError events in EL3,
to ignore errors with code 0xbf000002 and not forwarding any other errors
to kernel and instead throw panic from EL3 Trusted Firmware handler.&#13;
&#13;
Links to discussion and patches about this issue:
https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git/commit/?id=3c7dcdac5c50
https://lore.kernel.org/linux-pci/20190316161243.29517-1-repk@triplefau.lt/
https://lore.kernel.org/linux-pci/971be151d24312cc533989a64bd454b4@www.loen.fr/
https://review.trustedfirmware.org/c…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP4: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
PCI: aardvark: Fix kernel panic during PIO transfer&#13;
&#13;
Trying to start a new PIO transfer by writing value 0 in PIO_START register
when previous transfer has not yet completed (which is indicated by value 1
in PIO_START) causes an External Abort on CPU, which results in kernel
panic:&#13;
&#13;
    SError Interrupt on CPU0, code 0xbf000002 -- SError
    Kernel panic - not syncing: Asynchronous SError Interrupt&#13;
&#13;
To prevent kernel panic, it is required to reject a new PIO transfer when
previous one has not finished yet.&#13;
&#13;
If previous PIO transfer is not finished yet, the kernel may issue a new
PIO request only if the previous PIO transfer timed out.&#13;
&#13;
In the past the root cause of this issue was incorrectly identified (as it
often happens during link retraining or after link down event) and special
hack was implemented in Trusted Firmware to catch all SError events in EL3,
to ignore errors with code 0xbf000002 and not forwarding any other errors
to kernel and instead throw panic from EL3 Trusted Firmware handler.&#13;
&#13;
Links to discussion and patches about this issue:
https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git/commit/?id=3c7dcdac5c50
https://lore.kernel.org/linux-pci/20190316161243.29517-1-repk@triplefau.lt/
https://lore.kernel.org/linux-pci/971be151d24312cc533989a64bd454b4@www.loen.fr/
https://review.trustedfirmware.org/c…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2024-1736</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:1979-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:1979-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2024:1979-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2021-47496</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-47496</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-gcp-5.4, Ubuntu:18.04:LTS: linux-hwe-5.4, Ubuntu:18.04:LTS: linux-oracle-5.4, Ubuntu:18.04:LTS: linux-raspi-5.4, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure and 81 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net/tls: Fix flipped sign in tls_err_abort() calls 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,     [kworker]     tls_encrypt_done(..., err=&amp;lt;negative error from crypto request&amp;gt;)       tls_err_abort(.., err)         sk-&amp;gt;sk_err = err;     [task]     splice_from_pipe_feed       ...         tls_sw_do_sendpage           if (sk-&amp;gt;sk_err) {             ret = -sk-&amp;gt;sk_err;  // ret is positive     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() 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; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-gcp-5.4, Ubuntu:18.04:LTS: linux-hwe-5.4, Ubuntu:18.04:LTS: linux-oracle-5.4, Ubuntu:18.04:LTS: linux-raspi-5.4, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure and 81 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net/tls: Fix flipped sign in tls_err_abort() calls 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,     [kworker]     tls_encrypt_done(..., err=&amp;lt;negative error from crypto request&amp;gt;)       tls_err_abort(.., err)         sk-&amp;gt;sk_err = err;     [task]     splice_from_pipe_feed       ...         tls_sw_do_sendpage           if (sk-&amp;gt;sk_err) {             ret = -sk-&amp;gt;sk_err;  // ret is positive     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() 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/ubuntu-cve-2021-47496</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-1197 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service und unspezifische Angriffe</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1197</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen oder unspezifische Angriffe durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen oder unspezifische Angriffe durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1197</guid>
    </item>
  </channel>
</rss>
