https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 22:45:35 +0000 https://cve.radiocsirt.org/vuln/bell-cve-2026-68185 <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-2026-68185 https://cve.radiocsirt.org/vuln/certfr-2026-avi-1069 certfr-2026-avi-1069 https://cve.radiocsirt.org/vuln/certfr-2026-avi-1069 https://cve.radiocsirt.org/vuln/euvd-2026-354813 EUVD-2026-354813 https://cve.radiocsirt.org/vuln/euvd-2026-354813 https://cve.radiocsirt.org/vuln/fkie_cve-2026-68185 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>LoongArch: Move jump_label_init() before parse_early_param()</p> <p>When enabling both CONFIG_MEM_ALLOC_PROFILING=y and CONFIG_MEM_ALLOC_PROFILING_ENABLED_BY_DEFAULT=y, then diabling memory profiling by adding the boot parameter &#39;sysctl.vm.mem_profiling=0&#39; will cause the kernel failed to boot.</p> <p>After analysis, this is because jump_label_init() must be called before parse_early_param(), the early param handlers may modify static keys by static_branch_enable/disable().</p> <p>Fix this by moving jump_label_init() to before parse_early_param(). The solution is similar to other architectures.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>LoongArch: Move jump_label_init() before parse_early_param()</p> <p>When enabling both CONFIG_MEM_ALLOC_PROFILING=y and CONFIG_MEM_ALLOC_PROFILING_ENABLED_BY_DEFAULT=y, then diabling memory profiling by adding the boot parameter &#39;sysctl.vm.mem_profiling=0&#39; will cause the kernel failed to boot.</p> <p>After analysis, this is because jump_label_init() must be called before parse_early_param(), the early param handlers may modify static keys by static_branch_enable/disable().</p> <p>Fix this by moving jump_label_init() to before parse_early_param(). The solution is similar to other architectures.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-68185 https://cve.radiocsirt.org/vuln/ghsa-pcxf-938w-xxq5 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>LoongArch: Move jump_label_init() before parse_early_param()</p> <p>When enabling both CONFIG_MEM_ALLOC_PROFILING=y and CONFIG_MEM_ALLOC_PROFILING_ENABLED_BY_DEFAULT=y, then diabling memory profiling by adding the boot parameter &#39;sysctl.vm.mem_profiling=0&#39; will cause the kernel failed to boot.</p> <p>After analysis, this is because jump_label_init() must be called before parse_early_param(), the early param handlers may modify static keys by static_branch_enable/disable().</p> <p>Fix this by moving jump_label_init() to before parse_early_param(). The solution is similar to other architectures.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>LoongArch: Move jump_label_init() before parse_early_param()</p> <p>When enabling both CONFIG_MEM_ALLOC_PROFILING=y and CONFIG_MEM_ALLOC_PROFILING_ENABLED_BY_DEFAULT=y, then diabling memory profiling by adding the boot parameter &#39;sysctl.vm.mem_profiling=0&#39; will cause the kernel failed to boot.</p> <p>After analysis, this is because jump_label_init() must be called before parse_early_param(), the early param handlers may modify static keys by static_branch_enable/disable().</p> <p>Fix this by moving jump_label_init() to before parse_early_param(). The solution is similar to other architectures.</p> https://cve.radiocsirt.org/vuln/ghsa-pcxf-938w-xxq5 https://cve.radiocsirt.org/vuln/msrc_cve-2026-68185 msrc_CVE-2026-68185 https://cve.radiocsirt.org/vuln/msrc_cve-2026-68185 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-68185 <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 94 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: LoongArch: Move jump_label_init() before parse_early_param() When enabling both CONFIG_MEM_ALLOC_PROFILING=y and CONFIG_MEM_ALLOC_PROFILING_ENABLED_BY_DEFAULT=y, then diabling memory profiling by adding the boot parameter &#39;sysctl.vm.mem_profiling=0&#39; will cause the kernel failed to boot. After analysis, this is because jump_label_init() must be called before parse_early_param(), the early param handlers may modify static keys by static_branch_enable/disable(). Fix this by moving jump_label_init() to before parse_early_param(). The solution is similar to other architectures.</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 94 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: LoongArch: Move jump_label_init() before parse_early_param() When enabling both CONFIG_MEM_ALLOC_PROFILING=y and CONFIG_MEM_ALLOC_PROFILING_ENABLED_BY_DEFAULT=y, then diabling memory profiling by adding the boot parameter &#39;sysctl.vm.mem_profiling=0&#39; will cause the kernel failed to boot. After analysis, this is because jump_label_init() must be called before parse_early_param(), the early param handlers may modify static keys by static_branch_enable/disable(). Fix this by moving jump_label_init() to before parse_early_param(). The solution is similar to other architectures.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-68185 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2730 <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, darunter möglicherweise die Ausführung von beliebigem Code, die Ausweitung von Berechtigungen, die Offenlegung von Informationen, die Manipulation von Daten oder Denial-of-Service-Zustände.</p> <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, darunter möglicherweise die Ausführung von beliebigem Code, die Ausweitung von Berechtigungen, die Offenlegung von Informationen, die Manipulation von Daten oder Denial-of-Service-Zustände.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2730