<?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 00:10:21 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2025-21899</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-21899</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-2025-21899</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0333 — 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-2025-avi-0333</link>
      <description>certfr-2025-avi-0333</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0333</guid>
    </item>
    <item>
      <title>OESA-2025-1446 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2025-1446</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP1: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ntb_hw_switchtec: Fix shift-out-of-bounds in switchtec_ntb_mw_set_trans&lt;/p&gt;
&lt;p&gt;There is a kernel API ntb_mw_clear_trans() would pass 0 to both addr and
size. This would make xlate_pos negative.&lt;/p&gt;
&lt;p&gt;[   23.734156] switchtec switchtec0: MW 0: part 0 addr 0x0000000000000000 size 0x0000000000000000
[   23.734158] ================================================================================
[   23.734172] UBSAN: shift-out-of-bounds in drivers/ntb/hw/mscc/ntb_hw_switchtec.c:293:7
[   23.734418] shift exponent -1 is negative&lt;/p&gt;
&lt;p&gt;Ensuring xlate_pos is a positive or zero before BIT.(CVE-2023-53034)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/msm/gem: prevent integer overflow in msm_ioctl_gem_submit()&lt;/p&gt;
&lt;p&gt;The &amp;amp;quot;submit-&amp;amp;gt;cmd[i].size&amp;amp;quot; and &amp;amp;quot;submit-&amp;amp;gt;cmd[i].offset&amp;amp;quot; variables are u32
values that come from the user via the submit_lookup_cmds() function.
This addition could lead to an integer wrapping bug so use size_add()
to prevent that.&lt;/p&gt;
&lt;p&gt;Patchwork: https://patchwork.freedesktop.org/patch/624696/(CVE-2024-52559)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;fs/ntfs3: Mark inode as bad as soon as error detected in mi_enum_attr()&lt;/p&gt;
&lt;p&gt;Extended the `mi_enum_attr()` function interface with an additional
parameter, `struct ntfs_inode *ni`, to allow marking the inode
as bad as soon as an error i…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP1: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ntb_hw_switchtec: Fix shift-out-of-bounds in switchtec_ntb_mw_set_trans&lt;/p&gt;
&lt;p&gt;There is a kernel API ntb_mw_clear_trans() would pass 0 to both addr and
size. This would make xlate_pos negative.&lt;/p&gt;
&lt;p&gt;[   23.734156] switchtec switchtec0: MW 0: part 0 addr 0x0000000000000000 size 0x0000000000000000
[   23.734158] ================================================================================
[   23.734172] UBSAN: shift-out-of-bounds in drivers/ntb/hw/mscc/ntb_hw_switchtec.c:293:7
[   23.734418] shift exponent -1 is negative&lt;/p&gt;
&lt;p&gt;Ensuring xlate_pos is a positive or zero before BIT.(CVE-2023-53034)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/msm/gem: prevent integer overflow in msm_ioctl_gem_submit()&lt;/p&gt;
&lt;p&gt;The &amp;amp;quot;submit-&amp;amp;gt;cmd[i].size&amp;amp;quot; and &amp;amp;quot;submit-&amp;amp;gt;cmd[i].offset&amp;amp;quot; variables are u32
values that come from the user via the submit_lookup_cmds() function.
This addition could lead to an integer wrapping bug so use size_add()
to prevent that.&lt;/p&gt;
&lt;p&gt;Patchwork: https://patchwork.freedesktop.org/patch/624696/(CVE-2024-52559)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;fs/ntfs3: Mark inode as bad as soon as error detected in mi_enum_attr()&lt;/p&gt;
&lt;p&gt;Extended the `mi_enum_attr()` function interface with an additional
parameter, `struct ntfs_inode *ni`, to allow marking the inode
as bad as soon as an error i…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2025-1446</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-21899</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-21899</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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 175 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: tracing: Fix bad hist from corrupting named_triggers list The following commands causes a crash:  ~# cd /sys/kernel/tracing/events/rcu/rcu_callback  ~# echo &amp;#39;hist:name=bad:keys=common_pid:onmax(bogus).save(common_pid)&amp;#39; &amp;gt; trigger  bash: echo: write error: Invalid argument  ~# echo &amp;#39;hist:name=bad:keys=common_pid&amp;#39; &amp;gt; trigger Because the following occurs: event_trigger_write() {   trigger_process_regex() {     event_hist_trigger_parse() {       data = event_trigger_alloc(..);       event_trigger_register(.., data) {         cmd_ops-&amp;gt;reg(.., data, ..) [hist_register_trigger()] {           data-&amp;gt;ops-&amp;gt;init() [event_hist_trigger_init()] {             save_named_trigger(name, data) {               list_add(&amp;amp;data-&amp;gt;named_list, &amp;amp;named_triggers);             }           }         }       }       ret = create_actions(); (return -EINVAL)       if (ret)         goto out_unreg; [..]       ret = hist_trigger_enable(data, ...) {         list_add_tail_rcu(&amp;amp;data-&amp;gt;list, &amp;amp;file-&amp;gt;triggers); &amp;lt;&amp;lt;&amp;lt;---- SKIPPED!!! (this is important!) [..]  out_unreg:       event_hist_unregister(.., data) {         cmd_ops-&amp;gt;unreg(.., data, ..) [hist_unregister_trigger()] {           list_for_each_entry(iter, &amp;amp;file-&amp;gt;triggers, list) {             if (!hist_trigger_match(data, iter, named_data, false))   &amp;lt;- never matches                 continue;             [..]             test = iter;           }           if (test &amp;amp;&amp;amp; test-&amp;gt;ops-&amp;gt;free) &amp;lt;&amp;lt;&amp;lt;-- test is NULL…&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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 175 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: tracing: Fix bad hist from corrupting named_triggers list The following commands causes a crash:  ~# cd /sys/kernel/tracing/events/rcu/rcu_callback  ~# echo &amp;#39;hist:name=bad:keys=common_pid:onmax(bogus).save(common_pid)&amp;#39; &amp;gt; trigger  bash: echo: write error: Invalid argument  ~# echo &amp;#39;hist:name=bad:keys=common_pid&amp;#39; &amp;gt; trigger Because the following occurs: event_trigger_write() {   trigger_process_regex() {     event_hist_trigger_parse() {       data = event_trigger_alloc(..);       event_trigger_register(.., data) {         cmd_ops-&amp;gt;reg(.., data, ..) [hist_register_trigger()] {           data-&amp;gt;ops-&amp;gt;init() [event_hist_trigger_init()] {             save_named_trigger(name, data) {               list_add(&amp;amp;data-&amp;gt;named_list, &amp;amp;named_triggers);             }           }         }       }       ret = create_actions(); (return -EINVAL)       if (ret)         goto out_unreg; [..]       ret = hist_trigger_enable(data, ...) {         list_add_tail_rcu(&amp;amp;data-&amp;gt;list, &amp;amp;file-&amp;gt;triggers); &amp;lt;&amp;lt;&amp;lt;---- SKIPPED!!! (this is important!) [..]  out_unreg:       event_hist_unregister(.., data) {         cmd_ops-&amp;gt;unreg(.., data, ..) [hist_unregister_trigger()] {           list_for_each_entry(iter, &amp;amp;file-&amp;gt;triggers, list) {             if (!hist_trigger_match(data, iter, named_data, false))   &amp;lt;- never matches                 continue;             [..]             test = iter;           }           if (test &amp;amp;&amp;amp; test-&amp;gt;ops-&amp;gt;free) &amp;lt;&amp;lt;&amp;lt;-- test is NULL…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-21899</guid>
    </item>
  </channel>
</rss>
