<?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 06:03:55 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-64472</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-64472</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-64472</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0981 — 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-2026-avi-0981</link>
      <description>certfr-2026-avi-0981</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-0981</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-64472</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-64472</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 155 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: vfio/mlx5: Fix racy bitfields and tighten struct layout Bitfield operations are not atomic, they use a read-modify-write pattern, therefore we should be careful not to pack bitfields that can be concurrently updated into the same storage unit. This split takes a binary approach: flags that are only modified pre/post open/close remain bitfields, flags modified from user action, including actions that reach across to another device (ex. reset) use dedicated storage units. Note mlx5_vhca_page_tracker.status is relocated to fill the alignment hole this split exposes. Bitfield justifications:   migrate_cap: written only in mlx5vf_cmd_set_migratable() at probe   chunk_mode: written only in mlx5vf_cmd_set_migratable() at probe   mig_state_cap: written only in mlx5vf_cmd_set_migratable() at probe Dedicated storage units:   mdev_detach: written in the VF attach/detach event notifier                mlx5fv_vf_event() at runtime   log_active: written in mlx5vf_start_page_tracker()/               mlx5vf_stop_page_tracker() during runtime dirty tracking   deferred_reset: written in mlx5vf_state_mutex_unlock()/                   mlx5vf_pci_aer_reset_done() during runtime reset handling   is_err: set by tracker error handling and dirty-log polling at runtime   object_changed: set by tracker event handling and cleared by dirty-log                   polling at runtime&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 155 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: vfio/mlx5: Fix racy bitfields and tighten struct layout Bitfield operations are not atomic, they use a read-modify-write pattern, therefore we should be careful not to pack bitfields that can be concurrently updated into the same storage unit. This split takes a binary approach: flags that are only modified pre/post open/close remain bitfields, flags modified from user action, including actions that reach across to another device (ex. reset) use dedicated storage units. Note mlx5_vhca_page_tracker.status is relocated to fill the alignment hole this split exposes. Bitfield justifications:   migrate_cap: written only in mlx5vf_cmd_set_migratable() at probe   chunk_mode: written only in mlx5vf_cmd_set_migratable() at probe   mig_state_cap: written only in mlx5vf_cmd_set_migratable() at probe Dedicated storage units:   mdev_detach: written in the VF attach/detach event notifier                mlx5fv_vf_event() at runtime   log_active: written in mlx5vf_start_page_tracker()/               mlx5vf_stop_page_tracker() during runtime dirty tracking   deferred_reset: written in mlx5vf_state_mutex_unlock()/                   mlx5vf_pci_aer_reset_done() during runtime reset handling   is_err: set by tracker error handling and dirty-log polling at runtime   object_changed: set by tracker event handling and cleared by dirty-log                   polling at runtime&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-64472</guid>
    </item>
  </channel>
</rss>
