<?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, 03 Oct 2026 11:24:16 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-02962</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-02962</link>
      <description>bdu:2026-02962</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-02962</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-40305</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2025-40305</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2025-40305</guid>
    </item>
    <item>
      <title>certfr-2025-avi-1082 — De multiples vulnérabilités ont été découvertes dans les produits Microsoft. Elles permettent à un attaquant de provoqu…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-1082</link>
      <description>certfr-2025-avi-1082</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-1082</guid>
    </item>
    <item>
      <title>EUVD-2026-315002</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-315002</link>
      <description>EUVD-2026-315002</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-315002</guid>
    </item>
    <item>
      <title>fkie_cve-2025-40305</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-40305</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;9p/trans_fd: p9_fd_request: kick rx thread if EPOLLIN&lt;/p&gt;
&lt;p&gt;p9_read_work() doesn&amp;#39;t set Rworksched and doesn&amp;#39;t do schedule_work(m-&amp;gt;rq)
if list_empty(&amp;amp;m-&amp;gt;req_list).&lt;/p&gt;
&lt;p&gt;However, if the pipe is full, we need to read more data and this used to
work prior to commit aaec5a95d59615 (&amp;#34;pipe_read: don&amp;#39;t wake up the writer
if the pipe is still full&amp;#34;).&lt;/p&gt;
&lt;p&gt;p9_read_work() does p9_fd_read() -&amp;gt; ... -&amp;gt; anon_pipe_read() which (before
the commit above) triggered the unnecessary wakeup. This wakeup calls
p9_pollwake() which kicks p9_poll_workfn() -&amp;gt; p9_poll_mux(), p9_poll_mux()
will notice EPOLLIN and schedule_work(&amp;amp;m-&amp;gt;rq).&lt;/p&gt;
&lt;p&gt;This no longer happens after the optimization above, change p9_fd_request()
to use p9_poll_mux() instead of only checking for EPOLLOUT.&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;9p/trans_fd: p9_fd_request: kick rx thread if EPOLLIN&lt;/p&gt;
&lt;p&gt;p9_read_work() doesn&amp;#39;t set Rworksched and doesn&amp;#39;t do schedule_work(m-&amp;gt;rq)
if list_empty(&amp;amp;m-&amp;gt;req_list).&lt;/p&gt;
&lt;p&gt;However, if the pipe is full, we need to read more data and this used to
work prior to commit aaec5a95d59615 (&amp;#34;pipe_read: don&amp;#39;t wake up the writer
if the pipe is still full&amp;#34;).&lt;/p&gt;
&lt;p&gt;p9_read_work() does p9_fd_read() -&amp;gt; ... -&amp;gt; anon_pipe_read() which (before
the commit above) triggered the unnecessary wakeup. This wakeup calls
p9_pollwake() which kicks p9_poll_workfn() -&amp;gt; p9_poll_mux(), p9_poll_mux()
will notice EPOLLIN and schedule_work(&amp;amp;m-&amp;gt;rq).&lt;/p&gt;
&lt;p&gt;This no longer happens after the optimization above, change p9_fd_request()
to use p9_poll_mux() instead of only checking for EPOLLOUT.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-40305</guid>
    </item>
    <item>
      <title>GHSA-jr46-vc8c-pm2x</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-jr46-vc8c-pm2x</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;9p/trans_fd: p9_fd_request: kick rx thread if EPOLLIN&lt;/p&gt;
&lt;p&gt;p9_read_work() doesn&amp;#39;t set Rworksched and doesn&amp;#39;t do schedule_work(m-&amp;gt;rq)
if list_empty(&amp;amp;m-&amp;gt;req_list).&lt;/p&gt;
&lt;p&gt;However, if the pipe is full, we need to read more data and this used to
work prior to commit aaec5a95d59615 (&amp;#34;pipe_read: don&amp;#39;t wake up the writer
if the pipe is still full&amp;#34;).&lt;/p&gt;
&lt;p&gt;p9_read_work() does p9_fd_read() -&amp;gt; ... -&amp;gt; anon_pipe_read() which (before
the commit above) triggered the unnecessary wakeup. This wakeup calls
p9_pollwake() which kicks p9_poll_workfn() -&amp;gt; p9_poll_mux(), p9_poll_mux()
will notice EPOLLIN and schedule_work(&amp;amp;m-&amp;gt;rq).&lt;/p&gt;
&lt;p&gt;This no longer happens after the optimization above, change p9_fd_request()
to use p9_poll_mux() instead of only checking for EPOLLOUT.&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;9p/trans_fd: p9_fd_request: kick rx thread if EPOLLIN&lt;/p&gt;
&lt;p&gt;p9_read_work() doesn&amp;#39;t set Rworksched and doesn&amp;#39;t do schedule_work(m-&amp;gt;rq)
if list_empty(&amp;amp;m-&amp;gt;req_list).&lt;/p&gt;
&lt;p&gt;However, if the pipe is full, we need to read more data and this used to
work prior to commit aaec5a95d59615 (&amp;#34;pipe_read: don&amp;#39;t wake up the writer
if the pipe is still full&amp;#34;).&lt;/p&gt;
&lt;p&gt;p9_read_work() does p9_fd_read() -&amp;gt; ... -&amp;gt; anon_pipe_read() which (before
the commit above) triggered the unnecessary wakeup. This wakeup calls
p9_pollwake() which kicks p9_poll_workfn() -&amp;gt; p9_poll_mux(), p9_poll_mux()
will notice EPOLLIN and schedule_work(&amp;amp;m-&amp;gt;rq).&lt;/p&gt;
&lt;p&gt;This no longer happens after the optimization above, change p9_fd_request()
to use p9_poll_mux() instead of only checking for EPOLLOUT.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-jr46-vc8c-pm2x</guid>
    </item>
    <item>
      <title>msrc_CVE-2025-40305 — 9p/trans_fd: p9_fd_request: kick rx thread if EPOLLIN</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2025-40305</link>
      <description>msrc_CVE-2025-40305</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2025-40305</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-40305</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-40305</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 229 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: 9p/trans_fd: p9_fd_request: kick rx thread if EPOLLIN p9_read_work() doesn&amp;#39;t set Rworksched and doesn&amp;#39;t do schedule_work(m-&amp;gt;rq) if list_empty(&amp;amp;m-&amp;gt;req_list). However, if the pipe is full, we need to read more data and this used to work prior to commit aaec5a95d59615 (&amp;#34;pipe_read: don&amp;#39;t wake up the writer if the pipe is still full&amp;#34;). p9_read_work() does p9_fd_read() -&amp;gt; ... -&amp;gt; anon_pipe_read() which (before the commit above) triggered the unnecessary wakeup. This wakeup calls p9_pollwake() which kicks p9_poll_workfn() -&amp;gt; p9_poll_mux(), p9_poll_mux() will notice EPOLLIN and schedule_work(&amp;amp;m-&amp;gt;rq). This no longer happens after the optimization above, change p9_fd_request() to use p9_poll_mux() instead of only checking for EPOLLOUT.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 229 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: 9p/trans_fd: p9_fd_request: kick rx thread if EPOLLIN p9_read_work() doesn&amp;#39;t set Rworksched and doesn&amp;#39;t do schedule_work(m-&amp;gt;rq) if list_empty(&amp;amp;m-&amp;gt;req_list). However, if the pipe is full, we need to read more data and this used to work prior to commit aaec5a95d59615 (&amp;#34;pipe_read: don&amp;#39;t wake up the writer if the pipe is still full&amp;#34;). p9_read_work() does p9_fd_read() -&amp;gt; ... -&amp;gt; anon_pipe_read() which (before the commit above) triggered the unnecessary wakeup. This wakeup calls p9_pollwake() which kicks p9_poll_workfn() -&amp;gt; p9_poll_mux(), p9_poll_mux() will notice EPOLLIN and schedule_work(&amp;amp;m-&amp;gt;rq). This no longer happens after the optimization above, change p9_fd_request() to use p9_poll_mux() instead of only checking for EPOLLOUT.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-40305</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2756 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2756</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen oder weitere, nicht spezifizierte Auswirkungen zu erlangen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen oder weitere, nicht spezifizierte Auswirkungen zu erlangen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2756</guid>
    </item>
  </channel>
</rss>
