https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Thu, 12 Nov 2026 06:23:49 +0000 https://db.gcve.eu/vuln/certfr-2026-avi-1375 certfr-2026-avi-1375 https://db.gcve.eu/vuln/certfr-2026-avi-1375 https://db.gcve.eu/vuln/fkie_cve-2026-98445 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>xfs: don&#39;t let memory failures leak blocks and kill repairs</p> <p>LOLLM complains that a memory allocation failure in xrep_newbt_add_blocks results in online repair leaking blocks that were previously allocated to write a new btree, but the problem is worse than that -- a limitation of the codebase is that the callers cannot undo the transaction /and/ return the error -- either you undo all changes and commit the transaction, or you error out and the filesystem goes down.</p> <p>However, the new btree space reservation object isn&#39;t that big (~48 bytes). Let&#39;s just do a NOFAIL allocation and the problem goes away.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>xfs: don&#39;t let memory failures leak blocks and kill repairs</p> <p>LOLLM complains that a memory allocation failure in xrep_newbt_add_blocks results in online repair leaking blocks that were previously allocated to write a new btree, but the problem is worse than that -- a limitation of the codebase is that the callers cannot undo the transaction /and/ return the error -- either you undo all changes and commit the transaction, or you error out and the filesystem goes down.</p> <p>However, the new btree space reservation object isn&#39;t that big (~48 bytes). Let&#39;s just do a NOFAIL allocation and the problem goes away.</p> https://db.gcve.eu/vuln/fkie_cve-2026-98445 https://db.gcve.eu/vuln/ghsa-vx8f-phpg-5qwp <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>xfs: don&#39;t let memory failures leak blocks and kill repairs</p> <p>LOLLM complains that a memory allocation failure in xrep_newbt_add_blocks results in online repair leaking blocks that were previously allocated to write a new btree, but the problem is worse than that -- a limitation of the codebase is that the callers cannot undo the transaction /and/ return the error -- either you undo all changes and commit the transaction, or you error out and the filesystem goes down.</p> <p>However, the new btree space reservation object isn&#39;t that big (~48 bytes). Let&#39;s just do a NOFAIL allocation and the problem goes away.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>xfs: don&#39;t let memory failures leak blocks and kill repairs</p> <p>LOLLM complains that a memory allocation failure in xrep_newbt_add_blocks results in online repair leaking blocks that were previously allocated to write a new btree, but the problem is worse than that -- a limitation of the codebase is that the callers cannot undo the transaction /and/ return the error -- either you undo all changes and commit the transaction, or you error out and the filesystem goes down.</p> <p>However, the new btree space reservation object isn&#39;t that big (~48 bytes). Let&#39;s just do a NOFAIL allocation and the problem goes away.</p> https://db.gcve.eu/vuln/ghsa-vx8f-phpg-5qwp https://db.gcve.eu/vuln/msrc_cve-2026-98445 msrc_CVE-2026-98445 https://db.gcve.eu/vuln/msrc_cve-2026-98445 https://db.gcve.eu/vuln/ubuntu-cve-2026-98445 <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 156 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: xfs: don&#39;t let memory failures leak blocks and kill repairs LOLLM complains that a memory allocation failure in xrep_newbt_add_blocks results in online repair leaking blocks that were previously allocated to write a new btree, but the problem is worse than that -- a limitation of the codebase is that the callers cannot undo the transaction /and/ return the error -- either you undo all changes and commit the transaction, or you error out and the filesystem goes down. However, the new btree space reservation object isn&#39;t that big (~48 bytes). Let&#39;s just do a NOFAIL allocation and the problem goes away.</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 156 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: xfs: don&#39;t let memory failures leak blocks and kill repairs LOLLM complains that a memory allocation failure in xrep_newbt_add_blocks results in online repair leaking blocks that were previously allocated to write a new btree, but the problem is worse than that -- a limitation of the codebase is that the callers cannot undo the transaction /and/ return the error -- either you undo all changes and commit the transaction, or you error out and the filesystem goes down. However, the new btree space reservation object isn&#39;t that big (~48 bytes). Let&#39;s just do a NOFAIL allocation and the problem goes away.</p> https://db.gcve.eu/vuln/ubuntu-cve-2026-98445