<?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:59:32.244345+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-2025-37878</id>
    <title>BELL-CVE-2025-37878</title>
    <updated>2026-11-19T17:59:32.257241+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:25: linux-lts</p>
      </div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/bell-cve-2025-37878"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/certfr-2025-avi-0559</id>
    <title>certfr-2025-avi-0559 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
    <updated>2026-11-19T17:59:32.257309+00:00</updated>
    <content>certfr-2025-avi-0559</content>
    <link href="https://127.0.0.1:10001/vuln/certfr-2025-avi-0559"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/oesa-2025-1539</id>
    <title>OESA-2025-1539 — kernel security update</title>
    <updated>2026-11-19T17:59:32.257331+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>bpf: track changes_pkt_data property for global functions</p>
<p>When processing calls to certain helpers, verifier invalidates all
packet pointers in a current state. For example, consider the
following program:</p>
<p>__attribute__((__noinline__))
    long skb_pull_data(struct __sk_buff *sk, __u32 len)
    {
        return bpf_skb_pull_data(sk, len);
    }</p>
<p>SEC(&amp;quot;tc&amp;quot;)
    int test_invalidate_checks(struct __sk_buff *sk)
    {
        int *p = (void *)(long)sk-&amp;gt;data;
        if ((void *)(p + 1) &amp;gt; (void *)(long)sk-&amp;gt;data_end) return TCX_DROP;
        skb_pull_data(sk, 0);
        *p = 42;
        return TCX_PASS;
    }</p>
<p>After a call to bpf_skb_pull_data() the pointer &amp;apos;p&amp;apos; can&amp;apos;t be used
safely. See function filter.c:bpf_helper_changes_pkt_data() for a list
of such helpers.</p>
<p>At the moment verifier invalidates packet pointers when processing
helper function calls, and does not traverse global sub-programs when
processing calls to global sub-programs. This means that calls to
helpers done from global sub-programs do not invalidate pointers in
the caller state. E.g. the program above is unsafe, but is not
rejected by verifier.</p>
<p>This commit fixes the omission by computing field
bpf_subprog_info-&amp;gt;changes_pkt_data for each sub-program before main
verification pass.
changes_pkt_data should be set if:
- subprogram…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/oesa-2025-1539"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-37878</id>
    <title>UBUNTU-CVE-2025-37878</title>
    <updated>2026-11-19T17:59:32.257425+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 82 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: perf/core: Fix WARN_ON(!ctx) in __free_event() for partial init Move the get_ctx(child_ctx) call and the child_event-&gt;ctx assignment to occur immediately after the child event is allocated. Ensure that child_event-&gt;ctx is non-NULL before any subsequent error path within inherit_event calls free_event(), satisfying the assumptions of the cleanup code. Details: There's no clear Fixes tag, because this bug is a side-effect of multiple interacting commits over time (up to 15 years old), not a single regression. The code initially incremented refcount then assigned context immediately after the child_event was created. Later, an early validity check for child_event was added before the refcount/assignment. Even later, a WARN_ON_ONCE() cleanup check was added, assuming event-&gt;ctx is valid if the pmu_ctx is valid. The problem is that the WARN_ON_ONCE() could trigger after the initial check passed but before child_event-&gt;ctx was assigned, violating its precondition. The solution is to assign child_event-&gt;ctx right after its initial validation. This ensures the context exists for any subsequent checks or cleanup routines, resolving the WARN_ON_ONCE(). To resolve it, defer the refcount update and child_event-&gt;ctx assignment directly after child_event-&gt;pmu_ctx is set but before checking if the parent event is orphaned. The cleanup routine depends on event-&gt;pmu_ctx being non-NULL before it verifies event-&gt;ctx is non-NUL…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2025-37878"/>
  </entry>
</feed>
