<?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-19T19:37:20.033853+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-2026-avi-0316</id>
    <title>certfr-2026-avi-0316 — De multiples vulnérabilités ont été découvertes dans les produits VMware. Elles permettent à un attaquant de provoquer…</title>
    <updated>2026-11-19T19:37:20.050222+00:00</updated>
    <content>certfr-2026-avi-0316</content>
    <link href="https://127.0.0.1:10001/vuln/certfr-2026-avi-0316"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/oesa-2025-2659</id>
    <title>OESA-2025-2659 — kernel security update</title>
    <updated>2026-11-19T19:37:20.050308+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openEuler:20.03-LTS-SP4: 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>misc: tifm: fix possible memory leak in tifm_7xx1_switch_media()</p>
<p>If device_register() returns error in tifm_7xx1_switch_media(),
name of kobject which is allocated in dev_set_name() called in device_add()
is leaked.</p>
<p>Never directly free @dev after calling device_register(), even
if it returned an error! Always use put_device() to give up the
reference initialized.(CVE-2022-50349)</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>net: hns: fix possible memory leak in hnae_ae_register()</p>
<p>Inject fault while probing module, if device_register() fails,
but the refcount of kobject is not decreased to 0, the name
allocated in dev_set_name() is leaked. Fix this by calling
put_device(), so that name can be freed in callback function
kobject_cleanup().</p>
<p>unreferenced object 0xffff00c01aba2100 (size 128):
  comm &amp;quot;systemd-udevd&amp;quot;, pid 1259, jiffies 4294903284 (age 294.152s)
  hex dump (first 32 bytes):
    68 6e 61 65 30 00 00 00 18 21 ba 1a c0 00 ff ff  hnae0....!......
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  backtrace:
    [&amp;lt;0000000034783f26&amp;gt;] slab_post_alloc_hook+0xa0/0x3e0
    [&amp;lt;00000000748188f2&amp;gt;] __kmem_cache_alloc_node+0x164/0x2b0
    [&amp;lt;00000000ab0743e8&amp;gt;] __kmalloc_node_track_caller+0x6c/0x390
    [&amp;lt;000000006c0ffb13&amp;gt;] kvasprintf+0x8c/0x118
    [&amp;lt;00000000…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/oesa-2025-2659"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/ubuntu-cve-2022-50552</id>
    <title>UBUNTU-CVE-2022-50552</title>
    <updated>2026-11-19T19:37:20.050549+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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 143 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: blk-mq: use quiesced elevator switch when reinitializing queues The hctx's run_work may be racing with the elevator switch when reinitializing hardware queues. The queue is merely frozen in this context, but that only prevents requests from allocating and doesn't stop the hctx work from running. The work may get an elevator pointer that's being torn down, and can result in use-after-free errors and kernel panics (example below). Use the quiesced elevator switch instead, and make the previous one static since it is now only used locally.   nvme nvme0: resetting controller   nvme nvme0: 32/0/0 default/read/poll queues   BUG: kernel NULL pointer dereference, address: 0000000000000008   #PF: supervisor read access in kernel mode   #PF: error_code(0x0000) - not-present page   PGD 80000020c8861067 P4D 80000020c8861067 PUD 250f8c8067 PMD 0   Oops: 0000 [#1] SMP PTI   Workqueue: kblockd blk_mq_run_work_fn   RIP: 0010:kyber_has_work+0x29/0x70 ...   Call Trace:    __blk_mq_do_dispatch_sched+0x83/0x2b0    __blk_mq_sched_dispatch_requests+0x12e/0x170    blk_mq_sched_dispatch_requests+0x30/0x60    __blk_mq_run_hw_queue+0x2b/0x50    process_one_work+0x1ef/0x380    worker_thread+0x2d/0x3e0</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2022-50552"/>
  </entry>
</feed>
