<?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 10:41:24 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-46307</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-46307</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-46307</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0783 — De multiples vulnérabilités ont été découvertes dans Microsoft Azure. Elles permettent à un attaquant de provoquer une…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-0783</link>
      <description>certfr-2026-avi-0783</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-0783</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-46307</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-46307</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 255 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: wifi: ath5k: do not access array OOB Vincent reports: &amp;gt; The ath5k driver seems to do an array-index-out-of-bounds access as &amp;gt; shown by the UBSAN kernel message: &amp;gt; UBSAN: array-index-out-of-bounds in drivers/net/wireless/ath/ath5k/base.c:1741:20 &amp;gt; index 4 is out of range for type &amp;#39;ieee80211_tx_rate [4]&amp;#39; &amp;gt; ... &amp;gt; Call Trace: &amp;gt;  &amp;lt;TASK&amp;gt; &amp;gt;  dump_stack_lvl+0x5d/0x80 &amp;gt;  ubsan_epilogue+0x5/0x2b &amp;gt;  __ubsan_handle_out_of_bounds.cold+0x46/0x4b &amp;gt;  ath5k_tasklet_tx+0x4e0/0x560 [ath5k] &amp;gt;  tasklet_action_common+0xb5/0x1c0 It is real. &amp;#39;ts-&amp;gt;ts_final_idx&amp;#39; can be 3 on 5212, so:    info-&amp;gt;status.rates[ts-&amp;gt;ts_final_idx + 1].idx = -1; with the array defined as:    struct ieee80211_tx_rate rates[IEEE80211_TX_MAX_RATES]; while the size is:    #define IEEE80211_TX_MAX_RATES  4 is indeed bogus. Set this &amp;#39;idx = -1&amp;#39; sentinel only if the array index is less than the array size. As mac80211 will not look at rates beyond the size (IEEE80211_TX_MAX_RATES). Note: The effect of the OOB write is negligible. It just overwrites the next member of info-&amp;gt;status, i.e. ack_signal.&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 255 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: wifi: ath5k: do not access array OOB Vincent reports: &amp;gt; The ath5k driver seems to do an array-index-out-of-bounds access as &amp;gt; shown by the UBSAN kernel message: &amp;gt; UBSAN: array-index-out-of-bounds in drivers/net/wireless/ath/ath5k/base.c:1741:20 &amp;gt; index 4 is out of range for type &amp;#39;ieee80211_tx_rate [4]&amp;#39; &amp;gt; ... &amp;gt; Call Trace: &amp;gt;  &amp;lt;TASK&amp;gt; &amp;gt;  dump_stack_lvl+0x5d/0x80 &amp;gt;  ubsan_epilogue+0x5/0x2b &amp;gt;  __ubsan_handle_out_of_bounds.cold+0x46/0x4b &amp;gt;  ath5k_tasklet_tx+0x4e0/0x560 [ath5k] &amp;gt;  tasklet_action_common+0xb5/0x1c0 It is real. &amp;#39;ts-&amp;gt;ts_final_idx&amp;#39; can be 3 on 5212, so:    info-&amp;gt;status.rates[ts-&amp;gt;ts_final_idx + 1].idx = -1; with the array defined as:    struct ieee80211_tx_rate rates[IEEE80211_TX_MAX_RATES]; while the size is:    #define IEEE80211_TX_MAX_RATES  4 is indeed bogus. Set this &amp;#39;idx = -1&amp;#39; sentinel only if the array index is less than the array size. As mac80211 will not look at rates beyond the size (IEEE80211_TX_MAX_RATES). Note: The effect of the OOB write is negligible. It just overwrites the next member of info-&amp;gt;status, i.e. ack_signal.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-46307</guid>
    </item>
  </channel>
</rss>
