<?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-21T11:46:31.374677+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-2023-53623</id>
    <title>BELL-CVE-2023-53623</title>
    <updated>2026-11-21T11:46:31.378976+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:stream: linux-lts</p>
      </div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/bell-cve-2023-53623"/>
  </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-21T11:46:31.379029+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-2023-53623</id>
    <title>UBUNTU-CVE-2023-53623</title>
    <updated>2026-11-21T11:46:31.379108+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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, Ubuntu:16.04:LTS: linux-hwe-edge and 162 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: mm/swap: fix swap_info_struct race between swapoff and get_swap_pages() The si-&gt;lock must be held when deleting the si from the available list. Otherwise, another thread can re-add the si to the available list, which can lead to memory corruption.  The only place we have found where this happens is in the swapoff path.  This case can be described as below: core 0                       core 1 swapoff del_from_avail_list(si)      waiting try lock si-&gt;lock            acquire swap_avail_lock                              and re-add si into                              swap_avail_head acquire si-&gt;lock but missing si already being added again, and continuing to clear SWP_WRITEOK, etc. It can be easily found that a massive warning messages can be triggered inside get_swap_pages() by some special cases, for example, we call madvise(MADV_PAGEOUT) on blocks of touched memory concurrently, meanwhile, run much swapon-swapoff operations (e.g.  stress-ng-swap). However, in the worst case, panic can be caused by the above scene.  In swapoff(), the memory used by si could be kept in swap_info[] after turning off a swap.  This means memory corruption will not be caused immediately until allocated and reset for a new swap in the swapon path. A panic message caused: (with CONFIG_PLIST_DEBUG enabled) ------------[ cut here ]------------ top: 00000000e58a3003, n: 0000000013e75cda, p: 000000008cd4451a prev: 0000000035b1e58a, n: 00…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2023-53623"/>
  </entry>
</feed>
