<?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-21T10:20:42.399336+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-38632</id>
    <title>BELL-CVE-2025-38632</title>
    <updated>2026-11-21T10:20:42.417918+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:stream: linux-lts</p>
      </div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/bell-cve-2025-38632"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/certfr-2025-avi-0787</id>
    <title>certfr-2025-avi-0787 — 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-21T10:20:42.417974+00:00</updated>
    <content>certfr-2025-avi-0787</content>
    <link href="https://127.0.0.1:10001/vuln/certfr-2025-avi-0787"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/oesa-2025-2118</id>
    <title>OESA-2025-2118 — kernel security update</title>
    <updated>2026-11-21T10:20:42.417998+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>netfilter: nf_tables: avoid skb access on nf_stolen</p>
<p>When verdict is NF_STOLEN, the skb might have been freed.</p>
<p>When tracing is enabled, this can result in a use-after-free:
1. access to skb-&amp;gt;nf_trace
2. access to skb-&amp;gt;mark
3. computation of trace id
4. dump of packet payload</p>
<p>To avoid 1, keep a cached copy of skb-&amp;gt;nf_trace in the
trace state struct.
Refresh this copy whenever verdict is != STOLEN.</p>
<p>Avoid 2 by skipping skb-&amp;gt;mark access if verdict is STOLEN.</p>
<p>3 is avoided by precomputing the trace id.</p>
<p>Only dump the packet when verdict is not &amp;quot;STOLEN&amp;quot;.(CVE-2022-49622)</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>nfsd: release svc_expkey/svc_export with rcu_work</p>
<p>The last reference for `cache_head` can be reduced to zero in `c_show`
and `e_show`(using `rcu_read_lock` and `rcu_read_unlock`). Consequently,
`svc_export_put` and `expkey_put` will be invoked, leading to two
issues:</p>
<p>1. The `svc_export_put` will directly free ex_uuid. However,
   `e_show`/`c_show` will access `ex_uuid` after `cache_put`, which can
   trigger a use-after-free issue, shown below.</p>
<p>==================================================================
   BUG: KASAN: slab-use-after-free in svc_export_show+0x362/0x430 [nfsd]
   Read of size 1 at addr ff11000010fdc120 by task cat/870</p>
<p>CPU: 1 UID: 0 PID: 870 Comm: cat…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/oesa-2025-2118"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-38632</id>
    <title>UBUNTU-CVE-2025-38632</title>
    <updated>2026-11-21T10:20:42.418144+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 123 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: pinmux: fix race causing mux_owner NULL with active mux_usecount commit 5a3e85c3c397 ("pinmux: Use sequential access to access desc-&gt;pinmux data") tried to address the issue when two client of the same gpio calls pinctrl_select_state() for the same functionality, was resulting in NULL pointer issue while accessing desc-&gt;mux_owner. However, issue was not completely fixed due to the way it was handled and it can still result in the same NULL pointer. The issue occurs due to the following interleaving:      cpu0 (process A)                   cpu1 (process B)       pin_request() {                   pin_free() {                                          mutex_lock()                                          desc-&gt;mux_usecount--; //becomes 0                                          ..                                          mutex_unlock()   mutex_lock(desc-&gt;mux)   desc-&gt;mux_usecount++; // becomes 1   desc-&gt;mux_owner = owner;   mutex_unlock(desc-&gt;mux)                                          mutex_lock(desc-&gt;mux)                                          desc-&gt;mux_owner = NULL;                                          mutex_unlock(desc-&gt;mux) This sequence leads to a state where the pin appears to be in use (`mux_usecount == 1`) but has no owner (`mux_owner == NULL`), which can cause NULL pointer on next pin_request on the same pin. Ensure that updates to mux_usecount and mux_owner are performed atomically under the s…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2025-38632"/>
  </entry>
</feed>
