<?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://vulnerability.circl.lu</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>Thu, 01 Oct 2026 06:13:46 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-64265</title>
      <link>https://vulnerability.circl.lu/vuln/bell-cve-2026-64265</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/bell-cve-2026-64265</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1031 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Certaines d'entre elles permettent à…</title>
      <link>https://vulnerability.circl.lu/vuln/certfr-2026-avi-1031</link>
      <description>certfr-2026-avi-1031</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/certfr-2026-avi-1031</guid>
    </item>
    <item>
      <title>fkie_cve-2026-64265</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-64265</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;fuse: clear intr_entry in fuse_resend and fuse_remove_pending_req&lt;/p&gt;
&lt;p&gt;When fuse_resend() moves a request from fpq-&amp;gt;processing back to
fiq-&amp;gt;pending, it sets FR_PENDING and clears FR_SENT but does not
remove the requests intr_entry from fiq-&amp;gt;interrupts.  If the
request had FR_INTERRUPTED set from a prior signal, intr_entry
remains dangling on fiq-&amp;gt;interrupts.  When the requesting task
then receives a fatal signal, fuse_remove_pending_req() sees
FR_PENDING=1, removes the request from fiq-&amp;gt;pending and frees it
via the refcount path, also without cleaning intr_entry.  The
stale intr_entry causes use-after-free when fuse_read_interrupt()
iterates fiq-&amp;gt;interrupts:
  - list_del_init(&amp;amp;req-&amp;gt;intr_entry) -&amp;gt; UAF write on freed slab
  - req-&amp;gt;in.h.unique -&amp;gt; UAF read, data leaked to userspace&lt;/p&gt;
&lt;p&gt;Remove intr_entry from fiq-&amp;gt;interrupts in fuse_resend() for
interrupted requests before they are placed back on fiq-&amp;gt;pending.&lt;/p&gt;
&lt;p&gt;Add a WARN_ON if the intr_entry is not empty on request destruction.&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: clear intr_entry in fuse_resend and fuse_remove_pending_req&lt;/p&gt;
&lt;p&gt;When fuse_resend() moves a request from fpq-&amp;gt;processing back to
fiq-&amp;gt;pending, it sets FR_PENDING and clears FR_SENT but does not
remove the requests intr_entry from fiq-&amp;gt;interrupts.  If the
request had FR_INTERRUPTED set from a prior signal, intr_entry
remains dangling on fiq-&amp;gt;interrupts.  When the requesting task
then receives a fatal signal, fuse_remove_pending_req() sees
FR_PENDING=1, removes the request from fiq-&amp;gt;pending and frees it
via the refcount path, also without cleaning intr_entry.  The
stale intr_entry causes use-after-free when fuse_read_interrupt()
iterates fiq-&amp;gt;interrupts:
  - list_del_init(&amp;amp;req-&amp;gt;intr_entry) -&amp;gt; UAF write on freed slab
  - req-&amp;gt;in.h.unique -&amp;gt; UAF read, data leaked to userspace&lt;/p&gt;
&lt;p&gt;Remove intr_entry from fiq-&amp;gt;interrupts in fuse_resend() for
interrupted requests before they are placed back on fiq-&amp;gt;pending.&lt;/p&gt;
&lt;p&gt;Add a WARN_ON if the intr_entry is not empty on request destruction.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-64265</guid>
    </item>
    <item>
      <title>GHSA-694x-mwh7-5pvf</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-694x-mwh7-5pvf</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;fuse: clear intr_entry in fuse_resend and fuse_remove_pending_req&lt;/p&gt;
&lt;p&gt;When fuse_resend() moves a request from fpq-&amp;gt;processing back to
fiq-&amp;gt;pending, it sets FR_PENDING and clears FR_SENT but does not
remove the requests intr_entry from fiq-&amp;gt;interrupts.  If the
request had FR_INTERRUPTED set from a prior signal, intr_entry
remains dangling on fiq-&amp;gt;interrupts.  When the requesting task
then receives a fatal signal, fuse_remove_pending_req() sees
FR_PENDING=1, removes the request from fiq-&amp;gt;pending and frees it
via the refcount path, also without cleaning intr_entry.  The
stale intr_entry causes use-after-free when fuse_read_interrupt()
iterates fiq-&amp;gt;interrupts:
  - list_del_init(&amp;amp;req-&amp;gt;intr_entry) -&amp;gt; UAF write on freed slab
  - req-&amp;gt;in.h.unique -&amp;gt; UAF read, data leaked to userspace&lt;/p&gt;
