<?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:50:55 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2025-38170</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-38170</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-38170</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0698 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Certaines d'entre elles permettent à un…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2025-avi-0698</link>
      <description>certfr-2025-avi-0698</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0698</guid>
    </item>
    <item>
      <title>OESA-2025-1821 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2025-1821</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP3: 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;tty: n_gsm: add sanity check for gsm-&amp;amp;gt;receive in gsm_receive_buf()&lt;/p&gt;
&lt;p&gt;A null pointer dereference can happen when attempting to access the
&amp;amp;quot;gsm-&amp;amp;gt;receive()&amp;amp;quot; function in gsmld_receive_buf(). Currently, the code
assumes that gsm-&amp;amp;gt;recieve is only called after MUX activation.
Since the gsmld_receive_buf() function can be accessed without the need to
initialize the MUX, the gsm-&amp;amp;gt;receive() function will not be set and a
NULL pointer dereference will occur.&lt;/p&gt;
&lt;p&gt;Fix this by avoiding the call to &amp;amp;quot;gsm-&amp;amp;gt;receive()&amp;amp;quot; in case the function is
not initialized by adding a sanity check.&lt;/p&gt;
&lt;p&gt;Call Trace:
 &amp;amp;lt;TASK&amp;amp;gt;
 gsmld_receive_buf+0x1c2/0x2f0 drivers/tty/n_gsm.c:2861
 tiocsti drivers/tty/tty_io.c:2293 [inline]
 tty_ioctl+0xa75/0x15d0 drivers/tty/tty_io.c:2692
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:870 [inline]
 __se_sys_ioctl fs/ioctl.c:856 [inline]
 __x64_sys_ioctl+0x193/0x200 fs/ioctl.c:856
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd(CVE-2022-49940)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;iio: light: opt3001: fix deadlock due to concurrent flag access&lt;/p&gt;
&lt;p&gt;The threaded IRQ function in this driver is reading the flag twice: once to
lock a mutex and once to unlock it. Even thou…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP3: 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;tty: n_gsm: add sanity check for gsm-&amp;amp;gt;receive in gsm_receive_buf()&lt;/p&gt;
&lt;p&gt;A null pointer dereference can happen when attempting to access the
&amp;amp;quot;gsm-&amp;amp;gt;receive()&amp;amp;quot; function in gsmld_receive_buf(). Currently, the code
assumes that gsm-&amp;amp;gt;recieve is only called after MUX activation.
Since the gsmld_receive_buf() function can be accessed without the need to
initialize the MUX, the gsm-&amp;amp;gt;receive() function will not be set and a
NULL pointer dereference will occur.&lt;/p&gt;
&lt;p&gt;Fix this by avoiding the call to &amp;amp;quot;gsm-&amp;amp;gt;receive()&amp;amp;quot; in case the function is
not initialized by adding a sanity check.&lt;/p&gt;
&lt;p&gt;Call Trace:
 &amp;amp;lt;TASK&amp;amp;gt;
 gsmld_receive_buf+0x1c2/0x2f0 drivers/tty/n_gsm.c:2861
 tiocsti drivers/tty/tty_io.c:2293 [inline]
 tty_ioctl+0xa75/0x15d0 drivers/tty/tty_io.c:2692
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:870 [inline]
 __se_sys_ioctl fs/ioctl.c:856 [inline]
 __x64_sys_ioctl+0x193/0x200 fs/ioctl.c:856
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd(CVE-2022-49940)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;iio: light: opt3001: fix deadlock due to concurrent flag access&lt;/p&gt;
&lt;p&gt;The threaded IRQ function in this driver is reading the flag twice: once to
lock a mutex and once to unlock it. Even thou…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2025-1821</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-38170</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-38170</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 121 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: arm64/fpsimd: Discard stale CPU state when handling SME traps The logic for handling SME traps manipulates saved FPSIMD/SVE/SME state incorrectly, and a race with preemption can result in a task having TIF_SME set and TIF_FOREIGN_FPSTATE clear even though the live CPU state is stale (e.g. with SME traps enabled). This can result in warnings from do_sme_acc() where SME traps are not expected while TIF_SME is set: |        /* With TIF_SME userspace shouldn&amp;#39;t generate any traps */ |        if (test_and_set_thread_flag(TIF_SME)) |                WARN_ON(1); This is very similar to the SVE issue we fixed in commit:   751ecf6afd6568ad (&amp;#34;arm64/sve: Discard stale CPU state when handling SVE traps&amp;#34;) The race can occur when the SME trap handler is preempted before and after manipulating the saved FPSIMD/SVE/SME state, starting and ending on the same CPU, e.g. | void do_sme_acc(unsigned long esr, struct pt_regs *regs) | { |         // Trap on CPU 0 with TIF_SME clear, SME traps enabled |         // task-&amp;gt;fpsimd_cpu is 0. |         // per_cpu_ptr(&amp;amp;fpsimd_last_state, 0) is task. | |         ... | |         // Preempted; migrated from CPU 0 to CPU 1. |         // TIF_FOREIGN_FPSTATE is set. | |         get_cpu_fpsimd_context(); | |         /* With TIF_SME userspace shouldn&amp;#39;t generate any traps */ |         if (test_and_set_thread_flag(TIF_SME)) |                 WARN_ON(1); | |         if (!test_thread_flag(TIF_FOREIGN_FP…&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 121 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: arm64/fpsimd: Discard stale CPU state when handling SME traps The logic for handling SME traps manipulates saved FPSIMD/SVE/SME state incorrectly, and a race with preemption can result in a task having TIF_SME set and TIF_FOREIGN_FPSTATE clear even though the live CPU state is stale (e.g. with SME traps enabled). This can result in warnings from do_sme_acc() where SME traps are not expected while TIF_SME is set: |        /* With TIF_SME userspace shouldn&amp;#39;t generate any traps */ |        if (test_and_set_thread_flag(TIF_SME)) |                WARN_ON(1); This is very similar to the SVE issue we fixed in commit:   751ecf6afd6568ad (&amp;#34;arm64/sve: Discard stale CPU state when handling SVE traps&amp;#34;) The race can occur when the SME trap handler is preempted before and after manipulating the saved FPSIMD/SVE/SME state, starting and ending on the same CPU, e.g. | void do_sme_acc(unsigned long esr, struct pt_regs *regs) | { |         // Trap on CPU 0 with TIF_SME clear, SME traps enabled |         // task-&amp;gt;fpsimd_cpu is 0. |         // per_cpu_ptr(&amp;amp;fpsimd_last_state, 0) is task. | |         ... | |         // Preempted; migrated from CPU 0 to CPU 1. |         // TIF_FOREIGN_FPSTATE is set. | |         get_cpu_fpsimd_context(); | |         /* With TIF_SME userspace shouldn&amp;#39;t generate any traps */ |         if (test_and_set_thread_flag(TIF_SME)) |                 WARN_ON(1); | |         if (!test_thread_flag(TIF_FOREIGN_FP…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-38170</guid>
    </item>
  </channel>
</rss>
