<?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 08:46:25 +0000</lastBuildDate>
    <item>
      <title>ALSA-2024:10939 — Moderate: kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/alsa-2024:10939</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:9: bpftool, AlmaLinux:9: kernel, AlmaLinux:9: kernel-64k, AlmaLinux:9: kernel-64k-core, AlmaLinux:9: kernel-64k-debug, AlmaLinux:9: kernel-64k-debug-core, AlmaLinux:9: kernel-64k-debug-devel, AlmaLinux:9: kernel-64k-debug-devel-matched, AlmaLinux:9: kernel-64k-debug-modules, AlmaLinux:9: kernel-64k-debug-modules-core and 53 more&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: net/smc: fix illegal rmb_desc access in SMC-D connection dump (CVE-2024-26615)
  * kernel: block: initialize integrity buffer to zero before writing it to media (CVE-2024-43854)
  * kernel: iommu: Restore lost return in iommu_report_device_fault() (CVE-2024-44994)
  * kernel: netfilter: flowtable: initialise extack before use (CVE-2024-45018)
  * kernel: selinux,smack: don&amp;#39;t bypass permissions check in inode_setsecctx hook (CVE-2024-46695)
  * kernel: net: avoid potential underflow in qdisc_pkt_len_init() with UFO (CVE-2024-49949)
  * kernel: netfilter: nft_payload: sanitize offset and length before calling skb_checksum() (CVE-2024-50251)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:9: bpftool, AlmaLinux:9: kernel, AlmaLinux:9: kernel-64k, AlmaLinux:9: kernel-64k-core, AlmaLinux:9: kernel-64k-debug, AlmaLinux:9: kernel-64k-debug-core, AlmaLinux:9: kernel-64k-debug-devel, AlmaLinux:9: kernel-64k-debug-devel-matched, AlmaLinux:9: kernel-64k-debug-modules, AlmaLinux:9: kernel-64k-debug-modules-core and 53 more&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: net/smc: fix illegal rmb_desc access in SMC-D connection dump (CVE-2024-26615)
  * kernel: block: initialize integrity buffer to zero before writing it to media (CVE-2024-43854)
  * kernel: iommu: Restore lost return in iommu_report_device_fault() (CVE-2024-44994)
  * kernel: netfilter: flowtable: initialise extack before use (CVE-2024-45018)
  * kernel: selinux,smack: don&amp;#39;t bypass permissions check in inode_setsecctx hook (CVE-2024-46695)
  * kernel: net: avoid potential underflow in qdisc_pkt_len_init() with UFO (CVE-2024-49949)
  * kernel: netfilter: nft_payload: sanitize offset and length before calling skb_checksum() (CVE-2024-50251)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/alsa-2024:10939</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-45018</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-45018</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-2024-45018</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0837 — 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-2024-avi-0837</link>
      <description>certfr-2024-avi-0837</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2024-avi-0837</guid>
    </item>
    <item>
      <title>OESA-2024-2295 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2024-2295</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP1: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
octeontx2-af: Fix possible null pointer dereference.&#13;
&#13;
This patch fixes possible null pointer dereference in files
&amp;amp;quot;rvu_debugfs.c&amp;amp;quot; and &amp;amp;quot;rvu_nix.c&amp;amp;quot;(CVE-2021-47484)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
tcp: do not accept ACK of bytes we never sent&#13;
&#13;
This patch is based on a detailed report and ideas from Yepeng Pan
and Christian Rossow.&#13;
&#13;
ACK seq validation is currently following RFC 5961 5.2 guidelines:&#13;
&#13;
   The ACK value is considered acceptable only if
   it is in the range of ((SND.UNA - MAX.SND.WND) &amp;amp;lt;= SEG.ACK &amp;amp;lt;=
   SND.NXT).  All incoming segments whose ACK value doesn&amp;amp;apos;t satisfy the
   above condition MUST be discarded and an ACK sent back.  It needs to
   be noted that RFC 793 on page 72 (fifth check) says: &amp;amp;quot;If the ACK is a
   duplicate (SEG.ACK &amp;amp;lt; SND.UNA), it can be ignored.  If the ACK
   acknowledges something not yet sent (SEG.ACK &amp;amp;gt; SND.NXT) then send an
   ACK, drop the segment, and return&amp;amp;quot;.  The &amp;amp;quot;ignored&amp;amp;quot; above implies that
   the processing of the incoming data segment continues, which means
   the ACK value is treated as acceptable.  This mitigation makes the
   ACK check more stringent since any ACK &amp;amp;lt; SND.UNA wouldn&amp;amp;apos;t be
   accepted, instead only ACKs that are in the range ((SND.UNA -
   MAX.SND.WND) &amp;amp;lt;= SEG.AC…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP1: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
octeontx2-af: Fix possible null pointer dereference.&#13;
&#13;
This patch fixes possible null pointer dereference in files
&amp;amp;quot;rvu_debugfs.c&amp;amp;quot; and &amp;amp;quot;rvu_nix.c&amp;amp;quot;(CVE-2021-47484)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
tcp: do not accept ACK of bytes we never sent&#13;
&#13;
This patch is based on a detailed report and ideas from Yepeng Pan
and Christian Rossow.&#13;
&#13;
ACK seq validation is currently following RFC 5961 5.2 guidelines:&#13;
&#13;
   The ACK value is considered acceptable only if
   it is in the range of ((SND.UNA - MAX.SND.WND) &amp;amp;lt;= SEG.ACK &amp;amp;lt;=
   SND.NXT).  All incoming segments whose ACK value doesn&amp;amp;apos;t satisfy the
   above condition MUST be discarded and an ACK sent back.  It needs to
   be noted that RFC 793 on page 72 (fifth check) says: &amp;amp;quot;If the ACK is a
   duplicate (SEG.ACK &amp;amp;lt; SND.UNA), it can be ignored.  If the ACK
   acknowledges something not yet sent (SEG.ACK &amp;amp;gt; SND.NXT) then send an
   ACK, drop the segment, and return&amp;amp;quot;.  The &amp;amp;quot;ignored&amp;amp;quot; above implies that
   the processing of the incoming data segment continues, which means
   the ACK value is treated as acceptable.  This mitigation makes the
   ACK check more stringent since any ACK &amp;amp;lt; SND.UNA wouldn&amp;amp;apos;t be
   accepted, instead only ACKs that are in the range ((SND.UNA -
   MAX.SND.WND) &amp;amp;lt;= SEG.AC…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2024-2295</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-45018</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-45018</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 132 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: netfilter: flowtable: initialise extack before use Fix missing initialisation of extack in flow offload.&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 132 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: netfilter: flowtable: initialise extack before use Fix missing initialisation of extack in flow offload.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-45018</guid>
    </item>
  </channel>
</rss>