&lt;p&gt;Remove intr_entry from fiq-&amp;gt;interrupts in fuse_resend() for
interrupted requests before they are placed back on fiq-&amp;gt;pending.&lt;/p&gt;
&lt;p&gt;Add a WARN_ON if the intr_entry is not empty on request destruction.&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: clear intr_entry in fuse_resend and fuse_remove_pending_req&lt;/p&gt;
&lt;p&gt;When fuse_resend() moves a request from fpq-&amp;gt;processing back to
fiq-&amp;gt;pending, it sets FR_PENDING and clears FR_SENT but does not
remove the requests intr_entry from fiq-&amp;gt;interrupts.  If the
request had FR_INTERRUPTED set from a prior signal, intr_entry
remains dangling on fiq-&amp;gt;interrupts.  When the requesting task
then receives a fatal signal, fuse_remove_pending_req() sees
FR_PENDING=1, removes the request from fiq-&amp;gt;pending and frees it
via the refcount path, also without cleaning intr_entry.  The
stale intr_entry causes use-after-free when fuse_read_interrupt()
iterates fiq-&amp;gt;interrupts:
  - list_del_init(&amp;amp;req-&amp;gt;intr_entry) -&amp;gt; UAF write on freed slab
  - req-&amp;gt;in.h.unique -&amp;gt; UAF read, data leaked to userspace&lt;/p&gt;
&lt;p&gt;Remove intr_entry from fiq-&amp;gt;interrupts in fuse_resend() for
interrupted requests before they are placed back on fiq-&amp;gt;pending.&lt;/p&gt;
&lt;p&gt;Add a WARN_ON if the intr_entry is not empty on request destruction.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-694x-mwh7-5pvf</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:11476-1 — kernel-devel-7.1.7-1.1 on GA media</title>
      <link>https://vulnerability.circl.lu/vuln/opensuse-su-2026:11476-1</link>
      <description>&lt;p&gt;kernel-devel-7.1.7-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel-devel-7.1.7-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/opensuse-su-2026:11476-1</guid>
    </item>
    <item>
      <title>RLSA-2026:64775 — Important: kernel security, bug fix, and enhancement update</title>
      <link>https://vulnerability.circl.lu/vuln/rlsa-2026:64775</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Rocky Linux:10: kernel&lt;/p&gt;
