<?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:46:33 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2025-38615</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-38615</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-38615</guid>
    </item>
    <item>
      <title>certfr-2025-avi-1050 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2025-avi-1050</link>
      <description>certfr-2025-avi-1050</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-1050</guid>
    </item>
    <item>
      <title>OESA-2025-2407 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2025-2407</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;net: dsa: Avoid cross-chip syncing of VLAN filtering&lt;/p&gt;
&lt;p&gt;Changes to VLAN filtering are not applicable to cross-chip
notifications.&lt;/p&gt;
&lt;p&gt;On a system like this:&lt;/p&gt;
&lt;p&gt;.-----.   .-----.   .-----.
| sw1 +---+ sw2 +---+ sw3 |
&amp;amp;apos;-1-2-&amp;amp;apos;   &amp;amp;apos;-1-2-&amp;amp;apos;   &amp;amp;apos;-1-2-&amp;amp;apos;&lt;/p&gt;
&lt;p&gt;Before this change, upon sw1p1 leaving a bridge, a call to
dsa_port_vlan_filtering would also be made to sw2p1 and sw3p1.&lt;/p&gt;
&lt;p&gt;In this scenario:&lt;/p&gt;
&lt;p&gt;.---------.   .-----.   .-----.
|   sw1   +---+ sw2 +---+ sw3 |
&amp;amp;apos;-1-2-3-4-&amp;amp;apos;   &amp;amp;apos;-1-2-&amp;amp;apos;   &amp;amp;apos;-1-2-&amp;amp;apos;&lt;/p&gt;
&lt;p&gt;When sw1p4 would leave a bridge, dsa_port_vlan_filtering would be
called for sw2 and sw3 with a non-existing port - leading to array
out-of-bounds accesses and crashes on mv88e6xxx.(CVE-2022-49234)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;scsi: target: iscsi: Fix a race condition between login_work and the login thread&lt;/p&gt;
&lt;p&gt;In case a malicious initiator sends some random data immediately after a
login PDU; the iscsi_target_sk_data_ready() callback will schedule the
login_work and, at the same time, the negotiation may end without clearing
the LOGIN_FLAGS_INITIAL_PDU flag (because no additional PDU exchanges are
required to complete the login).&lt;/p&gt;
&lt;p&gt;The login has been completed but the login_work function will find the
LOGIN_FLAGS_INITIAL_PDU flag set and will never stop from rescheduling…&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;net: dsa: Avoid cross-chip syncing of VLAN filtering&lt;/p&gt;
&lt;p&gt;Changes to VLAN filtering are not applicable to cross-chip
notifications.&lt;/p&gt;
&lt;p&gt;On a system like this:&lt;/p&gt;
&lt;p&gt;.-----.   .-----.   .-----.
| sw1 +---+ sw2 +---+ sw3 |
&amp;amp;apos;-1-2-&amp;amp;apos;   &amp;amp;apos;-1-2-&amp;amp;apos;   &amp;amp;apos;-1-2-&amp;amp;apos;&lt;/p&gt;
&lt;p&gt;Before this change, upon sw1p1 leaving a bridge, a call to
dsa_port_vlan_filtering would also be made to sw2p1 and sw3p1.&lt;/p&gt;
&lt;p&gt;In this scenario:&lt;/p&gt;
&lt;p&gt;.---------.   .-----.   .-----.
|   sw1   +---+ sw2 +---+ sw3 |
&amp;amp;apos;-1-2-3-4-&amp;amp;apos;   &amp;amp;apos;-1-2-&amp;amp;apos;   &amp;amp;apos;-1-2-&amp;amp;apos;&lt;/p&gt;
&lt;p&gt;When sw1p4 would leave a bridge, dsa_port_vlan_filtering would be
called for sw2 and sw3 with a non-existing port - leading to array
out-of-bounds accesses and crashes on mv88e6xxx.(CVE-2022-49234)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;scsi: target: iscsi: Fix a race condition between login_work and the login thread&lt;/p&gt;
&lt;p&gt;In case a malicious initiator sends some random data immediately after a
login PDU; the iscsi_target_sk_data_ready() callback will schedule the
login_work and, at the same time, the negotiation may end without clearing
the LOGIN_FLAGS_INITIAL_PDU flag (because no additional PDU exchanges are
required to complete the login).&lt;/p&gt;
&lt;p&gt;The login has been completed but the login_work function will find the
LOGIN_FLAGS_INITIAL_PDU flag set and will never stop from rescheduling…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2025-2407</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-38615</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-38615</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 162 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: cancle set bad inode after removing name fails The reproducer uses a file0 on a ntfs3 file system with a corrupted i_link. When renaming, the file0&amp;#39;s inode is marked as a bad inode because the file name cannot be deleted. The underlying bug is that make_bad_inode() is called on a live inode. In some cases it&amp;#39;s &amp;#34;icache lookup finds a normal inode, d_splice_alias() is called to attach it to dentry, while another thread decides to call make_bad_inode() on it - that would evict it from icache, but we&amp;#39;d already found it there earlier&amp;#34;. In some it&amp;#39;s outright &amp;#34;we have an inode attached to dentry - that&amp;#39;s how we got it in the first place; let&amp;#39;s call make_bad_inode() on it just for shits and giggles&amp;#34;.&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 162 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: cancle set bad inode after removing name fails The reproducer uses a file0 on a ntfs3 file system with a corrupted i_link. When renaming, the file0&amp;#39;s inode is marked as a bad inode because the file name cannot be deleted. The underlying bug is that make_bad_inode() is called on a live inode. In some cases it&amp;#39;s &amp;#34;icache lookup finds a normal inode, d_splice_alias() is called to attach it to dentry, while another thread decides to call make_bad_inode() on it - that would evict it from icache, but we&amp;#39;d already found it there earlier&amp;#34;. In some it&amp;#39;s outright &amp;#34;we have an inode attached to dentry - that&amp;#39;s how we got it in the first place; let&amp;#39;s call make_bad_inode() on it just for shits and giggles&amp;#34;.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-38615</guid>
    </item>
  </channel>
</rss>
