<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-03T06:50:33.168134+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bell-cve-2026-53388</id>
    <title>BELL-CVE-2026-53388</title>
    <updated>2026-10-03T06:50:35.110245+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bell-cve-2026-53388"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0957</id>
    <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>
    <updated>2026-10-03T06:50:35.110355+00:00</updated>
    <content>certfr-2026-avi-0957</content>
    <link href="https://cve.radiocsirt.org/vuln/certfr-2026-avi-0957"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-353100</id>
    <title>EUVD-2026-353100</title>
    <updated>2026-10-03T06:50:35.110379+00:00</updated>
    <content>EUVD-2026-353100</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-353100"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-53388</id>
    <title>fkie_cve-2026-53388</title>
    <updated>2026-10-03T06:50:35.110392+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>fuse: re-lock request before replacing page cache folio</p>
<p>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.</p>
<p>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-&gt;folios[i]-&gt;mapping is never null
since ap-&gt;folios[i] will always point to the newfolio after
replace_page_cache_folio().</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-53388"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-45w6-5frg-3vfq</id>
    <title>GHSA-45w6-5frg-3vfq</title>
    <updated>2026-10-03T06:50:35.110427+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>fuse: re-lock request before replacing page cache folio</p>
<p>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.</p>
<p>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-&gt;folios[i]-&gt;mapping is never null
since ap-&gt;folios[i] will always point to the newfolio after
replace_page_cache_folio().</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-45w6-5frg-3vfq"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/msrc_cve-2026-53388</id>
    <title>msrc_CVE-2026-53388 — fuse: re-lock request before replacing page cache folio</title>
    <updated>2026-10-03T06:50:35.110449+00:00</updated>
    <content>msrc_CVE-2026-53388</content>
    <link href="https://cve.radiocsirt.org/vuln/msrc_cve-2026-53388"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/oesa-2026-3302</id>
    <title>OESA-2026-3302 — kernel security update</title>
    <updated>2026-10-03T06:50:35.110467+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openEuler:20.03-LTS-SP4: kernel</p>
<p>The Linux Kernel, the operating system core itself.

Security Fix(es):</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>inet: RAW sockets using IPPROTO_RAW MUST drop incoming ICMP</p>
<p>Yizhou Zhao reported that simply having one RAW socket on protocol
IPPROTO_RAW (255) was dangerous.</p>
<p>socket(AF_INET, SOCK_RAW, 255);</p>
<p>A malicious incoming ICMP packet can set the protocol field to 255
and match this socket, leading to FNHE cache changes.</p>
<p>inner = IP(src=&amp;quot;192.168.2.1&amp;quot;, dst=&amp;quot;8.8.8.8&amp;quot;, proto=255)/Raw(&amp;quot;TEST&amp;quot;)
pkt = IP(src=&amp;quot;192.168.1.1&amp;quot;, dst=&amp;quot;192.168.2.1&amp;quot;)/ICMP(type=3, code=4, nexthopmtu=576)/inner</p>
<p>&amp;quot;man 7 raw&amp;quot; states:</p>
<p>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.</p>
<p>Make sure we drop these malicious packets.(CVE-2026-46266)</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>netfilter: xt_policy: fix strict mode inbound policy matching</p>
<p>match_policy_in() walks sec_path entries from the last transform to the
first one, but strict policy matching needs to consume info-&amp;gt;pol[] in
the same forward order as the rule layout.</p>
<p>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)</p>
<p>In the Linux kernel, the follow…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/oesa-2026-3302"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/opensuse-su-2026:11339-1</id>
    <title>openSUSE-SU-2026:11339-1 — kernel-devel-7.1.4-1.1 on GA media</title>
    <updated>2026-10-03T06:50:35.110558+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>kernel-devel-7.1.4-1.1 on GA media</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/opensuse-su-2026:11339-1"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/suse-su-2026:23066-1</id>
    <title>SUSE-SU-2026:23066-1 — Security update for the Linux Kernel</title>
    <updated>2026-10-03T06:50:35.110616+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Security update for the Linux Kernel</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/suse-su-2026:23066-1"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-53388</id>
    <title>UBUNTU-CVE-2026-53388</title>
    <updated>2026-10-03T06:50:35.111092+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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</p>
<p>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-&gt;folios[i]-&gt;mapping is never null since ap-&gt;folios[i] will always point to the newfolio after replace_page_cache_folio().</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-53388"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2403</id>
    <title>WID-SEC-W-2026-2403 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
    <updated>2026-10-03T06:50:35.111452+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2403"/>
  </entry>
</feed>
