<?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-19T17:49:29.046598+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-53395</id>
    <title>BELL-CVE-2023-53395</title>
    <updated>2026-11-19T17:49:29.059342+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://127.0.0.1:10001/vuln/bell-cve-2023-53395"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/certfr-2025-avi-0895</id>
    <title>certfr-2025-avi-0895 — 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-11-19T17:49:29.059429+00:00</updated>
    <content>certfr-2025-avi-0895</content>
    <link href="https://127.0.0.1:10001/vuln/certfr-2025-avi-0895"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/oesa-2025-2407</id>
    <title>OESA-2025-2407 — kernel security update</title>
    <updated>2026-11-19T17:49:29.059454+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openEuler:22.03-LTS-SP3: 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>net: dsa: Avoid cross-chip syncing of VLAN filtering</p>
<p>Changes to VLAN filtering are not applicable to cross-chip
notifications.</p>
<p>On a system like this:</p>
<p>.-----.   .-----.   .-----.
| sw1 +---+ sw2 +---+ sw3 |
&amp;apos;-1-2-&amp;apos;   &amp;apos;-1-2-&amp;apos;   &amp;apos;-1-2-&amp;apos;</p>
<p>Before this change, upon sw1p1 leaving a bridge, a call to
dsa_port_vlan_filtering would also be made to sw2p1 and sw3p1.</p>
<p>In this scenario:</p>
<p>.---------.   .-----.   .-----.
|   sw1   +---+ sw2 +---+ sw3 |
&amp;apos;-1-2-3-4-&amp;apos;   &amp;apos;-1-2-&amp;apos;   &amp;apos;-1-2-&amp;apos;</p>
<p>When sw1p4 would leave a bridge, dsa_port_vlan_filtering would be
called for sw2 and sw3 with a non-existing port - leading to array
out-of-bounds accesses and crashes on mv88e6xxx.(CVE-2022-49234)</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>scsi: target: iscsi: Fix a race condition between login_work and the login thread</p>
<p>In case a malicious initiator sends some random data immediately after a
login PDU; the iscsi_target_sk_data_ready() callback will schedule the
login_work and, at the same time, the negotiation may end without clearing
the LOGIN_FLAGS_INITIAL_PDU flag (because no additional PDU exchanges are
required to complete the login).</p>
<p>The login has been completed but the login_work function will find the
LOGIN_FLAGS_INITIAL_PDU flag set and will never stop from rescheduling…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/oesa-2025-2407"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/ubuntu-cve-2023-53395</id>
    <title>UBUNTU-CVE-2023-53395</title>
    <updated>2026-11-19T17:49:29.059655+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 169 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: ACPICA: Add AML_NO_OPERAND_RESOLVE flag to Timer ACPICA commit 90310989a0790032f5a0140741ff09b545af4bc5 According to the ACPI specification 19.6.134, no argument is required to be passed for ASL Timer instruction. For taking care of no argument, AML_NO_OPERAND_RESOLVE flag is added to ASL Timer instruction opcode. When ASL timer instruction interpreted by ACPI interpreter, getting error. After adding AML_NO_OPERAND_RESOLVE flag to ASL Timer instruction opcode, issue is not observed. ============================================================= UBSAN: array-index-out-of-bounds in acpica/dswexec.c:401:12 index -1 is out of range for type 'union acpi_operand_object *[9]' CPU: 37 PID: 1678 Comm: cat Not tainted 6.0.0-dev-th500-6.0.y-1+bcf8c46459e407-generic-64k HW name: NVIDIA BIOS v1.1.1-d7acbfc-dirty 12/19/2022 Call trace:  dump_backtrace+0xe0/0x130  show_stack+0x20/0x60  dump_stack_lvl+0x68/0x84  dump_stack+0x18/0x34  ubsan_epilogue+0x10/0x50  __ubsan_handle_out_of_bounds+0x80/0x90  acpi_ds_exec_end_op+0x1bc/0x6d8  acpi_ps_parse_loop+0x57c/0x618  acpi_ps_parse_aml+0x1e0/0x4b4  acpi_ps_execute_method+0x24c/0x2b8  acpi_ns_evaluate+0x3a8/0x4bc  acpi_evaluate_object+0x15c/0x37c  acpi_evaluate_integer+0x54/0x15c  show_power+0x8c/0x12c [acpi_power_meter]</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2023-53395"/>
  </entry>
</feed>
