https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 16:20:29 +0000 https://cve.radiocsirt.org/vuln/bell-cve-2026-74471 <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-74471 https://cve.radiocsirt.org/vuln/certfr-2026-avi-1090 certfr-2026-avi-1090 https://cve.radiocsirt.org/vuln/certfr-2026-avi-1090 https://cve.radiocsirt.org/vuln/euvd-2026-356386 EUVD-2026-356386 https://cve.radiocsirt.org/vuln/euvd-2026-356386 https://cve.radiocsirt.org/vuln/fkie_cve-2026-74471 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>tracing: Check return value of __register_event() in trace_module_add_events()</p> <p>trace_module_add_events() ignores the return value of __register_event() and unconditionally calls __add_event_to_tracers() for each event.</p> <p>If __register_event() fails (for example, if event_init() fails), the trace_event_call is not added to ftrace_events list, but __add_event_to_tracers() still creates a trace_event_file pointing to it. If module loading subsequently fails and module memory is freed, tracing state retains a stale trace_event_call pointer in trace_event_file, leading to a use-after-free when tracefs or tracing subsystem operations are later executed.</p> <p>Fix this by checking the return value of __register_event() and only calling __add_event_to_tracers() if event registration succeeded.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>tracing: Check return value of __register_event() in trace_module_add_events()</p> <p>trace_module_add_events() ignores the return value of __register_event() and unconditionally calls __add_event_to_tracers() for each event.</p> <p>If __register_event() fails (for example, if event_init() fails), the trace_event_call is not added to ftrace_events list, but __add_event_to_tracers() still creates a trace_event_file pointing to it. If module loading subsequently fails and module memory is freed, tracing state retains a stale trace_event_call pointer in trace_event_file, leading to a use-after-free when tracefs or tracing subsystem operations are later executed.</p> <p>Fix this by checking the return value of __register_event() and only calling __add_event_to_tracers() if event registration succeeded.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-74471 https://cve.radiocsirt.org/vuln/ghsa-437h-q69x-6qrx <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>tracing: Check return value of __register_event() in trace_module_add_events()</p> <p>trace_module_add_events() ignores the return value of __register_event() and unconditionally calls __add_event_to_tracers() for each event.</p> <p>If __register_event() fails (for example, if event_init() fails), the trace_event_call is not added to ftrace_events list, but __add_event_to_tracers() still creates a trace_event_file pointing to it. If module loading subsequently fails and module memory is freed, tracing state retains a stale trace_event_call pointer in trace_event_file, leading to a use-after-free when tracefs or tracing subsystem operations are later executed.</p> <p>Fix this by checking the return value of __register_event() and only calling __add_event_to_tracers() if event registration succeeded.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>tracing: Check return value of __register_event() in trace_module_add_events()</p> <p>trace_module_add_events() ignores the return value of __register_event() and unconditionally calls __add_event_to_tracers() for each event.</p> <p>If __register_event() fails (for example, if event_init() fails), the trace_event_call is not added to ftrace_events list, but __add_event_to_tracers() still creates a trace_event_file pointing to it. If module loading subsequently fails and module memory is freed, tracing state retains a stale trace_event_call pointer in trace_event_file, leading to a use-after-free when tracefs or tracing subsystem operations are later executed.</p> <p>Fix this by checking the return value of __register_event() and only calling __add_event_to_tracers() if event registration succeeded.</p> https://cve.radiocsirt.org/vuln/ghsa-437h-q69x-6qrx https://cve.radiocsirt.org/vuln/msrc_cve-2026-74471 msrc_CVE-2026-74471 https://cve.radiocsirt.org/vuln/msrc_cve-2026-74471 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-74471 <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: tracing: Check return value of __register_event() in trace_module_add_events() trace_module_add_events() ignores the return value of __register_event() and unconditionally calls __add_event_to_tracers() for each event. If __register_event() fails (for example, if event_init() fails), the trace_event_call is not added to ftrace_events list, but __add_event_to_tracers() still creates a trace_event_file pointing to it. If module loading subsequently fails and module memory is freed, tracing state retains a stale trace_event_call pointer in trace_event_file, leading to a use-after-free when tracefs or tracing subsystem operations are later executed. Fix this by checking the return value of __register_event() and only calling __add_event_to_tracers() if event registration succeeded.</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: tracing: Check return value of __register_event() in trace_module_add_events() trace_module_add_events() ignores the return value of __register_event() and unconditionally calls __add_event_to_tracers() for each event. If __register_event() fails (for example, if event_init() fails), the trace_event_call is not added to ftrace_events list, but __add_event_to_tracers() still creates a trace_event_file pointing to it. If module loading subsequently fails and module memory is freed, tracing state retains a stale trace_event_call pointer in trace_event_file, leading to a use-after-free when tracefs or tracing subsystem operations are later executed. Fix this by checking the return value of __register_event() and only calling __add_event_to_tracers() if event registration succeeded.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-74471 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2852 <p>Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um root Rechte zu erlangen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.</p> <p>Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um root Rechte zu erlangen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2852