<?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 17:49:38 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-53388</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-53388</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-53388</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0957 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Certaines d'entre elles permettent à…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0957</link>
      <description>certfr-2026-avi-0957</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0957</guid>
    </item>
    <item>
      <title>EUVD-2026-353100</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-353100</link>
      <description>EUVD-2026-353100</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-353100</guid>
    </item>
    <item>
      <title>fkie_cve-2026-53388</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-53388</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;fuse: re-lock request before replacing page cache folio&lt;/p&gt;
&lt;p&gt;fuse_try_move_folio() unlocks the request on entry but does not
re-lock it on the success path. This means fuse_chan_abort() can end the
request and free the fuse_io_args (eg fuse_readpages_end()) while the
subsequent copy chain logic after fuse_try_move_folio() accesses the
fuse_io_args, leading to use-after-free issues.&lt;/p&gt;
&lt;p&gt;Fix this by calling lock_request() before replace_page_cache_folio().
This ensures the request is locked on the success path which will
prevent the fuse_io_args from being freed while the later copying logic
runs, and also ensures that the ap-&amp;gt;folios[i]-&amp;gt;mapping is never null
since ap-&amp;gt;folios[i] will always point to the newfolio after
replace_page_cache_folio().&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;fuse: re-lock request before replacing page cache folio&lt;/p&gt;
&lt;p&gt;fuse_try_move_folio() unlocks the request on entry but does not
re-lock it on the success path. This means fuse_chan_abort() can end the
request and free the fuse_io_args (eg fuse_readpages_end()) while the
subsequent copy chain logic after fuse_try_move_folio() accesses the
fuse_io_args, leading to use-after-free issues.&lt;/p&gt;
&lt;p&gt;Fix this by calling lock_request() before replace_page_cache_folio().
This ensures the request is locked on the success path which will
prevent the fuse_io_args from being freed while the later copying logic
runs, and also ensures that the ap-&amp;gt;folios[i]-&amp;gt;mapping is never null
since ap-&amp;gt;folios[i] will always point to the newfolio after
replace_page_cache_folio().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-53388</guid>
    </item>
    <item>
      <title>GHSA-45w6-5frg-3vfq</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-45w6-5frg-3vfq</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;fuse: re-lock request before replacing page cache folio&lt;/p&gt;
&lt;p&gt;fuse_try_move_folio() unlocks the request on entry but does not
re-lock it on the success path. This means fuse_chan_abort() can end the
request and free the fuse_io_args (eg fuse_readpages_end()) while the
subsequent copy chain logic after fuse_try_move_folio() accesses the
fuse_io_args, leading to use-after-free issues.&lt;/p&gt;
&lt;p&gt;Fix this by calling lock_request() before replace_page_cache_folio().
This ensures the request is locked on the success path which will
prevent the fuse_io_args from being freed while the later copying logic
runs, and also ensures that the ap-&amp;gt;folios[i]-&amp;gt;mapping is never null
since ap-&amp;gt;folios[i] will always point to the newfolio after
replace_page_cache_folio().&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;fuse: re-lock request before replacing page cache folio&lt;/p&gt;
&lt;p&gt;fuse_try_move_folio() unlocks the request on entry but does not
re-lock it on the success path. This means fuse_chan_abort() can end the
request and free the fuse_io_args (eg fuse_readpages_end()) while the
subsequent copy chain logic after fuse_try_move_folio() accesses the
fuse_io_args, leading to use-after-free issues.&lt;/p&gt;
&lt;p&gt;Fix this by calling lock_request() before replace_page_cache_folio().
This ensures the request is locked on the success path which will
prevent the fuse_io_args from being freed while the later copying logic
runs, and also ensures that the ap-&amp;gt;folios[i]-&amp;gt;mapping is never null
since ap-&amp;gt;folios[i] will always point to the newfolio after
replace_page_cache_folio().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-45w6-5frg-3vfq</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-53388 — fuse: re-lock request before replacing page cache folio</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-53388</link>
      <description>msrc_CVE-2026-53388</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-53388</guid>
    </item>
    <item>
      <title>OESA-2026-3302 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2026-3302</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):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;inet: RAW sockets using IPPROTO_RAW MUST drop incoming ICMP&lt;/p&gt;
&lt;p&gt;Yizhou Zhao reported that simply having one RAW socket on protocol
IPPROTO_RAW (255) was dangerous.&lt;/p&gt;
&lt;p&gt;socket(AF_INET, SOCK_RAW, 255);&lt;/p&gt;
&lt;p&gt;A malicious incoming ICMP packet can set the protocol field to 255
and match this socket, leading to FNHE cache changes.&lt;/p&gt;
&lt;p&gt;inner = IP(src=&amp;amp;quot;192.168.2.1&amp;amp;quot;, dst=&amp;amp;quot;8.8.8.8&amp;amp;quot;, proto=255)/Raw(&amp;amp;quot;TEST&amp;amp;quot;)
pkt = IP(src=&amp;amp;quot;192.168.1.1&amp;amp;quot;, dst=&amp;amp;quot;192.168.2.1&amp;amp;quot;)/ICMP(type=3, code=4, nexthopmtu=576)/inner&lt;/p&gt;
&lt;p&gt;&amp;amp;quot;man 7 raw&amp;amp;quot; states:&lt;/p&gt;
&lt;p&gt;A protocol of IPPROTO_RAW implies enabled IP_HDRINCL and is able
  to send any IP protocol that is specified in the passed header.
  Receiving of all IP protocols via IPPROTO_RAW is not possible
  using raw sockets.&lt;/p&gt;
