<?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://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-17T10:33:18.593975+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" 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://cve.radiocsirt.org/vuln/bell-cve-2026-98995</id>
    <title>BELL-CVE-2026-98995</title>
    <updated>2026-11-17T10:33:18.603016+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://cve.radiocsirt.org/vuln/bell-cve-2026-98995"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1537</id>
    <title>certfr-2026-avi-1537 — 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-17T10:33:18.603060+00:00</updated>
    <content>certfr-2026-avi-1537</content>
    <link href="https://cve.radiocsirt.org/vuln/certfr-2026-avi-1537"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-392027</id>
    <title>EUVD-2026-392027</title>
    <updated>2026-11-17T10:33:18.603080+00:00</updated>
    <content>EUVD-2026-392027</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-392027"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-98995</id>
    <title>fkie_cve-2026-98995</title>
    <updated>2026-11-17T10:33:18.603092+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>namespace: reset the old parent's -&gt;overmount in mnt_change_mountpoint()</p>
<p>__umount_mnt() resets -&gt;overmount of the parent when it unmounts the
mount that overmounts it. mnt_change_mountpoint() doesn't. It moves the
mount to its new parent and leaves the old one pointing at it.</p>
<p>For a mount that is moved beneath in attach_recursive_mnt() that doesn't
matter. The new mount has already reset -&gt;overmount of the old parent by
the time the old top mount is moved onto it.</p>
<p>It matters for reparent() though. propagate_umount() moves a surviving
overmount onto the first ancestor that isn't going to be unmounted. The
mount it was taken from is unmounted immediately afterwards. If a file
descriptor keeps that unmounted mount alive -&gt;overmount points at the
moved mount. That's a dangling pointer and UAF as the moved mount is
unmounted and freed.</p>
<p>do_lock_mount() follows -&gt;overmount from the target path under
mount_lock. With a file descriptor on such a mount as the target of a
mount beneath topmost_overmount() walks into the freed mount and
do_lock_mount() takes references on whatever it finds there.</p>
<p>So reset -&gt;overmount of the old parent in mnt_change_mountpoint() the
same way __umount_mnt() does. A mount's -&gt;overmount is then always a
mount that is attached to it.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-98995"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-h4q9-qcg7-rj48</id>
    <title>GHSA-h4q9-qcg7-rj48</title>
    <updated>2026-11-17T10:33:18.603130+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>namespace: reset the old parent's -&gt;overmount in mnt_change_mountpoint()</p>
<p>__umount_mnt() resets -&gt;overmount of the parent when it unmounts the
mount that overmounts it. mnt_change_mountpoint() doesn't. It moves the
mount to its new parent and leaves the old one pointing at it.</p>
<p>For a mount that is moved beneath in attach_recursive_mnt() that doesn't
matter. The new mount has already reset -&gt;overmount of the old parent by
the time the old top mount is moved onto it.</p>
<p>It matters for reparent() though. propagate_umount() moves a surviving
overmount onto the first ancestor that isn't going to be unmounted. The
mount it was taken from is unmounted immediately afterwards. If a file
descriptor keeps that unmounted mount alive -&gt;overmount points at the
moved mount. That's a dangling pointer and UAF as the moved mount is
unmounted and freed.</p>
<p>do_lock_mount() follows -&gt;overmount from the target path under
mount_lock. With a file descriptor on such a mount as the target of a
mount beneath topmost_overmount() walks into the freed mount and
do_lock_mount() takes references on whatever it finds there.</p>
<p>So reset -&gt;overmount of the old parent in mnt_change_mountpoint() the
same way __umount_mnt() does. A mount's -&gt;overmount is then always a
mount that is attached to it.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-h4q9-qcg7-rj48"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/msrc_cve-2026-98995</id>
    <title>msrc_CVE-2026-98995 — namespace: reset the old parent's -&gt;overmount in mnt_change_mountpoint()</title>
    <updated>2026-11-17T10:33:18.603158+00:00</updated>
    <content>msrc_CVE-2026-98995</content>
    <link href="https://cve.radiocsirt.org/vuln/msrc_cve-2026-98995"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-98995</id>
    <title>UBUNTU-CVE-2026-98995</title>
    <updated>2026-11-17T10:33:18.603173+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 129 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: namespace: reset the old parent's -&gt;overmount in mnt_change_mountpoint() __umount_mnt() resets -&gt;overmount of the parent when it unmounts the mount that overmounts it. mnt_change_mountpoint() doesn't. It moves the mount to its new parent and leaves the old one pointing at it. For a mount that is moved beneath in attach_recursive_mnt() that doesn't matter. The new mount has already reset -&gt;overmount of the old parent by the time the old top mount is moved onto it. It matters for reparent() though. propagate_umount() moves a surviving overmount onto the first ancestor that isn't going to be unmounted. The mount it was taken from is unmounted immediately afterwards. If a file descriptor keeps that unmounted mount alive -&gt;overmount points at the moved mount. That's a dangling pointer and UAF as the moved mount is unmounted and freed. do_lock_mount() follows -&gt;overmount from the target path under mount_lock. With a file descriptor on such a mount as the target of a mount beneath topmost_overmount() walks into the freed mount and do_lock_mount() takes references on whatever it finds there. So reset -&gt;overmount of the old parent in mnt_change_mountpoint() the same way __umount_mnt() does. A mount's -&gt;overmount is then always a mount that is attached to it.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-98995"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4152</id>
    <title>WID-SEC-W-2026-4152 — Linux Kernel: Mehrere Schwachstellen</title>
    <updated>2026-11-17T10:33:18.603317+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4152"/>
  </entry>
</feed>
