https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 20:10:27 +0000 https://cve.radiocsirt.org/vuln/bell-cve-2026-68146 <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-68146 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-357840 EUVD-2026-357840 https://cve.radiocsirt.org/vuln/euvd-2026-357840 https://cve.radiocsirt.org/vuln/fkie_cve-2026-68146 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ftrace: Add global mutex to serialize trace_parser access</p> <p>In ftrace, the trace_parser structure is allocated and initialized when a trace file is opened, and is subsequently used across write and release handlers to parse user input.</p> <p>The affected handler paths and their specific functions are: - Open paths: ftrace_regex_open(), ftrace_graph_open() - Write paths: ftrace_regex_write(), ftrace_graph_write() - Release paths: ftrace_regex_release(), ftrace_graph_release()</p> <p>If userspace opens a trace file descriptor and shares it across multiple threads, concurrent write calls will race on the parser&#39;s internal state, specifically the &#39;idx&#39;, &#39;cont&#39;, and &#39;buffer&#39; fields, leading to corrupted input or undefined behavior.</p> <p>Fix this by adding a global mutex, parser_lock, to serialize all access to trace_parser across write and release paths, preventing concurrent corruption of parser state.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ftrace: Add global mutex to serialize trace_parser access</p> <p>In ftrace, the trace_parser structure is allocated and initialized when a trace file is opened, and is subsequently used across write and release handlers to parse user input.</p> <p>The affected handler paths and their specific functions are: - Open paths: ftrace_regex_open(), ftrace_graph_open() - Write paths: ftrace_regex_write(), ftrace_graph_write() - Release paths: ftrace_regex_release(), ftrace_graph_release()</p> <p>If userspace opens a trace file descriptor and shares it across multiple threads, concurrent write calls will race on the parser&#39;s internal state, specifically the &#39;idx&#39;, &#39;cont&#39;, and &#39;buffer&#39; fields, leading to corrupted input or undefined behavior.</p> <p>Fix this by adding a global mutex, parser_lock, to serialize all access to trace_parser across write and release paths, preventing concurrent corruption of parser state.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-68146 https://cve.radiocsirt.org/vuln/ghsa-vcpv-vm68-v468 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ftrace: Add global mutex to serialize trace_parser access</p> <p>In ftrace, the trace_parser structure is allocated and initialized when a trace file is opened, and is subsequently used across write and release handlers to parse user input.</p> <p>The affected handler paths and their specific functions are: - Open paths: ftrace_regex_open(), ftrace_graph_open() - Write paths: ftrace_regex_write(), ftrace_graph_write() - Release paths: ftrace_regex_release(), ftrace_graph_release()</p> <p>If userspace opens a trace file descriptor and shares it across multiple threads, concurrent write calls will race on the parser&#39;s internal state, specifically the &#39;idx&#39;, &#39;cont&#39;, and &#39;buffer&#39; fields, leading to corrupted input or undefined behavior.</p> <p>Fix this by adding a global mutex, parser_lock, to serialize all access to trace_parser across write and release paths, preventing concurrent corruption of parser state.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ftrace: Add global mutex to serialize trace_parser access</p> <p>In ftrace, the trace_parser structure is allocated and initialized when a trace file is opened, and is subsequently used across write and release handlers to parse user input.</p> <p>The affected handler paths and their specific functions are: - Open paths: ftrace_regex_open(), ftrace_graph_open() - Write paths: ftrace_regex_write(), ftrace_graph_write() - Release paths: ftrace_regex_release(), ftrace_graph_release()</p> <p>If userspace opens a trace file descriptor and shares it across multiple threads, concurrent write calls will race on the parser&#39;s internal state, specifically the &#39;idx&#39;, &#39;cont&#39;, and &#39;buffer&#39; fields, leading to corrupted input or undefined behavior.</p> <p>Fix this by adding a global mutex, parser_lock, to serialize all access to trace_parser across write and release paths, preventing concurrent corruption of parser state.</p> https://cve.radiocsirt.org/vuln/ghsa-vcpv-vm68-v468 https://cve.radiocsirt.org/vuln/msrc_cve-2026-68146 msrc_CVE-2026-68146 https://cve.radiocsirt.org/vuln/msrc_cve-2026-68146 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-68146 <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 246 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: ftrace: Add global mutex to serialize trace_parser access In ftrace, the trace_parser structure is allocated and initialized when a trace file is opened, and is subsequently used across write and release handlers to parse user input. The affected handler paths and their specific functions are: - Open paths: ftrace_regex_open(), ftrace_graph_open() - Write paths: ftrace_regex_write(), ftrace_graph_write() - Release paths: ftrace_regex_release(), ftrace_graph_release() If userspace opens a trace file descriptor and shares it across multiple threads, concurrent write calls will race on the parser&#39;s internal state, specifically the &#39;idx&#39;, &#39;cont&#39;, and &#39;buffer&#39; fields, leading to corrupted input or undefined behavior. Fix this by adding a global mutex, parser_lock, to serialize all access to trace_parser across write and release paths, preventing concurrent corruption of parser state.</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 246 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: ftrace: Add global mutex to serialize trace_parser access In ftrace, the trace_parser structure is allocated and initialized when a trace file is opened, and is subsequently used across write and release handlers to parse user input. The affected handler paths and their specific functions are: - Open paths: ftrace_regex_open(), ftrace_graph_open() - Write paths: ftrace_regex_write(), ftrace_graph_write() - Release paths: ftrace_regex_release(), ftrace_graph_release() If userspace opens a trace file descriptor and shares it across multiple threads, concurrent write calls will race on the parser&#39;s internal state, specifically the &#39;idx&#39;, &#39;cont&#39;, and &#39;buffer&#39; fields, leading to corrupted input or undefined behavior. Fix this by adding a global mutex, parser_lock, to serialize all access to trace_parser across write and release paths, preventing concurrent corruption of parser state.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-68146 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