<?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 15:56:55 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2025-21827</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-21827</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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: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-21827</guid>
    </item>
    <item>
      <title>certfr-2025-avi-1057 — De multiples vulnérabilités ont été découvertes dans les produits VMware. Elles permettent à un attaquant de provoquer…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2025-avi-1057</link>
      <description>certfr-2025-avi-1057</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-1057</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-21827</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-21827</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 75 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btusb: mediatek: Add locks for usb_driver_claim_interface() The documentation for usb_driver_claim_interface() says that &amp;#34;the device lock&amp;#34; is needed when the function is called from places other than probe(). This appears to be the lock for the USB interface device. The Mediatek btusb code gets called via this path:   Workqueue: hci0 hci_power_on [bluetooth]   Call trace:    usb_driver_claim_interface    btusb_mtk_claim_iso_intf    btusb_mtk_setup    hci_dev_open_sync    hci_power_on    process_scheduled_works    worker_thread    kthread With the above call trace the device lock hasn&amp;#39;t been claimed. Claim it. Without this fix, we&amp;#39;d sometimes see the error &amp;#34;Failed to claim iso interface&amp;#34;. Sometimes we&amp;#39;d even see worse errors, like a NULL pointer dereference (where `intf-&amp;gt;dev.driver` was NULL) with a trace like:   Call trace:    usb_suspend_both    usb_runtime_suspend    __rpm_callback    rpm_suspend    pm_runtime_work    process_scheduled_works Both errors appear to be fixed with the proper locking.&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 75 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btusb: mediatek: Add locks for usb_driver_claim_interface() The documentation for usb_driver_claim_interface() says that &amp;#34;the device lock&amp;#34; is needed when the function is called from places other than probe(). This appears to be the lock for the USB interface device. The Mediatek btusb code gets called via this path:   Workqueue: hci0 hci_power_on [bluetooth]   Call trace:    usb_driver_claim_interface    btusb_mtk_claim_iso_intf    btusb_mtk_setup    hci_dev_open_sync    hci_power_on    process_scheduled_works    worker_thread    kthread With the above call trace the device lock hasn&amp;#39;t been claimed. Claim it. Without this fix, we&amp;#39;d sometimes see the error &amp;#34;Failed to claim iso interface&amp;#34;. Sometimes we&amp;#39;d even see worse errors, like a NULL pointer dereference (where `intf-&amp;gt;dev.driver` was NULL) with a trace like:   Call trace:    usb_suspend_both    usb_runtime_suspend    __rpm_callback    rpm_suspend    pm_runtime_work    process_scheduled_works Both errors appear to be fixed with the proper locking.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-21827</guid>
    </item>
  </channel>
</rss>
