<?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://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-28T09:09:37.881222+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" 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://vulnerability.circl.lu/vuln/CERTFR-2025-AVI-0529</id>
    <title>CERTFR-2025-AVI-0529 — 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-09-28T09:09:42.030788+00:00</updated>
    <content>CERTFR-2025-AVI-0529</content>
    <link href="https://vulnerability.circl.lu/vuln/CERTFR-2025-AVI-0529"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/fkie_cve-2022-49837</id>
    <title>fkie_cve-2022-49837</title>
    <updated>2026-09-28T09:09:42.030923+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>bpf: Fix memory leaks in __check_func_call</p>
<p>kmemleak reports this issue:</p>
<p>unreferenced object 0xffff88817139d000 (size 2048):
  comm "test_progs", pid 33246, jiffies 4307381979 (age 45851.820s)
  hex dump (first 32 bytes):
    01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  backtrace:
    [&lt;0000000045f075f0&gt;] kmalloc_trace+0x27/0xa0
    [&lt;0000000098b7c90a&gt;] __check_func_call+0x316/0x1230
    [&lt;00000000b4c3c403&gt;] check_helper_call+0x172e/0x4700
    [&lt;00000000aa3875b7&gt;] do_check+0x21d8/0x45e0
    [&lt;000000001147357b&gt;] do_check_common+0x767/0xaf0
    [&lt;00000000b5a595b4&gt;] bpf_check+0x43e3/0x5bc0
    [&lt;0000000011e391b1&gt;] bpf_prog_load+0xf26/0x1940
    [&lt;0000000007f765c0&gt;] __sys_bpf+0xd2c/0x3650
    [&lt;00000000839815d6&gt;] __x64_sys_bpf+0x75/0xc0
    [&lt;00000000946ee250&gt;] do_syscall_64+0x3b/0x90
    [&lt;0000000000506b7f&gt;] entry_SYSCALL_64_after_hwframe+0x63/0xcd</p>
<p>The root case here is: In function prepare_func_exit(), the callee is
not released in the abnormal scenario after "state-&gt;curframe--;". To
fix, move "state-&gt;curframe--;" to the very bottom of the function,
right when we free callee and reset frame[] pointer to NULL, as Andrii
suggested.</p>
<p>In addition, function __check_func_call() has a similar problem. In
the abnormal scenario before "state-&gt;curframe++;", the callee also
should be released by free_func_state().</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/fkie_cve-2022-49837"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-vvp4-j3wj-9jvq</id>
    <title>GHSA-vvp4-j3wj-9jvq</title>
    <updated>2026-09-28T09:09:42.031066+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>bpf: Fix memory leaks in __check_func_call</p>
<p>kmemleak reports this issue:</p>
<p>unreferenced object 0xffff88817139d000 (size 2048):
  comm "test_progs", pid 33246, jiffies 4307381979 (age 45851.820s)
  hex dump (first 32 bytes):
    01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  backtrace:
    [&lt;0000000045f075f0&gt;] kmalloc_trace+0x27/0xa0
    [&lt;0000000098b7c90a&gt;] __check_func_call+0x316/0x1230
    [&lt;00000000b4c3c403&gt;] check_helper_call+0x172e/0x4700
    [&lt;00000000aa3875b7&gt;] do_check+0x21d8/0x45e0
    [&lt;000000001147357b&gt;] do_check_common+0x767/0xaf0
    [&lt;00000000b5a595b4&gt;] bpf_check+0x43e3/0x5bc0
    [&lt;0000000011e391b1&gt;] bpf_prog_load+0xf26/0x1940
    [&lt;0000000007f765c0&gt;] __sys_bpf+0xd2c/0x3650
    [&lt;00000000839815d6&gt;] __x64_sys_bpf+0x75/0xc0
    [&lt;00000000946ee250&gt;] do_syscall_64+0x3b/0x90
    [&lt;0000000000506b7f&gt;] entry_SYSCALL_64_after_hwframe+0x63/0xcd</p>
