<?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:46:29.289804+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/oesa-2026-1341</id>
    <title>OESA-2026-1341 — kernel security update</title>
    <updated>2026-11-21T02:46:29.293730+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openEuler:22.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:kernel/resource: fix kfree() of bootmem memory againSince commit ebff7d8f270d ( mem hotunplug: fix kfree() of bootmemmemory ), we could get a resource allocated during boot viaalloc_resource().  And it s required to release the resource usingfree_resource().  Howerver, many people use kfree directly which willresult in kernel BUG.  In order to fix this without fixing every callsite, just leak a couple of bytes in such corner case.(CVE-2022-49190)</p>
<p>In the Linux kernel, the following vulnerability has been resolved:drivers: staging: rtl8723bs: Fix deadlock in rtw_surveydone_event_callback()There is a deadlock in rtw_surveydone_event_callback(),which is shown below:   (Thread 1)                  |      (Thread 2)                               | _set_timer()rtw_surveydone_event_callback()|  mod_timer() spin_lock_bh() //(1)          |  (wait a time) ...                           | rtw_scan_timeout_handler() del_timer_sync()              |  spin_lock_bh() //(2) (wait timer to stop)          |  ...We hold pmlmepriv-&amp;gt;lock in position (1) of thread 1 and usedel_timer_sync() to wait timer to stop, but timer handleralso need pmlmepriv-&amp;gt;lock in position (2) of thread 2.As a result, rtw_surveydone_event_callback() will block forever.This patch extracts del_timer_sync() from the protection ofspin_lock_bh(), which could let timer handler to obta…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/oesa-2026-1341"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/ubuntu-cve-2022-50159</id>
    <title>UBUNTU-CVE-2022-50159</title>
    <updated>2026-11-21T02:46:29.294286+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux-azure, 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, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 140 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: of: check previous kernel's ima-kexec-buffer against memory bounds Presently ima_get_kexec_buffer() doesn't check if the previous kernel's ima-kexec-buffer lies outside the addressable memory range. This can result in a kernel panic if the new kernel is booted with 'mem=X' arg and the ima-kexec-buffer was allocated beyond that range by the previous kernel. The panic is usually of the form below: $ sudo kexec --initrd initrd vmlinux --append='mem=16G' &lt;snip&gt;  BUG: Unable to handle kernel data access on read at 0xc000c01fff7f0000  Faulting instruction address: 0xc000000000837974  Oops: Kernel access of bad area, sig: 11 [#1] &lt;snip&gt;  NIP [c000000000837974] ima_restore_measurement_list+0x94/0x6c0  LR [c00000000083b55c] ima_load_kexec_buffer+0xac/0x160  Call Trace:  [c00000000371fa80] [c00000000083b55c] ima_load_kexec_buffer+0xac/0x160  [c00000000371fb00] [c0000000020512c4] ima_init+0x80/0x108  [c00000000371fb70] [c0000000020514dc] init_ima+0x4c/0x120  [c00000000371fbf0] [c000000000012240] do_one_initcall+0x60/0x2c0  [c00000000371fcc0] [c000000002004ad0] kernel_init_freeable+0x344/0x3ec  [c00000000371fda0] [c0000000000128a4] kernel_init+0x34/0x1b0  [c00000000371fe10] [c00000000000ce64] ret_from_kernel_thread+0x5c/0x64  Instruction dump:  f92100b8 f92100c0 90e10090 910100a0 4182050c 282a0017 3bc00000 40810330  7c0802a6 fb610198 7c9b2378 f80101d0 &lt;a1240000&gt; 2c090001 40820614 e9240010  ---[ end trace 000000000000000…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2022-50159"/>
  </entry>
</feed>
