<?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 10:44:50 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2024-56647</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-56647</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-56647</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0183 — De multiples vulnérabilités ont été découvertes dans les produits SUSE. Certaines d'entre elles permettent à un attaqua…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2025-avi-0183</link>
      <description>certfr-2025-avi-0183</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0183</guid>
    </item>
    <item>
      <title>OESA-2025-1094 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2025-1094</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;ASoC: ops: Shift tested values in snd_soc_put_volsw() by +min&lt;/p&gt;
&lt;p&gt;While the $val/$val2 values passed in from userspace are always &amp;amp;gt;= 0
integers, the limits of the control can be signed integers and the $min
can be non-zero and less than zero. To correctly validate $val/$val2
against platform_max, add the $min offset to val first.(CVE-2022-48917)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;tcp: do not accept ACK of bytes we never sent&lt;/p&gt;
&lt;p&gt;This patch is based on a detailed report and ideas from Yepeng Pan
and Christian Rossow.&lt;/p&gt;
&lt;p&gt;ACK seq validation is currently following RFC 5961 5.2 guidelines:&lt;/p&gt;
&lt;p&gt;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 mo…&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;ASoC: ops: Shift tested values in snd_soc_put_volsw() by +min&lt;/p&gt;
&lt;p&gt;While the $val/$val2 values passed in from userspace are always &amp;amp;gt;= 0
integers, the limits of the control can be signed integers and the $min
can be non-zero and less than zero. To correctly validate $val/$val2
against platform_max, add the $min offset to val first.(CVE-2022-48917)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;tcp: do not accept ACK of bytes we never sent&lt;/p&gt;
&lt;p&gt;This patch is based on a detailed report and ideas from Yepeng Pan
and Christian Rossow.&lt;/p&gt;
&lt;p&gt;ACK seq validation is currently following RFC 5961 5.2 guidelines:&lt;/p&gt;
&lt;p&gt;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 mo…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2025-1094</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-56647</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-56647</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 198 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: Fix icmp host relookup triggering ip_rt_bug arp link failure may trigger ip_rt_bug while xfrm enabled, call trace is: WARNING: CPU: 0 PID: 0 at net/ipv4/route.c:1241 ip_rt_bug+0x14/0x20 Modules linked in: CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Not tainted 6.12.0-rc6-00077-g2e1b3cc9d7f7 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 RIP: 0010:ip_rt_bug+0x14/0x20 Call Trace:  &amp;lt;IRQ&amp;gt;  ip_send_skb+0x14/0x40  __icmp_send+0x42d/0x6a0  ipv4_link_failure+0xe2/0x1d0  arp_error_report+0x3c/0x50  neigh_invalidate+0x8d/0x100  neigh_timer_handler+0x2e1/0x330  call_timer_fn+0x21/0x120  __run_timer_base.part.0+0x1c9/0x270  run_timer_softirq+0x4c/0x80  handle_softirqs+0xac/0x280  irq_exit_rcu+0x62/0x80  sysvec_apic_timer_interrupt+0x77/0x90 The script below reproduces this scenario: ip xfrm policy add src 0.0.0.0/0 dst 0.0.0.0/0 \ 	dir out priority 0 ptype main flag localok icmp ip l a veth1 type veth ip a a 192.168.141.111/24 dev veth0 ip l s veth0 up ping 192.168.141.155 -c 1 icmp_route_lookup() create input routes for locally generated packets while xfrm relookup ICMP traffic.Then it will set input route (dst-&amp;gt;out = ip_rt_bug) to skb for DESTUNREACH. For ICMP err triggered by locally generated packets, dst-&amp;gt;dev of output route is loopback. Generally, xfrm relookup verification is not required on loopback interfaces (net.ipv4.conf.lo.disable_xfrm = 1).…&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 198 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: Fix icmp host relookup triggering ip_rt_bug arp link failure may trigger ip_rt_bug while xfrm enabled, call trace is: WARNING: CPU: 0 PID: 0 at net/ipv4/route.c:1241 ip_rt_bug+0x14/0x20 Modules linked in: CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Not tainted 6.12.0-rc6-00077-g2e1b3cc9d7f7 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 RIP: 0010:ip_rt_bug+0x14/0x20 Call Trace:  &amp;lt;IRQ&amp;gt;  ip_send_skb+0x14/0x40  __icmp_send+0x42d/0x6a0  ipv4_link_failure+0xe2/0x1d0  arp_error_report+0x3c/0x50  neigh_invalidate+0x8d/0x100  neigh_timer_handler+0x2e1/0x330  call_timer_fn+0x21/0x120  __run_timer_base.part.0+0x1c9/0x270  run_timer_softirq+0x4c/0x80  handle_softirqs+0xac/0x280  irq_exit_rcu+0x62/0x80  sysvec_apic_timer_interrupt+0x77/0x90 The script below reproduces this scenario: ip xfrm policy add src 0.0.0.0/0 dst 0.0.0.0/0 \ 	dir out priority 0 ptype main flag localok icmp ip l a veth1 type veth ip a a 192.168.141.111/24 dev veth0 ip l s veth0 up ping 192.168.141.155 -c 1 icmp_route_lookup() create input routes for locally generated packets while xfrm relookup ICMP traffic.Then it will set input route (dst-&amp;gt;out = ip_rt_bug) to skb for DESTUNREACH. For ICMP err triggered by locally generated packets, dst-&amp;gt;dev of output route is loopback. Generally, xfrm relookup verification is not required on loopback interfaces (net.ipv4.conf.lo.disable_xfrm = 1).…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-56647</guid>
    </item>
  </channel>
</rss>
