<?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-21T08:25:16.963387+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/cve-2026-27456</id>
    <title>CVE-2026-27456 — util-linux: TOCTOU Race Condition in util-linux mount(8) - Loop Device Setup</title>
    <updated>2026-11-21T08:25:16.970519+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> util-linux</p>
<p>util-linux is a random collection of Linux utilities. Prior to version 2.41.4, a TOCTOU (Time-of-Check-Time-of-Use) vulnerability has been identified in the SUID binary /usr/bin/mount from util-linux. The mount binary, when setting up loop devices, validates the source file path with user privileges via fork() + setuid() + realpath(), but subsequently re-canonicalizes and opens it with root privileges (euid=0) without verifying that the path has not been replaced between both operations. Neither O_NOFOLLOW, nor inode comparison, nor post-open fstat() are employed. This allows a local unprivileged user to replace the source file with a symlink pointing to any root-owned file or device during the race window, causing the SUID binary to open and mount it as root. Exploitation requires an /etc/fstab entry with user,loop options whose path points to a directory where the attacker has write permission, and that /usr/bin/mount has the SUID bit set (the default configuration on virtually all Linux distributions). The impact is unauthorized read access to root-protected files and block devices, including backup images, disk volumes, and any file containing a valid filesystem. This issue has been patched in version 2.41.4.</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/cve-2026-27456"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/usn-8702-1</id>
    <title>USN-8702-1 — util-linux vulnerabilities</title>
    <updated>2026-11-21T08:25:16.970577+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:22.04:LTS: util-linux, Ubuntu:24.04:LTS: util-linux, Ubuntu:26.04:LTS: util-linux</p>
<p>It was discovered that libblkid in util-linux had a heap use-after-free
vulnerability during nested partition probing. An attacker who could
present a crafted block device image could possibly use this issue to
obtain sensitive information or cause a denial of service. (CVE-2026-13595)</p>
<p>It was discovered that the mount utility in util-linux had a time-of-check-
time-of-use vulnerability when setting up loop devices. A local attacker
could possibly use this issue to obtain unauthorized read access to root-
protected files and block devices. (CVE-2026-27456)</p>
<p>It was discovered that the login utility in util-linux improperly
canonicalized hostnames when invoked with the -h option. A remote attacker
could possibly use this issue to bypass host-based access control rules.
This issue only affected Ubuntu 26.04 LTS. (CVE-2026-3184)</p>
<p>It was discovered that libmount in util-linux had a time-of-check-time-of-
use vulnerability in its ownership hook. A local attacker could possibly
use this issue to gain elevated privileges. This issue only affected Ubuntu
24.04 LTS and Ubuntu 26.04 LTS. (CVE-2026-53612)</p>
<p>It was discovered that libmount in util-linux had a time-of-check-time-of-
use vulnerability that allowed target path redirection during mount
operations. A local attacker could possibly use this issue to gain elevated
privileges. (CVE-2026-53613)</p>
<p>It was discovered that libmount in util-linux improperly handled the
LIBMOUNT_FORCE_MOUNT2 environment variable in the SUID mount utility.…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/usn-8702-1"/>
  </entry>
</feed>
