<?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>Sat, 21 Nov 2026 09:30:53 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-53043</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-53043</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-53043</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0862 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Certaines d'entre elles permettent à…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-0862</link>
      <description>certfr-2026-avi-0862</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-0862</guid>
    </item>
    <item>
      <title>OESA-2026-3532 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2026-3532</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.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;uaccess: fix integer overflow on access_ok()&lt;/p&gt;
&lt;p&gt;Three architectures check the end of a user access against the
address limit without taking a possible overflow into account.
Passing a negative length or another overflow in here returns
success when it should not.&lt;/p&gt;
&lt;p&gt;Use the most common correct implementation here, which optimizes
for a constant &amp;amp;apos;size&amp;amp;apos; argument, and turns the common case into a
single comparison.(CVE-2022-49289)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;parisc: Fix double SIGFPE crash&lt;/p&gt;
&lt;p&gt;Camm noticed that on parisc a SIGFPE exception will crash an application with
a second SIGFPE in the signal handler.  Dave analyzed it, and it happens
because glibc uses a double-word floating-point store to atomically update
function descriptors. As a result of lazy binding, we hit a floating-point
store in fpe_func almost immediately.&lt;/p&gt;
&lt;p&gt;When the T bit is set, an assist exception trap occurs when when the
co-processor encounters *any* floating-point instruction except for a double
store of register %fr0.  The latter cancels all pending traps.  Let&amp;amp;apos;s fix this
by clearing the Trap (T) bit in the FP status register before returning to the
signal handler in userspace.&lt;/p&gt;
&lt;p&gt;The issue can be reproduced with this test program:&lt;/p&gt;
&lt;p&gt;root@parisc:~# cat fpe.c&lt;/p&gt;
&lt;p&gt;static void fpe_func(int sig, siginfo_t *i, void *v) {…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.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;uaccess: fix integer overflow on access_ok()&lt;/p&gt;
&lt;p&gt;Three architectures check the end of a user access against the
address limit without taking a possible overflow into account.
Passing a negative length or another overflow in here returns
success when it should not.&lt;/p&gt;
&lt;p&gt;Use the most common correct implementation here, which optimizes
for a constant &amp;amp;apos;size&amp;amp;apos; argument, and turns the common case into a
single comparison.(CVE-2022-49289)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;parisc: Fix double SIGFPE crash&lt;/p&gt;
&lt;p&gt;Camm noticed that on parisc a SIGFPE exception will crash an application with
a second SIGFPE in the signal handler.  Dave analyzed it, and it happens
because glibc uses a double-word floating-point store to atomically update
function descriptors. As a result of lazy binding, we hit a floating-point
store in fpe_func almost immediately.&lt;/p&gt;
&lt;p&gt;When the T bit is set, an assist exception trap occurs when when the
co-processor encounters *any* floating-point instruction except for a double
store of register %fr0.  The latter cancels all pending traps.  Let&amp;amp;apos;s fix this
by clearing the Trap (T) bit in the FP status register before returning to the
signal handler in userspace.&lt;/p&gt;
&lt;p&gt;The issue can be reproduced with this test program:&lt;/p&gt;
&lt;p&gt;root@parisc:~# cat fpe.c&lt;/p&gt;
&lt;p&gt;static void fpe_func(int sig, siginfo_t *i, void *v) {…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2026-3532</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-53043</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-53043</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 255 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ocfs2/dlm: validate qr_numregions in dlm_match_regions() Patch series &amp;#34;ocfs2/dlm: fix two bugs in dlm_match_regions()&amp;#34;. In dlm_match_regions(), the qr_numregions field from a DLM_QUERY_REGION network message is used to drive loops over the qr_regions buffer without sufficient validation.  This series fixes two issues: - Patch 1 adds a bounds check to reject messages where qr_numregions   exceeds O2NM_MAX_REGIONS. The o2net layer only validates message   byte length; it does not constrain field values, so a crafted message   can set qr_numregions up to 255 and trigger out-of-bounds reads past   the 1024-byte qr_regions buffer. - Patch 2 fixes an off-by-one in the local-vs-remote comparison loop,   which uses &amp;#39;&amp;lt;=&amp;#39; instead of &amp;#39;&amp;lt;&amp;#39;, reading one entry past the valid range   even when qr_numregions is within bounds. This patch (of 2): The qr_numregions field from a DLM_QUERY_REGION network message is used directly as loop bounds in dlm_match_regions() without checking against O2NM_MAX_REGIONS.  Since qr_regions is sized for at most O2NM_MAX_REGIONS (32) entries, a crafted message with qr_numregions &amp;gt; 32 causes out-of-bounds reads past the qr_regions buffer. Add a bounds check for qr_numregions before entering the loops.&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 255 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ocfs2/dlm: validate qr_numregions in dlm_match_regions() Patch series &amp;#34;ocfs2/dlm: fix two bugs in dlm_match_regions()&amp;#34;. In dlm_match_regions(), the qr_numregions field from a DLM_QUERY_REGION network message is used to drive loops over the qr_regions buffer without sufficient validation.  This series fixes two issues: - Patch 1 adds a bounds check to reject messages where qr_numregions   exceeds O2NM_MAX_REGIONS. The o2net layer only validates message   byte length; it does not constrain field values, so a crafted message   can set qr_numregions up to 255 and trigger out-of-bounds reads past   the 1024-byte qr_regions buffer. - Patch 2 fixes an off-by-one in the local-vs-remote comparison loop,   which uses &amp;#39;&amp;lt;=&amp;#39; instead of &amp;#39;&amp;lt;&amp;#39;, reading one entry past the valid range   even when qr_numregions is within bounds. This patch (of 2): The qr_numregions field from a DLM_QUERY_REGION network message is used directly as loop bounds in dlm_match_regions() without checking against O2NM_MAX_REGIONS.  Since qr_regions is sized for at most O2NM_MAX_REGIONS (32) entries, a crafted message with qr_numregions &amp;gt; 32 causes out-of-bounds reads past the qr_regions buffer. Add a bounds check for qr_numregions before entering the loops.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-53043</guid>
    </item>
  </channel>
</rss>
