<?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-21T03:59:22.614967+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-2024-50194</id>
    <title>BELL-CVE-2024-50194</title>
    <updated>2026-11-21T03:59:22.621120+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p>
      </div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/bell-cve-2024-50194"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/certfr-2024-avi-1102</id>
    <title>certfr-2024-avi-1102 — 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-21T03:59:22.621149+00:00</updated>
    <content>certfr-2024-avi-1102</content>
    <link href="https://127.0.0.1:10001/vuln/certfr-2024-avi-1102"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/oesa-2024-2537</id>
    <title>OESA-2024-2537 — kernel security update</title>
    <updated>2026-11-21T03:59:22.621160+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openEuler:24.03-LTS: kernel</p>
<p>The Linux Kernel, the operating system core itself.

Security Fix(es):

In the Linux kernel, the following vulnerability has been resolved:  xhci: Handle TD clearing for multiple streams case  When multiple streams are in use, multiple TDs might be in flight when an endpoint is stopped. We need to issue a Set TR Dequeue Pointer for each, to ensure everything is reset properly and the caches cleared. Change the logic so that any N&amp;gt;1 TDs found active for different streams are deferred until after the first one is processed, calling xhci_invalidate_cancelled_tds() again from xhci_handle_cmd_set_deq() to queue another command until we are done with all of them. Also change the error/&amp;quot;should never happen&amp;quot; paths to ensure we at least clear any affected TDs, even if we can&amp;apos;t issue a command to clear the hardware cache, and complain loudly with an xhci_warn() if this ever happens.  This problem case dates back to commit e9df17eb1408 (&amp;quot;USB: xhci: Correct assumptions about number of rings per endpoint.&amp;quot;) early on in the XHCI driver&amp;apos;s life, when stream support was first added. It was then identified but not fixed nor made into a warning in commit 674f8438c121 (&amp;quot;xhci: split handling halted endpoints into two steps&amp;quot;), which added a FIXME comment for the problem case (without materially changing the behavior as far as I can tell, though the new logic made the problem more obvious).  Then later, in commit 94f339147fc3 (&amp;quot;xhci: Fix failure…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/oesa-2024-2537"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-50194</id>
    <title>UBUNTU-CVE-2024-50194</title>
    <updated>2026-11-21T03:59:22.621326+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 187 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: arm64: probes: Fix uprobes for big-endian kernels The arm64 uprobes code is broken for big-endian kernels as it doesn't convert the in-memory instruction encoding (which is always little-endian) into the kernel's native endianness before analyzing and simulating instructions. This may result in a few distinct problems: * The kernel may may erroneously reject probing an instruction which can   safely be probed. * The kernel may erroneously erroneously permit stepping an   instruction out-of-line when that instruction cannot be stepped   out-of-line safely. * The kernel may erroneously simulate instruction incorrectly dur to   interpretting the byte-swapped encoding. The endianness mismatch isn't caught by the compiler or sparse because: * The arch_uprobe::{insn,ixol} fields are encoded as arrays of u8, so   the compiler and sparse have no idea these contain a little-endian   32-bit value. The core uprobes code populates these with a memcpy()   which similarly does not handle endianness. * While the uprobe_opcode_t type is an alias for __le32, both   arch_uprobe_analyze_insn() and arch_uprobe_skip_sstep() cast from u8[]   to the similarly-named probe_opcode_t, which is an alias for u32.   Hence there is no endianness conversion warning. Fix this by changing the arch_uprobe::{insn,ixol} fields to __le32 and adding the appropriate __le32_to_cpu() conversions prior to consuming the instruction encoding. The core…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2024-50194"/>
  </entry>
</feed>
