https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 10 Oct 2026 05:04:37 +0000 https://cve.radiocsirt.org/vuln/bell-cve-2026-53334 <p><strong>Affected:</strong> Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:stream: linux-lts</p> https://cve.radiocsirt.org/vuln/bell-cve-2026-53334 https://cve.radiocsirt.org/vuln/certfr-2026-avi-1162 certfr-2026-avi-1162 https://cve.radiocsirt.org/vuln/certfr-2026-avi-1162 https://cve.radiocsirt.org/vuln/euvd-2026-331657 EUVD-2026-331657 https://cve.radiocsirt.org/vuln/euvd-2026-331657 https://cve.radiocsirt.org/vuln/fkie_cve-2026-53334 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>mm/damon/reclaim: handle ctx allocation failure</p> <p>Patch series &#34;mm/damon/{reclaim,lru_sort}: handle ctx allocation failures&#34;.</p> <p>DAMON_RECLAIM and DAMON_LRU_SORT could dereference NULL pointers if their damon_ctx object allocations fail. The bugs are expected to happen infrequently because the allocations are arguably too small to fail on common setups. But theoretically they are possible and the consequences are bad. Fix those.</p> <p>The issues were discovered [1] by Sashiko.</p> <p>This patch (of 2):</p> <p>DAMON_RECLAIM allocates the damon_ctx object for its kdamond in its init function. damon_reclaim_enabled_store() wrongly assumes the allocation will always succeed once tried. If the damon_ctx allocation was failed, therefore, code execution reaches to damon_commit_ctx() while &#39;ctx&#39; is NULL. As a result, it dereferences the NULL &#39;ctx&#39; pointer. Avoid the NULL dereference by returning -ENOMEM if &#39;ctx&#39; is NULL.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>mm/damon/reclaim: handle ctx allocation failure</p> <p>Patch series &#34;mm/damon/{reclaim,lru_sort}: handle ctx allocation failures&#34;.</p> <p>DAMON_RECLAIM and DAMON_LRU_SORT could dereference NULL pointers if their damon_ctx object allocations fail. The bugs are expected to happen infrequently because the allocations are arguably too small to fail on common setups. But theoretically they are possible and the consequences are bad. Fix those.</p> <p>The issues were discovered [1] by Sashiko.</p> <p>This patch (of 2):</p> <p>DAMON_RECLAIM allocates the damon_ctx object for its kdamond in its init function. damon_reclaim_enabled_store() wrongly assumes the allocation will always succeed once tried. If the damon_ctx allocation was failed, therefore, code execution reaches to damon_commit_ctx() while &#39;ctx&#39; is NULL. As a result, it dereferences the NULL &#39;ctx&#39; pointer. Avoid the NULL dereference by returning -ENOMEM if &#39;ctx&#39; is NULL.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-53334 https://cve.radiocsirt.org/vuln/ghsa-q79f-r3xp-pp5m <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>mm/damon/reclaim: handle ctx allocation failure</p> <p>Patch series &#34;mm/damon/{reclaim,lru_sort}: handle ctx allocation failures&#34;.</p> <p>DAMON_RECLAIM and DAMON_LRU_SORT could dereference NULL pointers if their damon_ctx object allocations fail. The bugs are expected to happen infrequently because the allocations are arguably too small to fail on common setups. But theoretically they are possible and the consequences are bad. Fix those.</p> <p>The issues were discovered [1] by Sashiko.</p> <p>This patch (of 2):</p> <p>DAMON_RECLAIM allocates the damon_ctx object for its kdamond in its init function. damon_reclaim_enabled_store() wrongly assumes the allocation will always succeed once tried. If the damon_ctx allocation was failed, therefore, code execution reaches to damon_commit_ctx() while &#39;ctx&#39; is NULL. As a result, it dereferences the NULL &#39;ctx&#39; pointer. Avoid the NULL dereference by returning -ENOMEM if &#39;ctx&#39; is NULL.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>mm/damon/reclaim: handle ctx allocation failure</p> <p>Patch series &#34;mm/damon/{reclaim,lru_sort}: handle ctx allocation failures&#34;.</p> <p>DAMON_RECLAIM and DAMON_LRU_SORT could dereference NULL pointers if their damon_ctx object allocations fail. The bugs are expected to happen infrequently because the allocations are arguably too small to fail on common setups. But theoretically they are possible and the consequences are bad. Fix those.</p> <p>The issues were discovered [1] by Sashiko.</p> <p>This patch (of 2):</p> <p>DAMON_RECLAIM allocates the damon_ctx object for its kdamond in its init function. damon_reclaim_enabled_store() wrongly assumes the allocation will always succeed once tried. If the damon_ctx allocation was failed, therefore, code execution reaches to damon_commit_ctx() while &#39;ctx&#39; is NULL. As a result, it dereferences the NULL &#39;ctx&#39; pointer. Avoid the NULL dereference by returning -ENOMEM if &#39;ctx&#39; is NULL.</p> https://cve.radiocsirt.org/vuln/ghsa-q79f-r3xp-pp5m https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-53334 <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 110 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: mm/damon/reclaim: handle ctx allocation failure Patch series &#34;mm/damon/{reclaim,lru_sort}: handle ctx allocation failures&#34;. DAMON_RECLAIM and DAMON_LRU_SORT could dereference NULL pointers if their damon_ctx object allocations fail. The bugs are expected to happen infrequently because the allocations are arguably too small to fail on common setups. But theoretically they are possible and the consequences are bad. Fix those. The issues were discovered [1] by Sashiko. This patch (of 2): DAMON_RECLAIM allocates the damon_ctx object for its kdamond in its init function. damon_reclaim_enabled_store() wrongly assumes the allocation will always succeed once tried. If the damon_ctx allocation was failed, therefore, code execution reaches to damon_commit_ctx() while &#39;ctx&#39; is NULL. As a result, it dereferences the NULL &#39;ctx&#39; pointer. Avoid the NULL dereference by returning -ENOMEM if &#39;ctx&#39; is NULL.</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 110 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: mm/damon/reclaim: handle ctx allocation failure Patch series &#34;mm/damon/{reclaim,lru_sort}: handle ctx allocation failures&#34;. DAMON_RECLAIM and DAMON_LRU_SORT could dereference NULL pointers if their damon_ctx object allocations fail. The bugs are expected to happen infrequently because the allocations are arguably too small to fail on common setups. But theoretically they are possible and the consequences are bad. Fix those. The issues were discovered [1] by Sashiko. This patch (of 2): DAMON_RECLAIM allocates the damon_ctx object for its kdamond in its init function. damon_reclaim_enabled_store() wrongly assumes the allocation will always succeed once tried. If the damon_ctx allocation was failed, therefore, code execution reaches to damon_commit_ctx() while &#39;ctx&#39; is NULL. As a result, it dereferences the NULL &#39;ctx&#39; pointer. Avoid the NULL dereference by returning -ENOMEM if &#39;ctx&#39; is NULL.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-53334 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2175 <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, darunter möglicherweise das Auslösen eines Denial-of-Service-Zustands, die Umgehung von Sicherheitsmaßnahmen oder das Verursachen von Speicherbeschädigungen.</p> <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, darunter möglicherweise das Auslösen eines Denial-of-Service-Zustands, die Umgehung von Sicherheitsmaßnahmen oder das Verursachen von Speicherbeschädigungen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2175