&lt;p&gt;Make sure we drop these malicious packets.(CVE-2026-46266)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;netfilter: xt_policy: fix strict mode inbound policy matching&lt;/p&gt;
&lt;p&gt;match_policy_in() walks sec_path entries from the last transform to the
first one, but strict policy matching needs to consume info-&amp;amp;gt;pol[] in
the same forward order as the rule layout.&lt;/p&gt;
&lt;p&gt;Derive the strict-match policy position from the number of transforms
already consumed so that multi-element inbound rules are matched
consistently.(CVE-2026-52920)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the follow…&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):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;inet: RAW sockets using IPPROTO_RAW MUST drop incoming ICMP&lt;/p&gt;
&lt;p&gt;Yizhou Zhao reported that simply having one RAW socket on protocol
IPPROTO_RAW (255) was dangerous.&lt;/p&gt;
&lt;p&gt;socket(AF_INET, SOCK_RAW, 255);&lt;/p&gt;
&lt;p&gt;A malicious incoming ICMP packet can set the protocol field to 255
and match this socket, leading to FNHE cache changes.&lt;/p&gt;
&lt;p&gt;inner = IP(src=&amp;amp;quot;192.168.2.1&amp;amp;quot;, dst=&amp;amp;quot;8.8.8.8&amp;amp;quot;, proto=255)/Raw(&amp;amp;quot;TEST&amp;amp;quot;)
pkt = IP(src=&amp;amp;quot;192.168.1.1&amp;amp;quot;, dst=&amp;amp;quot;192.168.2.1&amp;amp;quot;)/ICMP(type=3, code=4, nexthopmtu=576)/inner&lt;/p&gt;
&lt;p&gt;&amp;amp;quot;man 7 raw&amp;amp;quot; states:&lt;/p&gt;
&lt;p&gt;A protocol of IPPROTO_RAW implies enabled IP_HDRINCL and is able
  to send any IP protocol that is specified in the passed header.
  Receiving of all IP protocols via IPPROTO_RAW is not possible
  using raw sockets.&lt;/p&gt;
&lt;p&gt;Make sure we drop these malicious packets.(CVE-2026-46266)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;netfilter: xt_policy: fix strict mode inbound policy matching&lt;/p&gt;
&lt;p&gt;match_policy_in() walks sec_path entries from the last transform to the
first one, but strict policy matching needs to consume info-&amp;amp;gt;pol[] in
the same forward order as the rule layout.&lt;/p&gt;
&lt;p&gt;Derive the strict-match policy position from the number of transforms
already consumed so that multi-element inbound rules are matched
consistently.(CVE-2026-52920)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the follow…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2026-3302</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:11339-1 — kernel-devel-7.1.4-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:11339-1</link>
      <description>&lt;p&gt;kernel-devel-7.1.4-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel-devel-7.1.4-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:11339-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:23066-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:23066-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-2026:23066-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-53388</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-53388</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 246 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: fuse: re-lock request before replacing page cache folio fuse_try_move_folio() unlocks the request on entry but does not re-lock it on the success path. This means fuse_chan_abort() can end the request and free the fuse_io_args (eg fuse_readpages_end()) while the subsequent copy chain logic after fuse_try_move_folio() accesses the fuse_io_args, leading to use-after-free issues. Fix this by calling lock_request() before replace_page_cache_folio(). This ensures the request is locked on the success path which will prevent the fuse_io_args from being freed while the later copying logic runs, and also ensures that the ap-&amp;gt;folios[i]-&amp;gt;mapping is never null since ap-&amp;gt;folios[i] will always point to the newfolio after replace_page_cache_folio().&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 246 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: fuse: re-lock request before replacing page cache folio fuse_try_move_folio() unlocks the request on entry but does not re-lock it on the success path. This means fuse_chan_abort() can end the request and free the fuse_io_args (eg fuse_readpages_end()) while the subsequent copy chain logic after fuse_try_move_folio() accesses the fuse_io_args, leading to use-after-free issues. Fix this by calling lock_request() before replace_page_cache_folio(). This ensures the request is locked on the success path which will prevent the fuse_io_args from being freed while the later copying logic runs, and also ensures that the ap-&amp;gt;folios[i]-&amp;gt;mapping is never null since ap-&amp;gt;folios[i] will always point to the newfolio after replace_page_cache_folio().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-53388</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2403 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2403</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder vertrauliche Informationen offenzulegen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder vertrauliche Informationen offenzulegen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2403</guid>
    </item>
  </channel>
</rss>
