https://db.gcve.eu/rss/recent/all/10 Most recent entries from all 2026-11-11T16:47:22.505301+00:00 Vulnerability-Lookup info@gcve.eu python-feedgen Contains only the most 10 recent entries. https://db.gcve.eu/vuln/cve-2026-98977 CVE-2026-98977 — namespace: handle mount locking for automounts correctly 2026-11-11T16:47:22.613920+00:00

Affected: Linux

In the Linux kernel, the following vulnerability has been resolved:

namespace: handle mount locking for automounts correctly

If mounts are propagated across user namespaces, attach_recursive_mnt() locks every copy of the source mount to protect overmounts from vanishing and revealing the underlying files or directories.

The user namespace is taken from the caller's mount namespaces since this is where the mounts end up. Except, that's not always true. Automounts may legitimately get popped in by tasks located in a different mount and user namespace during path lookup.

Then check doesn't make sense at that point. The copy in the namespace of the parent - which may be the host's - is now locked and the host cannot change the flags of its own mounts anymore.

Here's the reproducer:

- host has debugfs mounted nosuid,nodev,noexec and shared - tracefs automount below it is not yet active - hand a child process a directory descriptor on that mount - child process enters auser and mount namespace - child process' namespace now holds a locked copy of the host's debugfs mount that receives propagation from it - child process stats "tracing/." through the descriptor - lookup runs on the host's mount so the automount lands below the host's mount - propagation puts a copy below the child's copy - both try to clear the flags on the mount they got, with a bind remount:

host, on its own automount: MS_REMOUNT|MS_BIND = EPERM child, on the copy in its namespace: M…

 https://db.gcve.eu/vuln/usn-9018-1 USN-9018-1 — linux, linux-aws, linux-gcp, linux-ibm, linux-oem-7.0, linux-oracle vulnerabilities 2026-11-11T16:47:22.614184+00:00

Affected: Ubuntu:26.04:LTS: linux, Ubuntu:26.04:LTS: linux-aws, Ubuntu:26.04:LTS: linux-gcp, Ubuntu:26.04:LTS: linux-ibm, Ubuntu:26.04:LTS: linux-oem-7.0, Ubuntu:26.04:LTS: linux-oracle

Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems: - Network file systems library; - Stream parser; - ARM64 architecture; - PowerPC architecture; - RISC-V architecture; - S390 architecture; - User-Mode Linux (UML); - x86 architecture; - Block layer subsystem; - Android drivers; - Bluetooth drivers; - TPM device driver; - DPLL subsystem; - EDAC drivers; - GPIO subsystem; - GPU drivers; - HID subsystem; - IIO subsystem; - IIO ADC drivers; - InfiniBand drivers; - Input Device (Miscellaneous) drivers; - Multiple devices driver; - MemoryStick subsystem; - MMC subsystem; - MTD block device drivers; - Network drivers; - Ethernet bonding driver; - Mellanox network drivers; - STMicroelectronics network drivers; - Ethernet team driver; - MediaTek network drivers; - NVME drivers; - Device tree and open firmware driver; - Power sequencing drivers; - Voltage and Current Regulator drivers; - Real Time Clock drivers; - SCSI subsystem; - Greybus lights staging drivers; - Trusted Execution Environment drivers; - Thunderbolt and USB4 drivers; - TTY drivers; - Cadence USB3 driver; - USB Device Class drivers; - USB core drivers; - DesignWare USB2 driver; - DesignWare USB3 driver; - USB Gadget drivers; - USB Serial drivers; - USB Mass Storage drivers; - USB Type-C suppor…