https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 03:56:03 +0000 https://vulnerability.circl.lu/vuln/bell-cve-2026-72186 <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Withdrawn by the publisher.</strong></p> https://vulnerability.circl.lu/vuln/bell-cve-2026-72186 https://vulnerability.circl.lu/vuln/fkie_cve-2026-72186 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ntfs: make system files immutable to prevent corruption</p> <p>When a system file such as $Bitmap is exposed via show_sys_files and written from userspace, the volume is corrupted and, because the cluster allocator scans $Bitmap through the same inode&#39;s page cache, a write to $Bitmap also deadlocks writeback against the folio it already holds locked.</p> <p>These files are maintained by the driver itself and have no valid reason to be written through the file interface. Mark base metadata files (mft_no &lt; FILE_first_user) as immutable during inode read so the VFS rejects write, mmap, truncate and unlink with -EPERM. Directories are skipped so the root and $Extend remain usable. Internal metadata updates do not go through the VFS write path and are unaffected.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ntfs: make system files immutable to prevent corruption</p> <p>When a system file such as $Bitmap is exposed via show_sys_files and written from userspace, the volume is corrupted and, because the cluster allocator scans $Bitmap through the same inode&#39;s page cache, a write to $Bitmap also deadlocks writeback against the folio it already holds locked.</p> <p>These files are maintained by the driver itself and have no valid reason to be written through the file interface. Mark base metadata files (mft_no &lt; FILE_first_user) as immutable during inode read so the VFS rejects write, mmap, truncate and unlink with -EPERM. Directories are skipped so the root and $Extend remain usable. Internal metadata updates do not go through the VFS write path and are unaffected.</p> https://vulnerability.circl.lu/vuln/fkie_cve-2026-72186 https://vulnerability.circl.lu/vuln/ghsa-cpf7-qp55-xqgv <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ntfs: make system files immutable to prevent corruption</p> <p>When a system file such as $Bitmap is exposed via show_sys_files and written from userspace, the volume is corrupted and, because the cluster allocator scans $Bitmap through the same inode&#39;s page cache, a write to $Bitmap also deadlocks writeback against the folio it already holds locked.</p> <p>These files are maintained by the driver itself and have no valid reason to be written through the file interface. Mark base metadata files (mft_no &lt; FILE_first_user) as immutable during inode read so the VFS rejects write, mmap, truncate and unlink with -EPERM. Directories are skipped so the root and $Extend remain usable. Internal metadata updates do not go through the VFS write path and are unaffected.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ntfs: make system files immutable to prevent corruption</p> <p>When a system file such as $Bitmap is exposed via show_sys_files and written from userspace, the volume is corrupted and, because the cluster allocator scans $Bitmap through the same inode&#39;s page cache, a write to $Bitmap also deadlocks writeback against the folio it already holds locked.</p> <p>These files are maintained by the driver itself and have no valid reason to be written through the file interface. Mark base metadata files (mft_no &lt; FILE_first_user) as immutable during inode read so the VFS rejects write, mmap, truncate and unlink with -EPERM. Directories are skipped so the root and $Extend remain usable. Internal metadata updates do not go through the VFS write path and are unaffected.</p> https://vulnerability.circl.lu/vuln/ghsa-cpf7-qp55-xqgv https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-72186 <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 93 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: ntfs: make system files immutable to prevent corruption When a system file such as $Bitmap is exposed via show_sys_files and written from userspace, the volume is corrupted and, because the cluster allocator scans $Bitmap through the same inode&#39;s page cache, a write to $Bitmap also deadlocks writeback against the folio it already holds locked. These files are maintained by the driver itself and have no valid reason to be written through the file interface. Mark base metadata files (mft_no &lt; FILE_first_user) as immutable during inode read so the VFS rejects write, mmap, truncate and unlink with -EPERM. Directories are skipped so the root and $Extend remain usable. Internal metadata updates do not go through the VFS write path and are unaffected.</p> <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 93 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: ntfs: make system files immutable to prevent corruption When a system file such as $Bitmap is exposed via show_sys_files and written from userspace, the volume is corrupted and, because the cluster allocator scans $Bitmap through the same inode&#39;s page cache, a write to $Bitmap also deadlocks writeback against the folio it already holds locked. These files are maintained by the driver itself and have no valid reason to be written through the file interface. Mark base metadata files (mft_no &lt; FILE_first_user) as immutable during inode read so the VFS rejects write, mmap, truncate and unlink with -EPERM. Directories are skipped so the root and $Extend remain usable. Internal metadata updates do not go through the VFS write path and are unaffected.</p> https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-72186 https://vulnerability.circl.lu/vuln/wid-sec-w-2026-2852 <p>Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.</p> <p>Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.</p> https://vulnerability.circl.lu/vuln/wid-sec-w-2026-2852