https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 28 Sep 2026 11:32:24 +0000 https://vulnerability.circl.lu/vuln/fkie_cve-2026-98139 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ntfs: only count successfully cleared runs when freeing clusters</p> <p>ntfs_cluster_free_from_rl_nolock() adds a run&#39;s length to nr_freed whenever the error bookkeeping condition is false, which includes cases where ntfs_bitmap_clear_run() actually failed - e.g. a second run failing with the same errno as an earlier one, or any failure after a non-ENOMEM error was already recorded. Since a failed ntfs_bitmap_clear_run() rolls back its partial modifications, no bits were cleared for that run, yet its length still inflates vol-&gt;free_clusters, corrupting statfs output and the allocator&#39;s free space gate.</p> <p>Only count runs whose bitmap clear succeeded.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ntfs: only count successfully cleared runs when freeing clusters</p> <p>ntfs_cluster_free_from_rl_nolock() adds a run&#39;s length to nr_freed whenever the error bookkeeping condition is false, which includes cases where ntfs_bitmap_clear_run() actually failed - e.g. a second run failing with the same errno as an earlier one, or any failure after a non-ENOMEM error was already recorded. Since a failed ntfs_bitmap_clear_run() rolls back its partial modifications, no bits were cleared for that run, yet its length still inflates vol-&gt;free_clusters, corrupting statfs output and the allocator&#39;s free space gate.</p> <p>Only count runs whose bitmap clear succeeded.</p> https://vulnerability.circl.lu/vuln/fkie_cve-2026-98139 https://vulnerability.circl.lu/vuln/ghsa-6rpr-wqmr-68rh <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ntfs: only count successfully cleared runs when freeing clusters</p> <p>ntfs_cluster_free_from_rl_nolock() adds a run&#39;s length to nr_freed whenever the error bookkeeping condition is false, which includes cases where ntfs_bitmap_clear_run() actually failed - e.g. a second run failing with the same errno as an earlier one, or any failure after a non-ENOMEM error was already recorded. Since a failed ntfs_bitmap_clear_run() rolls back its partial modifications, no bits were cleared for that run, yet its length still inflates vol-&gt;free_clusters, corrupting statfs output and the allocator&#39;s free space gate.</p> <p>Only count runs whose bitmap clear succeeded.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ntfs: only count successfully cleared runs when freeing clusters</p> <p>ntfs_cluster_free_from_rl_nolock() adds a run&#39;s length to nr_freed whenever the error bookkeeping condition is false, which includes cases where ntfs_bitmap_clear_run() actually failed - e.g. a second run failing with the same errno as an earlier one, or any failure after a non-ENOMEM error was already recorded. Since a failed ntfs_bitmap_clear_run() rolls back its partial modifications, no bits were cleared for that run, yet its length still inflates vol-&gt;free_clusters, corrupting statfs output and the allocator&#39;s free space gate.</p> <p>Only count runs whose bitmap clear succeeded.</p> https://vulnerability.circl.lu/vuln/ghsa-6rpr-wqmr-68rh https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-98139 <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 246 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: ntfs: only count successfully cleared runs when freeing clusters ntfs_cluster_free_from_rl_nolock() adds a run&#39;s length to nr_freed whenever the error bookkeeping condition is false, which includes cases where ntfs_bitmap_clear_run() actually failed - e.g. a second run failing with the same errno as an earlier one, or any failure after a non-ENOMEM error was already recorded. Since a failed ntfs_bitmap_clear_run() rolls back its partial modifications, no bits were cleared for that run, yet its length still inflates vol-&gt;free_clusters, corrupting statfs output and the allocator&#39;s free space gate. Only count runs whose bitmap clear succeeded.</p> <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 246 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: ntfs: only count successfully cleared runs when freeing clusters ntfs_cluster_free_from_rl_nolock() adds a run&#39;s length to nr_freed whenever the error bookkeeping condition is false, which includes cases where ntfs_bitmap_clear_run() actually failed - e.g. a second run failing with the same errno as an earlier one, or any failure after a non-ENOMEM error was already recorded. Since a failed ntfs_bitmap_clear_run() rolls back its partial modifications, no bits were cleared for that run, yet its length still inflates vol-&gt;free_clusters, corrupting statfs output and the allocator&#39;s free space gate. Only count runs whose bitmap clear succeeded.</p> https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-98139 https://vulnerability.circl.lu/vuln/wid-sec-w-2026-3579 <p>Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Zustand herbeizuführen oder nicht näher spezifizierten Angriff durchzuführen.</p> <p>Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Zustand herbeizuführen oder nicht näher spezifizierten Angriff durchzuführen.</p> https://vulnerability.circl.lu/vuln/wid-sec-w-2026-3579