<?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:12:26 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-80782</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-80782</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-80782</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1163 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Certaines d'entre elles permettent à…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-1163</link>
      <description>certfr-2026-avi-1163</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-1163</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-80782</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-80782</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 248 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: HID: magicmouse: do not keep a stale msc-&amp;gt;input if no input is claimed magicmouse_input_mapping() caches the first hid_input&amp;#39;s input_dev in msc-&amp;gt;input while the report descriptor is parsed, and the rest of the driver treats a non-NULL msc-&amp;gt;input as proof that an input device was registered. That does not hold on the hid-input error path. If hidinput_connect() fails -- for instance because input_register_device() returns an error -- it unwinds through hidinput_disconnect(), which frees every input_dev it created, including the one cached in msc-&amp;gt;input. The failure does not abort the probe. hid_connect() only skips the claim: 	if ((connect_mask &amp;amp; HID_CONNECT_HIDINPUT) &amp;amp;&amp;amp; !hidinput_connect(hdev, 				connect_mask &amp;amp; HID_CONNECT_HIDINPUT_FORCE)) 		hdev-&amp;gt;claimed |= HID_CLAIMED_INPUT; and the &amp;#34;device has no listeners&amp;#34; bailout below it does not fire for this driver, which sets -&amp;gt;raw_event; on the USB Magic Mouse 2 / Magic Trackpad 2 paths hidraw and hiddev are claimed as well. hid_hw_start() therefore returns 0 and magicmouse_probe() continues with msc-&amp;gt;input pointing at freed memory. Being non-NULL, it passes the &amp;#34;input not registered&amp;#34; check in probe and the NULL checks in -&amp;gt;raw_event and -&amp;gt;event, so the next input report dereferences freed memory. Clear msc-&amp;gt;input when the HID core did not claim an input device, so the existing NULL checks cover this case as well.&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 248 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: HID: magicmouse: do not keep a stale msc-&amp;gt;input if no input is claimed magicmouse_input_mapping() caches the first hid_input&amp;#39;s input_dev in msc-&amp;gt;input while the report descriptor is parsed, and the rest of the driver treats a non-NULL msc-&amp;gt;input as proof that an input device was registered. That does not hold on the hid-input error path. If hidinput_connect() fails -- for instance because input_register_device() returns an error -- it unwinds through hidinput_disconnect(), which frees every input_dev it created, including the one cached in msc-&amp;gt;input. The failure does not abort the probe. hid_connect() only skips the claim: 	if ((connect_mask &amp;amp; HID_CONNECT_HIDINPUT) &amp;amp;&amp;amp; !hidinput_connect(hdev, 				connect_mask &amp;amp; HID_CONNECT_HIDINPUT_FORCE)) 		hdev-&amp;gt;claimed |= HID_CLAIMED_INPUT; and the &amp;#34;device has no listeners&amp;#34; bailout below it does not fire for this driver, which sets -&amp;gt;raw_event; on the USB Magic Mouse 2 / Magic Trackpad 2 paths hidraw and hiddev are claimed as well. hid_hw_start() therefore returns 0 and magicmouse_probe() continues with msc-&amp;gt;input pointing at freed memory. Being non-NULL, it passes the &amp;#34;input not registered&amp;#34; check in probe and the NULL checks in -&amp;gt;raw_event and -&amp;gt;event, so the next input report dereferences freed memory. Clear msc-&amp;gt;input when the HID core did not claim an input device, so the existing NULL checks cover this case as well.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-80782</guid>
    </item>
  </channel>
</rss>
