<?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:19.520586+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-56770</id>
    <title>BELL-CVE-2024-56770</title>
    <updated>2026-11-21T03:59:19.532051+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-56770"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/certfr-2025-avi-0184</id>
    <title>certfr-2025-avi-0184 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Elles permettent à un attaquant de p…</title>
    <updated>2026-11-21T03:59:19.532091+00:00</updated>
    <content>certfr-2025-avi-0184</content>
    <link href="https://127.0.0.1:10001/vuln/certfr-2025-avi-0184"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/oesa-2025-1248</id>
    <title>OESA-2025-1248 — kernel security update</title>
    <updated>2026-11-21T03:59:19.532107+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):</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>sched: fix warning in sched_setaffinity</p>
<p>Commit 8f9ea86fdf99b added some logic to sched_setaffinity that included
a WARN when a per-task affinity assignment races with a cpuset update.</p>
<p>Specifically, we can have a race where a cpuset update results in the
task affinity no longer being a subset of the cpuset. That&amp;apos;s fine; we
have a fallback to instead use the cpuset mask. However, we have a WARN
set up that will trigger if the cpuset mask has no overlap at all with
the requested task affinity. This shouldn&amp;apos;t be a warning condition; its
trivial to create this condition.</p>
<p>Reproduced the warning by the following setup:</p>
<p>- $PID inside a cpuset cgroup
- another thread repeatedly switching the cpuset cpus from 1-2 to just 1
- another thread repeatedly setting the $PID affinity (via taskset) to 2(CVE-2024-41932)</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>riscv: Fix IPIs usage in kfence_protect_page()</p>
<p>flush_tlb_kernel_range() may use IPIs to flush the TLBs of all the
cores, which triggers the following warning when the irqs are disabled:</p>
<p>[    3.455330] WARNING: CPU: 1 PID: 0 at kernel/smp.c:815 smp_call_function_many_cond+0x452/0x520
[    3.456647] Modules linked in:
[    3.457218] CPU: 1 UID: 0 PID: 0 Comm: swapper/1 Not tainted 6.12.0-rc7-00010-g91d3de7240b8 #1
[    3.457416] Hardware name: QEMU QEMU Vi…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/oesa-2025-1248"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-56770</id>
    <title>UBUNTU-CVE-2024-56770</title>
    <updated>2026-11-21T03:59:19.532261+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 196 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: net/sched: netem: account for backlog updates from child qdisc In general, 'qlen' of any classful qdisc should keep track of the number of packets that the qdisc itself and all of its children holds. In case of netem, 'qlen' only accounts for the packets in its internal tfifo. When netem is used with a child qdisc, the child qdisc can use 'qdisc_tree_reduce_backlog' to inform its parent, netem, about created or dropped SKBs. This function updates 'qlen' and the backlog statistics of netem, but netem does not account for changes made by a child qdisc. 'qlen' then indicates the wrong number of packets in the tfifo. If a child qdisc creates new SKBs during enqueue and informs its parent about this, netem's 'qlen' value is increased. When netem dequeues the newly created SKBs from the child, the 'qlen' in netem is not updated. If 'qlen' reaches the configured sch-&gt;limit, the enqueue function stops working, even though the tfifo is not full. Reproduce the bug: Ensure that the sender machine has GSO enabled. Configure netem as root qdisc and tbf as its child on the outgoing interface of the machine as follows: $ tc qdisc add dev &lt;oif&gt; root handle 1: netem delay 100ms limit 100 $ tc qdisc add dev &lt;oif&gt; parent 1:0 tbf rate 50Mbit burst 1542 latency 50ms Send bulk TCP traffic out via this interface, e.g., by running an iPerf3 client on the machine. Check the qdisc statistics: $ tc -s qdisc show dev &lt;oif&gt; Statistics a…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2024-56770"/>
  </entry>
</feed>