<p>The root case here is: In function prepare_func_exit(), the callee is
not released in the abnormal scenario after "state-&gt;curframe--;". To
fix, move "state-&gt;curframe--;" to the very bottom of the function,
right when we free callee and reset frame[] pointer to NULL, as Andrii
suggested.</p>
<p>In addition, function __check_func_call() has a similar problem. In
the abnormal scenario before "state-&gt;curframe++;", the callee also
should be released by free_func_state().</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-vvp4-j3wj-9jvq"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/rhsa-2023:6583</id>
    <title>RHSA-2023:6583 — Red Hat Security Advisory: kernel security, bug fix, and enhancement update</title>
    <updated>2026-09-28T09:09:42.031165+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>kernel: seg6: fix the iif in the IPv6 socket control block Kernel: race when faulting a device private page in memory manager kernel: use-after-free in l1oip timer handlers kernel: Rate limit overflow messages in r8152 in intr_callback kernel: vmwgfx: use-after-free in vmw_cmd_res_check kernel: vmwgfx: use-after-free in vmw_execbuf_tie_context hw: Intel: Gather Data Sampling (GDS) side channel vulnerability kernel: Information leak in l2cap_parse_conf_req in net/bluetooth/l2cap_core.c kernel: perf: Fix perf_pending_task() UaF kernel: gpiolib: fix memory leak in gpiochip_setup_dev() kernel: memcg: fix possible use-after-free in memcg_write_event_control() kernel: mm/khugepaged: invoke MMU notifiers in shmem/file collapse paths kernel: char: tpm: Protect tpm_pm_suspend with locks kernel: ixgbevf: Fix resource leak in ixgbevf_init_module() kernel: dax: make sure inodes are flushed before destroy cache kernel: watch_queue: Actually free the watch kernel: watch_queue: Fix NULL dereference in error cleanup kernel: rtc: pl031: fix rtc features null pointer dereference kernel: tpm: fix reference counting for struct tpm_chip kernel: NFSv4: Don't hold the layoutget locks across multiple RPC calls kernel: xprtrdma: treat all calls not a bcall when bc_serv is NULL kernel: net: ipv6: unexport __init-annotated seg6_hmac_init() kernel: af_unix: Fix a data-race in unix_dgram_peer_wake_me(). kernel: regulator: scmi: Fix refcount leak in scmi_regulator_probe kernel: mm/mempolicy: fix uninit-v…</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/rhsa-2023:6583"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/suse-su-2025:01966-1</id>
    <title>SUSE-SU-2025:01966-1 — Security update for the Linux Kernel</title>
    <updated>2026-09-28T09:09:42.033141+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Security update for the Linux Kernel</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/suse-su-2025:01966-1"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ubuntu-cve-2022-49837</id>
    <title>UBUNTU-CVE-2022-49837</title>
    <updated>2026-09-28T09:09:42.033425+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 121 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: bpf: Fix memory leaks in __check_func_call kmemleak reports this issue: unreferenced object 0xffff88817139d000 (size 2048):   comm "test_progs", pid 33246, jiffies 4307381979 (age 45851.820s)   hex dump (first 32 bytes):     01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................     00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................   backtrace:     [&lt;0000000045f075f0&gt;] kmalloc_trace+0x27/0xa0     [&lt;0000000098b7c90a&gt;] __check_func_call+0x316/0x1230     [&lt;00000000b4c3c403&gt;] check_helper_call+0x172e/0x4700     [&lt;00000000aa3875b7&gt;] do_check+0x21d8/0x45e0     [&lt;000000001147357b&gt;] do_check_common+0x767/0xaf0     [&lt;00000000b5a595b4&gt;] bpf_check+0x43e3/0x5bc0     [&lt;0000000011e391b1&gt;] bpf_prog_load+0xf26/0x1940     [&lt;0000000007f765c0&gt;] __sys_bpf+0xd2c/0x3650     [&lt;00000000839815d6&gt;] __x64_sys_bpf+0x75/0xc0     [&lt;00000000946ee250&gt;] do_syscall_64+0x3b/0x90     [&lt;0000000000506b7f&gt;] entry_SYSCALL_64_after_hwframe+0x63/0xcd The root case here is: In function prepare_func_exit(), the callee is not released in the abnormal scenario after "state-&gt;curframe--;". To fix, move "state-&gt;curframe--;" to the very bottom of the function, right when we free callee and reset frame[] pointer to NULL, as Andrii suggested. In addition, function __check_func_call() has a similar problem. In the abnormal scenario before "state-&gt;curframe++;", the callee also should be released by free_func_state().</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ubuntu-cve-2022-49837"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/wid-sec-w-2025-0922</id>
    <title>WID-SEC-W-2025-0922 — Linux Kernel: Mehrere Schwachstellen</title>
    <updated>2026-09-28T09:09:42.033995+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff und nicht näher spezifizierte Angriffe durchzuführen.</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/wid-sec-w-2025-0922"/>
  </entry>
</feed>