&lt;p&gt;The kernel packages contain the Linux kernel, the core of any Linux operating system.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: can: bcm: add locking for bcm_op runtime updates (CVE-2025-38004)&lt;/p&gt;
&lt;p&gt;* kernel: ipv6: add NULL checks for idev in SRv6 paths (CVE-2026-23442)&lt;/p&gt;
&lt;p&gt;* kernel: udp: Fix wildcard bind conflict check when using hash2 (CVE-2026-31503)&lt;/p&gt;
&lt;p&gt;* kernel: ipv6: prevent possible UaF in addrconf_permanent_addr() (CVE-2026-43339)&lt;/p&gt;
&lt;p&gt;* kernel: tcp: call sk_data_ready() after listener migration (CVE-2026-46015)&lt;/p&gt;
&lt;p&gt;* kernel: inet: RAW sockets using IPPROTO_RAW MUST drop incoming ICMP (CVE-2026-46266)&lt;/p&gt;
&lt;p&gt;* kernel: flow_dissector: do not dissect PPPoE PFC frames (CVE-2026-46306)&lt;/p&gt;
&lt;p&gt;* kernel: io_uring/poll: fix signed comparison in io_poll_get_ownership() (CVE-2026-52933)&lt;/p&gt;
&lt;p&gt;* kernel: ppp: require CAP_NET_ADMIN in target netns for unattached ioctls (CVE-2026-53075)&lt;/p&gt;
&lt;p&gt;* kernel: KVM: arm64: Take the SRCU lock for page table walks in fault injection and AT emulation (CVE-2026-53277)&lt;/p&gt;
&lt;p&gt;* kernel: ipv6: sit: reload inner IPv6 header after GSO offloads (CVE-2026-53228)&lt;/p&gt;
&lt;p&gt;* kernel: net: add pskb_may_pull() to skb_gro_receive_list() (CVE-2026-53235)&lt;/p&gt;
&lt;p&gt;* kernel: net: guard timestamp cmsgs to real error queue skbs (CVE-2026-53223)&lt;/p&gt;
&lt;p&gt;* kernel: ipv6: mcast: Fix use-after-free when processing MLD queries (CVE-2026-53275)&lt;/p&gt;
&lt;p&gt;* kernel: ipv6: anycast: insert aca into global hash under idev-&amp;gt;lock (CVE-2026-53259)&lt;/p&gt;
&lt;p&gt;* kernel: ipv4: free net-&amp;gt;ipv4.sysctl_local_reserved_ports after unregister_net_sysctl_table() (CVE-2026-64002)&lt;/p&gt;
&lt;p&gt;*…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Rocky Linux:10: kernel&lt;/p&gt;
&lt;p&gt;The kernel packages contain the Linux kernel, the core of any Linux operating system.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: can: bcm: add locking for bcm_op runtime updates (CVE-2025-38004)&lt;/p&gt;
&lt;p&gt;* kernel: ipv6: add NULL checks for idev in SRv6 paths (CVE-2026-23442)&lt;/p&gt;
&lt;p&gt;* kernel: udp: Fix wildcard bind conflict check when using hash2 (CVE-2026-31503)&lt;/p&gt;
&lt;p&gt;* kernel: ipv6: prevent possible UaF in addrconf_permanent_addr() (CVE-2026-43339)&lt;/p&gt;
&lt;p&gt;* kernel: tcp: call sk_data_ready() after listener migration (CVE-2026-46015)&lt;/p&gt;
&lt;p&gt;* kernel: inet: RAW sockets using IPPROTO_RAW MUST drop incoming ICMP (CVE-2026-46266)&lt;/p&gt;
&lt;p&gt;* kernel: flow_dissector: do not dissect PPPoE PFC frames (CVE-2026-46306)&lt;/p&gt;
&lt;p&gt;* kernel: io_uring/poll: fix signed comparison in io_poll_get_ownership() (CVE-2026-52933)&lt;/p&gt;
&lt;p&gt;* kernel: ppp: require CAP_NET_ADMIN in target netns for unattached ioctls (CVE-2026-53075)&lt;/p&gt;
&lt;p&gt;* kernel: KVM: arm64: Take the SRCU lock for page table walks in fault injection and AT emulation (CVE-2026-53277)&lt;/p&gt;
&lt;p&gt;* kernel: ipv6: sit: reload inner IPv6 header after GSO offloads (CVE-2026-53228)&lt;/p&gt;
&lt;p&gt;* kernel: net: add pskb_may_pull() to skb_gro_receive_list() (CVE-2026-53235)&lt;/p&gt;
&lt;p&gt;* kernel: net: guard timestamp cmsgs to real error queue skbs (CVE-2026-53223)&lt;/p&gt;
&lt;p&gt;* kernel: ipv6: mcast: Fix use-after-free when processing MLD queries (CVE-2026-53275)&lt;/p&gt;
&lt;p&gt;* kernel: ipv6: anycast: insert aca into global hash under idev-&amp;gt;lock (CVE-2026-53259)&lt;/p&gt;
&lt;p&gt;* kernel: ipv4: free net-&amp;gt;ipv4.sysctl_local_reserved_ports after unregister_net_sysctl_table() (CVE-2026-64002)&lt;/p&gt;
&lt;p&gt;*…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/rlsa-2026:64775</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:23881-1 — Security update for the Linux Kernel</title>
      <link>https://vulnerability.circl.lu/vuln/suse-su-2026:23881-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://vulnerability.circl.lu/vuln/suse-su-2026:23881-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-64265</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-64265</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.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 119 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: fuse: clear intr_entry in fuse_resend and fuse_remove_pending_req When fuse_resend() moves a request from fpq-&amp;gt;processing back to fiq-&amp;gt;pending, it sets FR_PENDING and clears FR_SENT but does not remove the requests intr_entry from fiq-&amp;gt;interrupts.  If the request had FR_INTERRUPTED set from a prior signal, intr_entry remains dangling on fiq-&amp;gt;interrupts.  When the requesting task then receives a fatal signal, fuse_remove_pending_req() sees FR_PENDING=1, removes the request from fiq-&amp;gt;pending and frees it via the refcount path, also without cleaning intr_entry.  The stale intr_entry causes use-after-free when fuse_read_interrupt() iterates fiq-&amp;gt;interrupts:   - list_del_init(&amp;amp;req-&amp;gt;intr_entry) -&amp;gt; UAF write on freed slab   - req-&amp;gt;in.h.unique -&amp;gt; UAF read, data leaked to userspace Remove intr_entry from fiq-&amp;gt;interrupts in fuse_resend() for interrupted requests before they are placed back on fiq-&amp;gt;pending. Add a WARN_ON if the intr_entry is not empty on request destruction.&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.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 119 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: fuse: clear intr_entry in fuse_resend and fuse_remove_pending_req When fuse_resend() moves a request from fpq-&amp;gt;processing back to fiq-&amp;gt;pending, it sets FR_PENDING and clears FR_SENT but does not remove the requests intr_entry from fiq-&amp;gt;interrupts.  If the request had FR_INTERRUPTED set from a prior signal, intr_entry remains dangling on fiq-&amp;gt;interrupts.  When the requesting task then receives a fatal signal, fuse_remove_pending_req() sees FR_PENDING=1, removes the request from fiq-&amp;gt;pending and frees it via the refcount path, also without cleaning intr_entry.  The stale intr_entry causes use-after-free when fuse_read_interrupt() iterates fiq-&amp;gt;interrupts:   - list_del_init(&amp;amp;req-&amp;gt;intr_entry) -&amp;gt; UAF write on freed slab   - req-&amp;gt;in.h.unique -&amp;gt; UAF read, data leaked to userspace Remove intr_entry from fiq-&amp;gt;interrupts in fuse_resend() for interrupted requests before they are placed back on fiq-&amp;gt;pending. Add a WARN_ON if the intr_entry is not empty on request destruction.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-64265</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2527 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://vulnerability.circl.lu/vuln/wid-sec-w-2026-2527</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, dazu können DoS-Angriffe, die Offenlegung von Informationen, die Beschädigung des Speichers oder die Umgehung von Sicherheitsmaßnahmen gehören.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, dazu können DoS-Angriffe, die Offenlegung von Informationen, die Beschädigung des Speichers oder die Umgehung von Sicherheitsmaßnahmen gehören.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/wid-sec-w-2026-2527</guid>
    </item>
  </channel>
</rss>
