https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 08:21:58 +0000 https://cve.radiocsirt.org/vuln/bdu:2024-08987 bdu:2024-08987 https://cve.radiocsirt.org/vuln/bdu:2024-08987 https://cve.radiocsirt.org/vuln/bell-cve-2024-47676 <p><strong>Affected:</strong> Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> https://cve.radiocsirt.org/vuln/bell-cve-2024-47676 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0152 certfr-2025-avi-0152 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0152 https://cve.radiocsirt.org/vuln/euvd-2026-346164 EUVD-2026-346164 https://cve.radiocsirt.org/vuln/euvd-2026-346164 https://cve.radiocsirt.org/vuln/fkie_cve-2024-47676 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>mm/hugetlb.c: fix UAF of vma in hugetlb fault pathway</p> <p>Syzbot reports a UAF in hugetlb_fault(). This happens because vmf_anon_prepare() could drop the per-VMA lock and allow the current VMA to be freed before hugetlb_vma_unlock_read() is called.</p> <p>We can fix this by using a modified version of vmf_anon_prepare() that doesn&#39;t release the VMA lock on failure, and then release it ourselves after hugetlb_vma_unlock_read().</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>mm/hugetlb.c: fix UAF of vma in hugetlb fault pathway</p> <p>Syzbot reports a UAF in hugetlb_fault(). This happens because vmf_anon_prepare() could drop the per-VMA lock and allow the current VMA to be freed before hugetlb_vma_unlock_read() is called.</p> <p>We can fix this by using a modified version of vmf_anon_prepare() that doesn&#39;t release the VMA lock on failure, and then release it ourselves after hugetlb_vma_unlock_read().</p> https://cve.radiocsirt.org/vuln/fkie_cve-2024-47676 https://cve.radiocsirt.org/vuln/ghsa-7jh9-v3vw-v9px <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>mm/hugetlb.c: fix UAF of vma in hugetlb fault pathway</p> <p>Syzbot reports a UAF in hugetlb_fault(). This happens because vmf_anon_prepare() could drop the per-VMA lock and allow the current VMA to be freed before hugetlb_vma_unlock_read() is called.</p> <p>We can fix this by using a modified version of vmf_anon_prepare() that doesn&#39;t release the VMA lock on failure, and then release it ourselves after hugetlb_vma_unlock_read().</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>mm/hugetlb.c: fix UAF of vma in hugetlb fault pathway</p> <p>Syzbot reports a UAF in hugetlb_fault(). This happens because vmf_anon_prepare() could drop the per-VMA lock and allow the current VMA to be freed before hugetlb_vma_unlock_read() is called.</p> <p>We can fix this by using a modified version of vmf_anon_prepare() that doesn&#39;t release the VMA lock on failure, and then release it ourselves after hugetlb_vma_unlock_read().</p> https://cve.radiocsirt.org/vuln/ghsa-7jh9-v3vw-v9px https://cve.radiocsirt.org/vuln/opensuse-su-2024:14500-1 <p>kernel-devel-6.11.8-1.1 on GA media</p> <p>kernel-devel-6.11.8-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2024:14500-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-47676 <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 67 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: mm/hugetlb.c: fix UAF of vma in hugetlb fault pathway Syzbot reports a UAF in hugetlb_fault(). This happens because vmf_anon_prepare() could drop the per-VMA lock and allow the current VMA to be freed before hugetlb_vma_unlock_read() is called. We can fix this by using a modified version of vmf_anon_prepare() that doesn&#39;t release the VMA lock on failure, and then release it ourselves after hugetlb_vma_unlock_read().</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 67 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: mm/hugetlb.c: fix UAF of vma in hugetlb fault pathway Syzbot reports a UAF in hugetlb_fault(). This happens because vmf_anon_prepare() could drop the per-VMA lock and allow the current VMA to be freed before hugetlb_vma_unlock_read() is called. We can fix this by using a modified version of vmf_anon_prepare() that doesn&#39;t release the VMA lock on failure, and then release it ourselves after hugetlb_vma_unlock_read().</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-47676 https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3251 <p>Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere, nicht näher bekannte Auswirkungen zu erzielen..</p> <p>Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere, nicht näher bekannte Auswirkungen zu erzielen..</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3251