https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 15:01:20 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-12432 bdu:2026-12432 https://cve.radiocsirt.org/vuln/bdu:2026-12432 https://cve.radiocsirt.org/vuln/bell-cve-2025-71109 <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-71109 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-347548 EUVD-2026-347548 https://cve.radiocsirt.org/vuln/euvd-2026-347548 https://cve.radiocsirt.org/vuln/fkie_cve-2025-71109 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>MIPS: ftrace: Fix memory corruption when kernel is located beyond 32 bits</p> <p>Since commit e424054000878 (&#34;MIPS: Tracing: Reduce the overhead of dynamic Function Tracer&#34;), the macro UASM_i_LA_mostly has been used, and this macro can generate more than 2 instructions. At the same time, the code in ftrace assumes that no more than 2 instructions can be generated, which is why it stores them in an int[2] array. However, as previously noted, the macro UASM_i_LA_mostly (and now UASM_i_LA) causes a buffer overflow when _mcount is beyond 32 bits. This leads to corruption of the variables located in the __read_mostly section.</p> <p>This corruption was observed because the variable __cpu_primary_thread_mask was corrupted, causing a hang very early during boot.</p> <p>This fix prevents the corruption by avoiding the generation of instructions if they could exceed 2 instructions in length. Fortunately, insn_la_mcount is only used if the instrumented code is located outside the kernel code section, so dynamic ftrace can still be used, albeit in a more limited scope. This is still preferable to corrupting memory and/or crashing the kernel.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>MIPS: ftrace: Fix memory corruption when kernel is located beyond 32 bits</p> <p>Since commit e424054000878 (&#34;MIPS: Tracing: Reduce the overhead of dynamic Function Tracer&#34;), the macro UASM_i_LA_mostly has been used, and this macro can generate more than 2 instructions. At the same time, the code in ftrace assumes that no more than 2 instructions can be generated, which is why it stores them in an int[2] array. However, as previously noted, the macro UASM_i_LA_mostly (and now UASM_i_LA) causes a buffer overflow when _mcount is beyond 32 bits. This leads to corruption of the variables located in the __read_mostly section.</p> <p>This corruption was observed because the variable __cpu_primary_thread_mask was corrupted, causing a hang very early during boot.</p> <p>This fix prevents the corruption by avoiding the generation of instructions if they could exceed 2 instructions in length. Fortunately, insn_la_mcount is only used if the instrumented code is located outside the kernel code section, so dynamic ftrace can still be used, albeit in a more limited scope. This is still preferable to corrupting memory and/or crashing the kernel.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-71109 https://cve.radiocsirt.org/vuln/ghsa-f8h3-qj6h-j2cj <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>MIPS: ftrace: Fix memory corruption when kernel is located beyond 32 bits</p> <p>Since commit e424054000878 (&#34;MIPS: Tracing: Reduce the overhead of dynamic Function Tracer&#34;), the macro UASM_i_LA_mostly has been used, and this macro can generate more than 2 instructions. At the same time, the code in ftrace assumes that no more than 2 instructions can be generated, which is why it stores them in an int[2] array. However, as previously noted, the macro UASM_i_LA_mostly (and now UASM_i_LA) causes a buffer overflow when _mcount is beyond 32 bits. This leads to corruption of the variables located in the __read_mostly section.</p> <p>This corruption was observed because the variable __cpu_primary_thread_mask was corrupted, causing a hang very early during boot.</p> <p>This fix prevents the corruption by avoiding the generation of instructions if they could exceed 2 instructions in length. Fortunately, insn_la_mcount is only used if the instrumented code is located outside the kernel code section, so dynamic ftrace can still be used, albeit in a more limited scope. This is still preferable to corrupting memory and/or crashing the kernel.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>MIPS: ftrace: Fix memory corruption when kernel is located beyond 32 bits</p> <p>Since commit e424054000878 (&#34;MIPS: Tracing: Reduce the overhead of dynamic Function Tracer&#34;), the macro UASM_i_LA_mostly has been used, and this macro can generate more than 2 instructions. At the same time, the code in ftrace assumes that no more than 2 instructions can be generated, which is why it stores them in an int[2] array. However, as previously noted, the macro UASM_i_LA_mostly (and now UASM_i_LA) causes a buffer overflow when _mcount is beyond 32 bits. This leads to corruption of the variables located in the __read_mostly section.</p> <p>This corruption was observed because the variable __cpu_primary_thread_mask was corrupted, causing a hang very early during boot.</p> <p>This fix prevents the corruption by avoiding the generation of instructions if they could exceed 2 instructions in length. Fortunately, insn_la_mcount is only used if the instrumented code is located outside the kernel code section, so dynamic ftrace can still be used, albeit in a more limited scope. This is still preferable to corrupting memory and/or crashing the kernel.</p> https://cve.radiocsirt.org/vuln/ghsa-f8h3-qj6h-j2cj https://cve.radiocsirt.org/vuln/msrc_cve-2025-71109 msrc_CVE-2025-71109 https://cve.radiocsirt.org/vuln/msrc_cve-2025-71109 https://cve.radiocsirt.org/vuln/oesa-2026-2676 <p><strong>Affected:</strong> openEuler:24.03-LTS-SP3: kernel</p> <p>The Linux Kernel, the operating system core itself. Security Fix(es):</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>parisc: Drop WARN_ON_ONCE() from flush_cache_vmap</p> <p>I have observed warning to occassionally trigger.(CVE-2025-39781)</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>MIPS: ftrace: Fix memory corruption when kernel is located beyond 32 bits</p> <p>Since commit e424054000878 (&amp;quot;MIPS: Tracing: Reduce the overhead of dynamic Function Tracer&amp;quot;), the macro UASM_i_LA_mostly has been used, and this macro can generate more than 2 instructions. At the same time, the code in ftrace assumes that no more than 2 instructions can be generated, which is why it stores them in an int[2] array. However, as previously noted, the macro UASM_i_LA_mostly (and now UASM_i_LA) causes a buffer overflow when _mcount is beyond 32 bits. This leads to corruption of the variables located in the __read_mostly section.</p> <p>This corruption was observed because the variable __cpu_primary_thread_mask was corrupted, causing a hang very early during boot.</p> <p>This fix prevents the corruption by avoiding the generation of instructions if they could exceed 2 instructions in length. Fortunately, insn_la_mcount is only used if the instrumented code is located outside the kernel code section, so dynamic ftrace can still be used, albeit in a more limited scope. This is still preferable to corrupting memory and/or crashing the kernel.(CVE-2025-71109)</p> <p>In the Linu…</p> <p><strong>Affected:</strong> openEuler:24.03-LTS-SP3: kernel</p> <p>The Linux Kernel, the operating system core itself. Security Fix(es):</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>parisc: Drop WARN_ON_ONCE() from flush_cache_vmap</p> <p>I have observed warning to occassionally trigger.(CVE-2025-39781)</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>MIPS: ftrace: Fix memory corruption when kernel is located beyond 32 bits</p> <p>Since commit e424054000878 (&amp;quot;MIPS: Tracing: Reduce the overhead of dynamic Function Tracer&amp;quot;), the macro UASM_i_LA_mostly has been used, and this macro can generate more than 2 instructions. At the same time, the code in ftrace assumes that no more than 2 instructions can be generated, which is why it stores them in an int[2] array. However, as previously noted, the macro UASM_i_LA_mostly (and now UASM_i_LA) causes a buffer overflow when _mcount is beyond 32 bits. This leads to corruption of the variables located in the __read_mostly section.</p> <p>This corruption was observed because the variable __cpu_primary_thread_mask was corrupted, causing a hang very early during boot.</p> <p>This fix prevents the corruption by avoiding the generation of instructions if they could exceed 2 instructions in length. Fortunately, insn_la_mcount is only used if the instrumented code is located outside the kernel code section, so dynamic ftrace can still be used, albeit in a more limited scope. This is still preferable to corrupting memory and/or crashing the kernel.(CVE-2025-71109)</p> <p>In the Linu…</p> https://cve.radiocsirt.org/vuln/oesa-2026-2676 https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-71109 <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: MIPS: ftrace: Fix memory corruption when kernel is located beyond 32 bits Since commit e424054000878 (&#34;MIPS: Tracing: Reduce the overhead of dynamic Function Tracer&#34;), the macro UASM_i_LA_mostly has been used, and this macro can generate more than 2 instructions. At the same time, the code in ftrace assumes that no more than 2 instructions can be generated, which is why it stores them in an int[2] array. However, as previously noted, the macro UASM_i_LA_mostly (and now UASM_i_LA) causes a buffer overflow when _mcount is beyond 32 bits. This leads to corruption of the variables located in the __read_mostly section. This corruption was observed because the variable __cpu_primary_thread_mask was corrupted, causing a hang very early during boot. This fix prevents the corruption by avoiding the generation of instructions if they could exceed 2 instructions in length. Fortunately, insn_la_mcount is only used if the instrumented code is located outside the kernel code section, so dynamic ftrace can still be used, albeit in a more limited scope. This is still preferable to corrupting memory and/or crashing 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: MIPS: ftrace: Fix memory corruption when kernel is located beyond 32 bits Since commit e424054000878 (&#34;MIPS: Tracing: Reduce the overhead of dynamic Function Tracer&#34;), the macro UASM_i_LA_mostly has been used, and this macro can generate more than 2 instructions. At the same time, the code in ftrace assumes that no more than 2 instructions can be generated, which is why it stores them in an int[2] array. However, as previously noted, the macro UASM_i_LA_mostly (and now UASM_i_LA) causes a buffer overflow when _mcount is beyond 32 bits. This leads to corruption of the variables located in the __read_mostly section. This corruption was observed because the variable __cpu_primary_thread_mask was corrupted, causing a hang very early during boot. This fix prevents the corruption by avoiding the generation of instructions if they could exceed 2 instructions in length. Fortunately, insn_la_mcount is only used if the instrumented code is located outside the kernel code section, so dynamic ftrace can still be used, albeit in a more limited scope. This is still preferable to corrupting memory and/or crashing the kernel.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-71109 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0119 <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-0119