https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 07 Oct 2026 04:55:40 +0000 https://cve.radiocsirt.org/vuln/bdu:2025-07488 bdu:2025-07488 https://cve.radiocsirt.org/vuln/bdu:2025-07488 https://cve.radiocsirt.org/vuln/bell-cve-2024-43843 <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-43843 https://cve.radiocsirt.org/vuln/certfr-2024-avi-1080 certfr-2024-avi-1080 https://cve.radiocsirt.org/vuln/certfr-2024-avi-1080 https://cve.radiocsirt.org/vuln/euvd-2026-313136 EUVD-2026-313136 https://cve.radiocsirt.org/vuln/euvd-2026-313136 https://cve.radiocsirt.org/vuln/fkie_cve-2024-43843 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>riscv, bpf: Fix out-of-bounds issue when preparing trampoline image</p> <p>We get the size of the trampoline image during the dry run phase and allocate memory based on that size. The allocated image will then be populated with instructions during the real patch phase. But after commit 26ef208c209a (&#34;bpf: Use arch_bpf_trampoline_size&#34;), the `im` argument is inconsistent in the dry run and real patch phase. This may cause emit_imm in RV64 to generate a different number of instructions when generating the &#39;im&#39; address, potentially causing out-of-bounds issues. Let&#39;s emit the maximum number of instructions for the &#34;im&#34; address during dry run to fix this problem.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>riscv, bpf: Fix out-of-bounds issue when preparing trampoline image</p> <p>We get the size of the trampoline image during the dry run phase and allocate memory based on that size. The allocated image will then be populated with instructions during the real patch phase. But after commit 26ef208c209a (&#34;bpf: Use arch_bpf_trampoline_size&#34;), the `im` argument is inconsistent in the dry run and real patch phase. This may cause emit_imm in RV64 to generate a different number of instructions when generating the &#39;im&#39; address, potentially causing out-of-bounds issues. Let&#39;s emit the maximum number of instructions for the &#34;im&#34; address during dry run to fix this problem.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2024-43843 https://cve.radiocsirt.org/vuln/ghsa-r657-mr7r-rf9x <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>riscv, bpf: Fix out-of-bounds issue when preparing trampoline image</p> <p>We get the size of the trampoline image during the dry run phase and allocate memory based on that size. The allocated image will then be populated with instructions during the real patch phase. But after commit 26ef208c209a (&#34;bpf: Use arch_bpf_trampoline_size&#34;), the `im` argument is inconsistent in the dry run and real patch phase. This may cause emit_imm in RV64 to generate a different number of instructions when generating the &#39;im&#39; address, potentially causing out-of-bounds issues. Let&#39;s emit the maximum number of instructions for the &#34;im&#34; address during dry run to fix this problem.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>riscv, bpf: Fix out-of-bounds issue when preparing trampoline image</p> <p>We get the size of the trampoline image during the dry run phase and allocate memory based on that size. The allocated image will then be populated with instructions during the real patch phase. But after commit 26ef208c209a (&#34;bpf: Use arch_bpf_trampoline_size&#34;), the `im` argument is inconsistent in the dry run and real patch phase. This may cause emit_imm in RV64 to generate a different number of instructions when generating the &#39;im&#39; address, potentially causing out-of-bounds issues. Let&#39;s emit the maximum number of instructions for the &#34;im&#34; address during dry run to fix this problem.</p> https://cve.radiocsirt.org/vuln/ghsa-r657-mr7r-rf9x https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-43843 <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 88 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: riscv, bpf: Fix out-of-bounds issue when preparing trampoline image We get the size of the trampoline image during the dry run phase and allocate memory based on that size. The allocated image will then be populated with instructions during the real patch phase. But after commit 26ef208c209a (&#34;bpf: Use arch_bpf_trampoline_size&#34;), the `im` argument is inconsistent in the dry run and real patch phase. This may cause emit_imm in RV64 to generate a different number of instructions when generating the &#39;im&#39; address, potentially causing out-of-bounds issues. Let&#39;s emit the maximum number of instructions for the &#34;im&#34; address during dry run to fix this problem.</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 88 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: riscv, bpf: Fix out-of-bounds issue when preparing trampoline image We get the size of the trampoline image during the dry run phase and allocate memory based on that size. The allocated image will then be populated with instructions during the real patch phase. But after commit 26ef208c209a (&#34;bpf: Use arch_bpf_trampoline_size&#34;), the `im` argument is inconsistent in the dry run and real patch phase. This may cause emit_imm in RV64 to generate a different number of instructions when generating the &#39;im&#39; address, potentially causing out-of-bounds issues. Let&#39;s emit the maximum number of instructions for the &#34;im&#34; address during dry run to fix this problem.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-43843 https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1875 <p>Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder unbekannte Auswirkungen zu erzielen.</p> <p>Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder unbekannte Auswirkungen zu erzielen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1875