<?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>Fri, 20 Nov 2026 23:50:52 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2024-26687</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-26687</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-2024-26687</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0334 — De multiples vulnérabilités ont été découvertes dans &lt;span
class="textit"&gt;le noyau Linux de Debian&lt;/span&gt;. Elles permet…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2024-avi-0334</link>
      <description>certfr-2024-avi-0334</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2024-avi-0334</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-26687</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-26687</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:14.04:LTS: linux, 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 160 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: xen/events: close evtchn after mapping cleanup shutdown_pirq and startup_pirq are not taking the irq_mapping_update_lock because they can&amp;#39;t due to lock inversion. Both are called with the irq_desc-&amp;gt;lock being taking. The lock order, however, is first irq_mapping_update_lock and then irq_desc-&amp;gt;lock. This opens multiple races: - shutdown_pirq can be interrupted by a function that allocates an event   channel:   CPU0                        CPU1   shutdown_pirq {     xen_evtchn_close(e)                               __startup_pirq {                                 EVTCHNOP_bind_pirq                                   -&amp;gt; returns just freed evtchn e                                 set_evtchn_to_irq(e, irq)                               }     xen_irq_info_cleanup() {       set_evtchn_to_irq(e, -1)     }   }   Assume here event channel e refers here to the same event channel   number.   After this race the evtchn_to_irq mapping for e is invalid (-1). - __startup_pirq races with __unbind_from_irq in a similar way. Because   __startup_pirq doesn&amp;#39;t take irq_mapping_update_lock it can grab the   evtchn that __unbind_from_irq is currently freeing and cleaning up. In   this case even though the event channel is allocated, its mapping can   be unset in evtchn_to_irq. The fix is to first cleanup the mappings and then close the event channel. In this way, when an event channel gets allocated it&amp;#39;s potential previous evtchn_to_…&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:14.04:LTS: linux, 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 160 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: xen/events: close evtchn after mapping cleanup shutdown_pirq and startup_pirq are not taking the irq_mapping_update_lock because they can&amp;#39;t due to lock inversion. Both are called with the irq_desc-&amp;gt;lock being taking. The lock order, however, is first irq_mapping_update_lock and then irq_desc-&amp;gt;lock. This opens multiple races: - shutdown_pirq can be interrupted by a function that allocates an event   channel:   CPU0                        CPU1   shutdown_pirq {     xen_evtchn_close(e)                               __startup_pirq {                                 EVTCHNOP_bind_pirq                                   -&amp;gt; returns just freed evtchn e                                 set_evtchn_to_irq(e, irq)                               }     xen_irq_info_cleanup() {       set_evtchn_to_irq(e, -1)     }   }   Assume here event channel e refers here to the same event channel   number.   After this race the evtchn_to_irq mapping for e is invalid (-1). - __startup_pirq races with __unbind_from_irq in a similar way. Because   __startup_pirq doesn&amp;#39;t take irq_mapping_update_lock it can grab the   evtchn that __unbind_from_irq is currently freeing and cleaning up. In   this case even though the event channel is allocated, its mapping can   be unset in evtchn_to_irq. The fix is to first cleanup the mappings and then close the event channel. In this way, when an event channel gets allocated it&amp;#39;s potential previous evtchn_to_…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-26687</guid>
    </item>
  </channel>
</rss>
