<?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-21T03:59:31.994360+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/bell-cve-2024-56670</id>
    <title>BELL-CVE-2024-56670</title>
    <updated>2026-11-21T03:59:32.003086+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p>
      </div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/bell-cve-2024-56670"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/certfr-2025-avi-0088</id>
    <title>certfr-2025-avi-0088 — 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-21T03:59:32.003123+00:00</updated>
    <content>certfr-2025-avi-0088</content>
    <link href="https://127.0.0.1:10001/vuln/certfr-2025-avi-0088"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/oesa-2025-1339</id>
    <title>OESA-2025-1339 — kernel security update</title>
    <updated>2026-11-21T03:59:32.003139+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openEuler:24.03-LTS: 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>dma-debug: fix a possible deadlock on radix_lock</p>
<p>radix_lock() shouldn&amp;apos;t be held while holding dma_hash_entry[idx].lock
otherwise, there&amp;apos;s a possible deadlock scenario when
dma debug API is called holding rq_lock():</p>
<p>CPU0                   CPU1                       CPU2
dma_free_attrs()
check_unmap()          add_dma_entry()            __schedule() //out
                                                  (A) rq_lock()
get_hash_bucket()
(A) dma_entry_hash
                                                  check_sync()
                       (A) radix_lock()           (W) dma_entry_hash
dma_entry_free()
(W) radix_lock()
                       // CPU2&amp;apos;s one
                       (W) rq_lock()</p>
<p>CPU1 situation can happen when it extending radix tree and
it tries to wake up kswapd via wake_all_kswapd().</p>
<p>CPU2 situation can happen while perf_event_task_sched_out()
(i.e. dma sync operation is called while deleting perf_event using
 etm and etr tmc which are Arm Coresight hwtracing driver backends).</p>
<p>To remove this possible situation, call dma_entry_free() after
put_hash_bucket() in check_unmap().(CVE-2024-47143)</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>dlm: fix possible lkb_resource null dereference</p>
<p>This patch fixes a possible null pointer dereference when this function is
called from request_lock(…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/oesa-2025-1339"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-56670</id>
    <title>UBUNTU-CVE-2024-56670</title>
    <updated>2026-11-21T03:59:32.003429+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 196 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: usb: gadget: u_serial: Fix the issue that gs_start_io crashed due to accessing null pointer Considering that in some extreme cases, when u_serial driver is accessed by multiple threads, Thread A is executing the open operation and calling the gs_open, Thread B is executing the disconnect operation and calling the gserial_disconnect function,The port-&gt;port_usb pointer will be set to NULL. E.g.     Thread A                                 Thread B     gs_open()                                gadget_unbind_driver()     gs_start_io()                            composite_disconnect()     gs_start_rx()                            gserial_disconnect()     ...                                      ...     spin_unlock(&amp;port-&gt;port_lock)     status = usb_ep_queue()                  spin_lock(&amp;port-&gt;port_lock)     spin_lock(&amp;port-&gt;port_lock)              port-&gt;port_usb = NULL     gs_free_requests(port-&gt;port_usb-&gt;in)     spin_unlock(&amp;port-&gt;port_lock)     Crash This causes thread A to access a null pointer (port-&gt;port_usb is null) when calling the gs_free_requests function, causing a crash. If port_usb is NULL, the release request will be skipped as it will be done by gserial_disconnect. So add a null pointer check to gs_start_io before attempting to access the value of the pointer port-&gt;port_usb. Call trace:  gs_start_io+0x164/0x25c  gs_open+0x108/0x13c  tty_open+0x314/0x638  chrdev_open+0x1b8/0x258  do_dentry_open+0x2c4/0…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2024-56670"/>
  </entry>
</feed>
