<?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://127.0.0.1:10001</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, 19 Nov 2026 17:44:22 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-68082</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-68082</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://127.0.0.1:10001/vuln/bell-cve-2026-68082</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1090 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-1090</link>
      <description>certfr-2026-avi-1090</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-1090</guid>
    </item>
    <item>
      <title>OESA-2026-3705 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2026-3705</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;ocfs2/dlm: fix off-by-one in dlm_match_regions() region comparison&lt;/p&gt;
&lt;p&gt;The local-vs-remote region comparison loop uses &amp;amp;apos;&amp;amp;lt;=&amp;amp;apos; instead of &amp;amp;apos;&amp;amp;lt;&amp;amp;apos;,
causing it to read one entry past the valid range of qr_regions.  The
other loops in the same function correctly use &amp;amp;apos;&amp;amp;lt;&amp;amp;apos;.&lt;/p&gt;
&lt;p&gt;Fix the loop condition to use &amp;amp;apos;&amp;amp;lt;&amp;amp;apos; for consistency and correctness.(CVE-2026-53309)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ixgbevf: fix use-after-free in VEPA multicast source pruning&lt;/p&gt;
&lt;p&gt;ixgbevf_clean_rx_irq() prunes frames whose source MAC matches the VF&amp;amp;apos;s
own address (VEPA multicast workaround) by freeing the skb and
continuing to the next descriptor:&lt;/p&gt;
&lt;p&gt;dev_kfree_skb_irq(skb);
    continue;&lt;/p&gt;
&lt;p&gt;The skb pointer is declared outside the while loop and persists across
iterations.  Because the continue skips the &amp;amp;quot;skb = NULL&amp;amp;quot; reset at the
bottom of the loop, the next iteration enters the &amp;amp;quot;else if (skb)&amp;amp;quot; path
and calls ixgbevf_add_rx_frag() on the freed skb, dereferencing
skb_shinfo(skb)-&amp;amp;gt;nr_frags - a use-after-free in NAPI softirq context.&lt;/p&gt;
&lt;p&gt;The sibling driver iavf already handles this correctly by nulling the
pointer before continuing.  Apply the same pattern here.&lt;/p&gt;
&lt;p&gt;I do not have ixgbevf hardware; the bug was found by static analysis
(scan_drop_continue_loops.py + semgrep drop_…&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;ocfs2/dlm: fix off-by-one in dlm_match_regions() region comparison&lt;/p&gt;
&lt;p&gt;The local-vs-remote region comparison loop uses &amp;amp;apos;&amp;amp;lt;=&amp;amp;apos; instead of &amp;amp;apos;&amp;amp;lt;&amp;amp;apos;,
causing it to read one entry past the valid range of qr_regions.  The
other loops in the same function correctly use &amp;amp;apos;&amp;amp;lt;&amp;amp;apos;.&lt;/p&gt;
&lt;p&gt;Fix the loop condition to use &amp;amp;apos;&amp;amp;lt;&amp;amp;apos; for consistency and correctness.(CVE-2026-53309)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ixgbevf: fix use-after-free in VEPA multicast source pruning&lt;/p&gt;
&lt;p&gt;ixgbevf_clean_rx_irq() prunes frames whose source MAC matches the VF&amp;amp;apos;s
own address (VEPA multicast workaround) by freeing the skb and
continuing to the next descriptor:&lt;/p&gt;
&lt;p&gt;dev_kfree_skb_irq(skb);
    continue;&lt;/p&gt;
&lt;p&gt;The skb pointer is declared outside the while loop and persists across
iterations.  Because the continue skips the &amp;amp;quot;skb = NULL&amp;amp;quot; reset at the
bottom of the loop, the next iteration enters the &amp;amp;quot;else if (skb)&amp;amp;quot; path
and calls ixgbevf_add_rx_frag() on the freed skb, dereferencing
skb_shinfo(skb)-&amp;amp;gt;nr_frags - a use-after-free in NAPI softirq context.&lt;/p&gt;
&lt;p&gt;The sibling driver iavf already handles this correctly by nulling the
pointer before continuing.  Apply the same pattern here.&lt;/p&gt;
&lt;p&gt;I do not have ixgbevf hardware; the bug was found by static analysis
(scan_drop_continue_loops.py + semgrep drop_…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2026-3705</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-68082</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-68082</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, 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, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 240 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: libceph: fix two unsafe bare decodes in decode_lockers() decode_lockers() in cls_lock_client.c contains two bare decode operations that allow a malicious or compromised OSD to trigger slab-out-of-bounds reads: 1. ceph_decode_32(p) at the num_lockers field has no preceding bounds    check. ceph_start_decoding() accepts struct_len=0 as valid -- the    internal ceph_decode_need(p, end, 0, bad) always passes -- so when an    OSD sends struct_len=0, ceph_start_decoding() returns success with    p == end. The immediately following bare ceph_decode_32(p) then reads    4 bytes past the validated buffer boundary. The garbage value is    passed directly to kzalloc_objs() as the locker count.    The sibling function decode_watchers() in osd_client.c already uses    ceph_decode_32_safe() after its own ceph_start_decoding() call.    decode_lockers() was the only site using the bare variant. 2. ceph_decode_8(p) after the decode_locker() loop has no preceding    bounds check. If an OSD crafts num_lockers such that the loop    advances p exactly to end, the subsequent bare ceph_decode_8(p) reads    one byte past the validated buffer boundary. The result is passed    directly into *type, which is used as a lock type discriminator by    callers, giving an OSD-controlled one-byte OOB read with direct    influence over the lock type field. Fix both by replacing bare operations with their safe variants:   ceph_decode_32(p) -&amp;gt; ce…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, 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, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 240 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: libceph: fix two unsafe bare decodes in decode_lockers() decode_lockers() in cls_lock_client.c contains two bare decode operations that allow a malicious or compromised OSD to trigger slab-out-of-bounds reads: 1. ceph_decode_32(p) at the num_lockers field has no preceding bounds    check. ceph_start_decoding() accepts struct_len=0 as valid -- the    internal ceph_decode_need(p, end, 0, bad) always passes -- so when an    OSD sends struct_len=0, ceph_start_decoding() returns success with    p == end. The immediately following bare ceph_decode_32(p) then reads    4 bytes past the validated buffer boundary. The garbage value is    passed directly to kzalloc_objs() as the locker count.    The sibling function decode_watchers() in osd_client.c already uses    ceph_decode_32_safe() after its own ceph_start_decoding() call.    decode_lockers() was the only site using the bare variant. 2. ceph_decode_8(p) after the decode_locker() loop has no preceding    bounds check. If an OSD crafts num_lockers such that the loop    advances p exactly to end, the subsequent bare ceph_decode_8(p) reads    one byte past the validated buffer boundary. The result is passed    directly into *type, which is used as a lock type discriminator by    callers, giving an OSD-controlled one-byte OOB read with direct    influence over the lock type field. Fix both by replacing bare operations with their safe variants:   ceph_decode_32(p) -&amp;gt; ce…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-68082</guid>
    </item>
  </channel>
</rss>
