<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://127.0.0.1:10001/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-21T02:10:54.900265+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://127.0.0.1:10001" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://127.0.0.1:10001/vuln/certfr-2025-avi-0587</id>
    <title>certfr-2025-avi-0587 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
    <updated>2026-11-21T02:10:54.911848+00:00</updated>
    <content>certfr-2025-avi-0587</content>
    <link href="https://127.0.0.1:10001/vuln/certfr-2025-avi-0587"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/oesa-2025-1821</id>
    <title>OESA-2025-1821 — kernel security update</title>
    <updated>2026-11-21T02:10:54.911896+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openEuler:22.03-LTS-SP3: kernel</p>
<p>The Linux Kernel, the operating system core itself.

Security Fix(es):</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>tty: n_gsm: add sanity check for gsm-&amp;gt;receive in gsm_receive_buf()</p>
<p>A null pointer dereference can happen when attempting to access the
&amp;quot;gsm-&amp;gt;receive()&amp;quot; function in gsmld_receive_buf(). Currently, the code
assumes that gsm-&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;gt;receive() function will not be set and a
NULL pointer dereference will occur.</p>
<p>Fix this by avoiding the call to &amp;quot;gsm-&amp;gt;receive()&amp;quot; in case the function is
not initialized by adding a sanity check.</p>
<p>Call Trace:
 &amp;lt;TASK&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)</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>iio: light: opt3001: fix deadlock due to concurrent flag access</p>
<p>The threaded IRQ function in this driver is reading the flag twice: once to
lock a mutex and once to unlock it. Even thou…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/oesa-2025-1821"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/rxsa-2024:3138</id>
    <title>RXSA-2024:3138 — Moderate: kernel security, bug fix, and enhancement update</title>
    <updated>2026-11-21T02:10:54.912002+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Rocky Linux:8: bpftool, Rocky Linux:8: bpftool-debuginfo, Rocky Linux:8: kernel, Rocky Linux:8: kernel-core, Rocky Linux:8: kernel-debug, Rocky Linux:8: kernel-debug-core, Rocky Linux:8: kernel-debug-debuginfo, Rocky Linux:8: kernel-debug-devel, Rocky Linux:8: kernel-debuginfo, Rocky Linux:8: kernel-debug-modules and 14 more</p>
<p>The kernel packages contain the Linux kernel, the core of any Linux operating system.</p>
<p>Security Fix(es):</p>
<p>For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.</p>
<p>Additional Changes:</p>
<p>For detailed information on changes in this release, see the Rocky Linux SIG Cloud 8.10 Release Notes linked from the References section.</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/rxsa-2024:3138"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/ubuntu-cve-2022-49940</id>
    <title>UBUNTU-CVE-2022-49940</title>
    <updated>2026-11-21T02:10:54.912087+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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 268 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: tty: n_gsm: add sanity check for gsm-&gt;receive in gsm_receive_buf() A null pointer dereference can happen when attempting to access the "gsm-&gt;receive()" function in gsmld_receive_buf(). Currently, the code assumes that gsm-&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-&gt;receive() function will not be set and a NULL pointer dereference will occur. Fix this by avoiding the call to "gsm-&gt;receive()" in case the function is not initialized by adding a sanity check. Call Trace:  &lt;TASK&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</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2022-49940"/>
  </entry>
</feed>
