<?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 05:49:17 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2025-37885</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-37885</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-2025-37885</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0463 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Elles permettent à un attaquant de p…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2025-avi-0463</link>
      <description>certfr-2025-avi-0463</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0463</guid>
    </item>
    <item>
      <title>OESA-2025-2118 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2025-2118</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP3: 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;netfilter: nf_tables: avoid skb access on nf_stolen&lt;/p&gt;
&lt;p&gt;When verdict is NF_STOLEN, the skb might have been freed.&lt;/p&gt;
&lt;p&gt;When tracing is enabled, this can result in a use-after-free:
1. access to skb-&amp;amp;gt;nf_trace
2. access to skb-&amp;amp;gt;mark
3. computation of trace id
4. dump of packet payload&lt;/p&gt;
&lt;p&gt;To avoid 1, keep a cached copy of skb-&amp;amp;gt;nf_trace in the
trace state struct.
Refresh this copy whenever verdict is != STOLEN.&lt;/p&gt;
&lt;p&gt;Avoid 2 by skipping skb-&amp;amp;gt;mark access if verdict is STOLEN.&lt;/p&gt;
&lt;p&gt;3 is avoided by precomputing the trace id.&lt;/p&gt;
&lt;p&gt;Only dump the packet when verdict is not &amp;amp;quot;STOLEN&amp;amp;quot;.(CVE-2022-49622)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;nfsd: release svc_expkey/svc_export with rcu_work&lt;/p&gt;
&lt;p&gt;The last reference for `cache_head` can be reduced to zero in `c_show`
and `e_show`(using `rcu_read_lock` and `rcu_read_unlock`). Consequently,
`svc_export_put` and `expkey_put` will be invoked, leading to two
issues:&lt;/p&gt;
&lt;p&gt;1. The `svc_export_put` will directly free ex_uuid. However,
   `e_show`/`c_show` will access `ex_uuid` after `cache_put`, which can
   trigger a use-after-free issue, shown below.&lt;/p&gt;
&lt;p&gt;==================================================================
   BUG: KASAN: slab-use-after-free in svc_export_show+0x362/0x430 [nfsd]
   Read of size 1 at addr ff11000010fdc120 by task cat/870&lt;/p&gt;
&lt;p&gt;CPU: 1 UID: 0 PID: 870 Comm: cat…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP3: 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;netfilter: nf_tables: avoid skb access on nf_stolen&lt;/p&gt;
&lt;p&gt;When verdict is NF_STOLEN, the skb might have been freed.&lt;/p&gt;
&lt;p&gt;When tracing is enabled, this can result in a use-after-free:
1. access to skb-&amp;amp;gt;nf_trace
2. access to skb-&amp;amp;gt;mark
3. computation of trace id
4. dump of packet payload&lt;/p&gt;
&lt;p&gt;To avoid 1, keep a cached copy of skb-&amp;amp;gt;nf_trace in the
trace state struct.
Refresh this copy whenever verdict is != STOLEN.&lt;/p&gt;
&lt;p&gt;Avoid 2 by skipping skb-&amp;amp;gt;mark access if verdict is STOLEN.&lt;/p&gt;
&lt;p&gt;3 is avoided by precomputing the trace id.&lt;/p&gt;
&lt;p&gt;Only dump the packet when verdict is not &amp;amp;quot;STOLEN&amp;amp;quot;.(CVE-2022-49622)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;nfsd: release svc_expkey/svc_export with rcu_work&lt;/p&gt;
&lt;p&gt;The last reference for `cache_head` can be reduced to zero in `c_show`
and `e_show`(using `rcu_read_lock` and `rcu_read_unlock`). Consequently,
`svc_export_put` and `expkey_put` will be invoked, leading to two
issues:&lt;/p&gt;
&lt;p&gt;1. The `svc_export_put` will directly free ex_uuid. However,
   `e_show`/`c_show` will access `ex_uuid` after `cache_put`, which can
   trigger a use-after-free issue, shown below.&lt;/p&gt;
&lt;p&gt;==================================================================
   BUG: KASAN: slab-use-after-free in svc_export_show+0x362/0x430 [nfsd]
   Read of size 1 at addr ff11000010fdc120 by task cat/870&lt;/p&gt;
&lt;p&gt;CPU: 1 UID: 0 PID: 870 Comm: cat…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2025-2118</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-37885</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-37885</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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, Ubuntu:16.04:LTS: linux-hwe-edge and 207 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Reset IRTE to host control if *new* route isn&amp;#39;t postable Restore an IRTE back to host control (remapped or posted MSI mode) if the *new* GSI route prevents posting the IRQ directly to a vCPU, regardless of the GSI routing type.  Updating the IRTE if and only if the new GSI is an MSI results in KVM leaving an IRTE posting to a vCPU. The dangling IRTE can result in interrupts being incorrectly delivered to the guest, and in the worst case scenario can result in use-after-free, e.g. if the VM is torn down, but the underlying host IRQ isn&amp;#39;t freed.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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, Ubuntu:16.04:LTS: linux-hwe-edge and 207 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Reset IRTE to host control if *new* route isn&amp;#39;t postable Restore an IRTE back to host control (remapped or posted MSI mode) if the *new* GSI route prevents posting the IRQ directly to a vCPU, regardless of the GSI routing type.  Updating the IRTE if and only if the new GSI is an MSI results in KVM leaving an IRTE posting to a vCPU. The dangling IRTE can result in interrupts being incorrectly delivered to the guest, and in the worst case scenario can result in use-after-free, e.g. if the VM is torn down, but the underlying host IRQ isn&amp;#39;t freed.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-37885</guid>
    </item>
  </channel>
</rss>
