<?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-10-01T02:07:44.623198+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-2026-AVI-0108</id>
    <title>CERTFR-2026-AVI-0108 — 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-10-01T02:07:48.291791+00:00</updated>
    <content>CERTFR-2026-AVI-0108</content>
    <link href="https://vulnerability.circl.lu/vuln/CERTFR-2026-AVI-0108"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/bell-cve-2023-54072</id>
    <title>BELL-CVE-2023-54072</title>
    <updated>2026-10-01T02:07:48.291947+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:stream: linux-lts</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/bell-cve-2023-54072"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/fkie_cve-2023-54072</id>
    <title>fkie_cve-2023-54072</title>
    <updated>2026-10-01T02:07:48.292042+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>ALSA: pcm: Fix potential data race at PCM memory allocation helpers</p>
<p>The PCM memory allocation helpers have a sanity check against too many
buffer allocations.  However, the check is performed without a proper
lock and the allocation isn't serialized; this allows user to allocate
more memories than predefined max size.</p>
<p>Practically seen, this isn't really a big problem, as it's more or
less some "soft limit" as a sanity check, and it's not possible to
allocate unlimitedly.  But it's still better to address this for more
consistent behavior.</p>
<p>The patch covers the size check in do_alloc_pages() with the
card-&gt;memory_mutex, and increases the allocated size there for
preventing the further overflow.  When the actual allocation fails,
the size is decreased accordingly.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/fkie_cve-2023-54072"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-xx23-73hr-9p64</id>
    <title>GHSA-xx23-73hr-9p64</title>
    <updated>2026-10-01T02:07:48.292110+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>ALSA: pcm: Fix potential data race at PCM memory allocation helpers</p>
<p>The PCM memory allocation helpers have a sanity check against too many
buffer allocations.  However, the check is performed without a proper
lock and the allocation isn't serialized; this allows user to allocate
more memories than predefined max size.</p>
<p>Practically seen, this isn't really a big problem, as it's more or
less some "soft limit" as a sanity check, and it's not possible to
allocate unlimitedly.  But it's still better to address this for more
consistent behavior.</p>
<p>The patch covers the size check in do_alloc_pages() with the
card-&gt;memory_mutex, and increases the allocated size there for
preventing the further overflow.  When the actual allocation fails,
the size is decreased accordingly.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-xx23-73hr-9p64"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/rhsa-2024:2394</id>
    <title>RHSA-2024:2394 — Red Hat Security Advisory: kernel security, bug fix, and enhancement update</title>
    <updated>2026-10-01T02:07:48.292151+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>kernel: Bluetooth BR/EDR PIN Pairing procedure is vulnerable to an impersonation attack kernel: ovl: fix warning in ovl_create_real() kernel: memcg does not limit the number of POSIX file locks allowing memory exhaustion kernel: vmwgfx: NULL pointer dereference in vmw_cmd_dx_define_query kernel: integer overflow in l2cap_config_req() in net/bluetooth/l2cap_core.c kernel: i2c: mlxbf: prevent stack overflow in mlxbf_i2c_smbus_start_transaction() kernel: Bluetooth: L2CAP: Fix u8 overflow kernel: hwmon: (coretemp) fix pci device refcount leak in nv1a_ram_new() kernel: tracing: Fix sleeping function called from invalid context on RT kernel kernel: net: mdio: unexport __init-annotated mdio_bus_init() kernel: arm64: ftrace: consistently handle PLTs. kernel: mm/uffd: fix pte marker when fork() without fork event kernel: Bluetooth: Fix a buffer overflow in mgmt_mesh_add() kernel: tty: n_gsm: add sanity check for gsm-&gt;receive in gsm_receive_buf() kernel: ftrace: Fix NULL pointer dereference in is_ftrace_trampoline when ftrace is dead kernel: tee: add overflow check in register_shm_helper() kernel: tty: n_gsm: fix deadlock and link starvation in outgoing data path kernel: PM: hibernate: defer device probing when resuming from hibernation kernel: ext4: don't allow journal inode to have encrypt flag kernel: ext4: fix delayed allocation bug in ext4_clu_mapped for bigalloc + inline kernel: erofs: fix order &gt;= MAX_ORDER warning due to crafted negative i_size kernel: perf/x86/intel/uncore: F…</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/rhsa-2024:2394"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/rxsa-2024:3138</id>
    <title>RXSA-2024:3138 — Moderate: kernel security, bug fix, and enhancement update</title>
    <updated>2026-10-01T02:07:48.293563+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Rocky Linux:8: kernel</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://vulnerability.circl.lu/vuln/rxsa-2024:3138"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/suse-su-2026:0263-1</id>
    <title>SUSE-SU-2026:0263-1 — Security update for the Linux Kernel</title>
    <updated>2026-10-01T02:07:48.293616+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-2026:0263-1"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ubuntu-cve-2023-54072</id>
    <title>UBUNTU-CVE-2023-54072</title>
    <updated>2026-10-01T02:07:48.294125+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 164 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: ALSA: pcm: Fix potential data race at PCM memory allocation helpers The PCM memory allocation helpers have a sanity check against too many buffer allocations.  However, the check is performed without a proper lock and the allocation isn't serialized; this allows user to allocate more memories than predefined max size. Practically seen, this isn't really a big problem, as it's more or less some "soft limit" as a sanity check, and it's not possible to allocate unlimitedly.  But it's still better to address this for more consistent behavior. The patch covers the size check in do_alloc_pages() with the card-&gt;memory_mutex, and increases the allocated size there for preventing the further overflow.  When the actual allocation fails, the size is decreased accordingly.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ubuntu-cve-2023-54072"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/wid-sec-w-2025-2929</id>
    <title>WID-SEC-W-2025-2929 — Linux Kernel: Mehrere Schwachstellen</title>
    <updated>2026-10-01T02:07:48.294542+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/wid-sec-w-2025-2929"/>
  </entry>
</feed>
