https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 23:42:30 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-00747 bdu:2026-00747 https://cve.radiocsirt.org/vuln/bdu:2026-00747 https://cve.radiocsirt.org/vuln/bell-cve-2025-68771 <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> https://cve.radiocsirt.org/vuln/bell-cve-2025-68771 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0166 certfr-2026-avi-0166 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0166 https://cve.radiocsirt.org/vuln/euvd-2026-315176 EUVD-2026-315176 https://cve.radiocsirt.org/vuln/euvd-2026-315176 https://cve.radiocsirt.org/vuln/fkie_cve-2025-68771 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ocfs2: fix kernel BUG in ocfs2_find_victim_chain</p> <p>syzbot reported a kernel BUG in ocfs2_find_victim_chain() because the `cl_next_free_rec` field of the allocation chain list (next free slot in the chain list) is 0, triggring the BUG_ON(!cl-&gt;cl_next_free_rec) condition in ocfs2_find_victim_chain() and panicking the kernel.</p> <p>To fix this, an if condition is introduced in ocfs2_claim_suballoc_bits(), just before calling ocfs2_find_victim_chain(), the code block in it being executed when either of the following conditions is true:</p> <p>1. `cl_next_free_rec` is equal to 0, indicating that there are no free chains in the allocation chain list 2. `cl_next_free_rec` is greater than `cl_count` (the total number of chains in the allocation chain list)</p> <p>Either of them being true is indicative of the fact that there are no chains left for usage.</p> <p>This is addressed using ocfs2_error(), which prints the error log for debugging purposes, rather than panicking the kernel.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ocfs2: fix kernel BUG in ocfs2_find_victim_chain</p> <p>syzbot reported a kernel BUG in ocfs2_find_victim_chain() because the `cl_next_free_rec` field of the allocation chain list (next free slot in the chain list) is 0, triggring the BUG_ON(!cl-&gt;cl_next_free_rec) condition in ocfs2_find_victim_chain() and panicking the kernel.</p> <p>To fix this, an if condition is introduced in ocfs2_claim_suballoc_bits(), just before calling ocfs2_find_victim_chain(), the code block in it being executed when either of the following conditions is true:</p> <p>1. `cl_next_free_rec` is equal to 0, indicating that there are no free chains in the allocation chain list 2. `cl_next_free_rec` is greater than `cl_count` (the total number of chains in the allocation chain list)</p> <p>Either of them being true is indicative of the fact that there are no chains left for usage.</p> <p>This is addressed using ocfs2_error(), which prints the error log for debugging purposes, rather than panicking the kernel.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-68771 https://cve.radiocsirt.org/vuln/ghsa-48cw-6cgr-r587 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ocfs2: fix kernel BUG in ocfs2_find_victim_chain</p> <p>syzbot reported a kernel BUG in ocfs2_find_victim_chain() because the `cl_next_free_rec` field of the allocation chain list (next free slot in the chain list) is 0, triggring the BUG_ON(!cl-&gt;cl_next_free_rec) condition in ocfs2_find_victim_chain() and panicking the kernel.</p> <p>To fix this, an if condition is introduced in ocfs2_claim_suballoc_bits(), just before calling ocfs2_find_victim_chain(), the code block in it being executed when either of the following conditions is true:</p> <p>1. `cl_next_free_rec` is equal to 0, indicating that there are no free chains in the allocation chain list 2. `cl_next_free_rec` is greater than `cl_count` (the total number of chains in the allocation chain list)</p> <p>Either of them being true is indicative of the fact that there are no chains left for usage.</p> <p>This is addressed using ocfs2_error(), which prints the error log for debugging purposes, rather than panicking the kernel.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ocfs2: fix kernel BUG in ocfs2_find_victim_chain</p> <p>syzbot reported a kernel BUG in ocfs2_find_victim_chain() because the `cl_next_free_rec` field of the allocation chain list (next free slot in the chain list) is 0, triggring the BUG_ON(!cl-&gt;cl_next_free_rec) condition in ocfs2_find_victim_chain() and panicking the kernel.</p> <p>To fix this, an if condition is introduced in ocfs2_claim_suballoc_bits(), just before calling ocfs2_find_victim_chain(), the code block in it being executed when either of the following conditions is true:</p> <p>1. `cl_next_free_rec` is equal to 0, indicating that there are no free chains in the allocation chain list 2. `cl_next_free_rec` is greater than `cl_count` (the total number of chains in the allocation chain list)</p> <p>Either of them being true is indicative of the fact that there are no chains left for usage.</p> <p>This is addressed using ocfs2_error(), which prints the error log for debugging purposes, rather than panicking the kernel.</p> https://cve.radiocsirt.org/vuln/ghsa-48cw-6cgr-r587 https://cve.radiocsirt.org/vuln/msrc_cve-2025-68771 msrc_CVE-2025-68771 https://cve.radiocsirt.org/vuln/msrc_cve-2025-68771 https://cve.radiocsirt.org/vuln/opensuse-su-2026:20287-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://cve.radiocsirt.org/vuln/opensuse-su-2026:20287-1 https://cve.radiocsirt.org/vuln/suse-su-2026:0411-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://cve.radiocsirt.org/vuln/suse-su-2026:0411-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-68771 <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 232 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: ocfs2: fix kernel BUG in ocfs2_find_victim_chain syzbot reported a kernel BUG in ocfs2_find_victim_chain() because the `cl_next_free_rec` field of the allocation chain list (next free slot in the chain list) is 0, triggring the BUG_ON(!cl-&gt;cl_next_free_rec) condition in ocfs2_find_victim_chain() and panicking the kernel. To fix this, an if condition is introduced in ocfs2_claim_suballoc_bits(), just before calling ocfs2_find_victim_chain(), the code block in it being executed when either of the following conditions is true: 1. `cl_next_free_rec` is equal to 0, indicating that there are no free chains in the allocation chain list 2. `cl_next_free_rec` is greater than `cl_count` (the total number of chains in the allocation chain list) Either of them being true is indicative of the fact that there are no chains left for usage. This is addressed using ocfs2_error(), which prints the error log for debugging purposes, rather than panicking the kernel.</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 232 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: ocfs2: fix kernel BUG in ocfs2_find_victim_chain syzbot reported a kernel BUG in ocfs2_find_victim_chain() because the `cl_next_free_rec` field of the allocation chain list (next free slot in the chain list) is 0, triggring the BUG_ON(!cl-&gt;cl_next_free_rec) condition in ocfs2_find_victim_chain() and panicking the kernel. To fix this, an if condition is introduced in ocfs2_claim_suballoc_bits(), just before calling ocfs2_find_victim_chain(), the code block in it being executed when either of the following conditions is true: 1. `cl_next_free_rec` is equal to 0, indicating that there are no free chains in the allocation chain list 2. `cl_next_free_rec` is greater than `cl_count` (the total number of chains in the allocation chain list) Either of them being true is indicative of the fact that there are no chains left for usage. This is addressed using ocfs2_error(), which prints the error log for debugging purposes, rather than panicking the kernel.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-68771 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0086 <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.</p> <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0086