https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 19:53:15 +0000 https://cve.radiocsirt.org/vuln/bell-cve-2026-90255 <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-90255 https://cve.radiocsirt.org/vuln/certfr-2026-avi-1253 certfr-2026-avi-1253 https://cve.radiocsirt.org/vuln/certfr-2026-avi-1253 https://cve.radiocsirt.org/vuln/euvd-2026-372114 EUVD-2026-372114 https://cve.radiocsirt.org/vuln/euvd-2026-372114 https://cve.radiocsirt.org/vuln/fkie_cve-2026-90255 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>Bluetooth: hci_conn: fix the SCO setup context lifetime</p> <p>hci_setup_sync() queues a conn_handle_t with a NULL destroy callback, so the context is only freed if hci_enhanced_setup_sync() actually runs. An entry that is cancelled instead is leaked, as _hci_cmd_sync_cancel_entry() does not release entry-&gt;data when there is no destroy callback, and hci_cmd_sync_clear() cancels every pending entry when the controller is unregistered.</p> <p>The context also stores a bare hci_conn pointer, so the connection can be freed while the work is queued. The dequeue in hci_conn_del() does not cover it either, as it matches on entry-&gt;data == conn and entry-&gt;data is the wrapper here. Same problem as commit 2f5d635ad590 (&#34;Bluetooth: hci_sync: hold conn in hci_connect_acl/le_sync() callbacks&#34;).</p> <p>Hold the connection and release both from a destroy callback. The submission failure path drops both, since hci_cmd_sync_submit() does not call the destroy callback when it fails to queue.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>Bluetooth: hci_conn: fix the SCO setup context lifetime</p> <p>hci_setup_sync() queues a conn_handle_t with a NULL destroy callback, so the context is only freed if hci_enhanced_setup_sync() actually runs. An entry that is cancelled instead is leaked, as _hci_cmd_sync_cancel_entry() does not release entry-&gt;data when there is no destroy callback, and hci_cmd_sync_clear() cancels every pending entry when the controller is unregistered.</p> <p>The context also stores a bare hci_conn pointer, so the connection can be freed while the work is queued. The dequeue in hci_conn_del() does not cover it either, as it matches on entry-&gt;data == conn and entry-&gt;data is the wrapper here. Same problem as commit 2f5d635ad590 (&#34;Bluetooth: hci_sync: hold conn in hci_connect_acl/le_sync() callbacks&#34;).</p> <p>Hold the connection and release both from a destroy callback. The submission failure path drops both, since hci_cmd_sync_submit() does not call the destroy callback when it fails to queue.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-90255 https://cve.radiocsirt.org/vuln/ghsa-wjxp-4hww-crmx <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>Bluetooth: hci_conn: fix the SCO setup context lifetime</p> <p>hci_setup_sync() queues a conn_handle_t with a NULL destroy callback, so the context is only freed if hci_enhanced_setup_sync() actually runs. An entry that is cancelled instead is leaked, as _hci_cmd_sync_cancel_entry() does not release entry-&gt;data when there is no destroy callback, and hci_cmd_sync_clear() cancels every pending entry when the controller is unregistered.</p> <p>The context also stores a bare hci_conn pointer, so the connection can be freed while the work is queued. The dequeue in hci_conn_del() does not cover it either, as it matches on entry-&gt;data == conn and entry-&gt;data is the wrapper here. Same problem as commit 2f5d635ad590 (&#34;Bluetooth: hci_sync: hold conn in hci_connect_acl/le_sync() callbacks&#34;).</p> <p>Hold the connection and release both from a destroy callback. The submission failure path drops both, since hci_cmd_sync_submit() does not call the destroy callback when it fails to queue.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>Bluetooth: hci_conn: fix the SCO setup context lifetime</p> <p>hci_setup_sync() queues a conn_handle_t with a NULL destroy callback, so the context is only freed if hci_enhanced_setup_sync() actually runs. An entry that is cancelled instead is leaked, as _hci_cmd_sync_cancel_entry() does not release entry-&gt;data when there is no destroy callback, and hci_cmd_sync_clear() cancels every pending entry when the controller is unregistered.</p> <p>The context also stores a bare hci_conn pointer, so the connection can be freed while the work is queued. The dequeue in hci_conn_del() does not cover it either, as it matches on entry-&gt;data == conn and entry-&gt;data is the wrapper here. Same problem as commit 2f5d635ad590 (&#34;Bluetooth: hci_sync: hold conn in hci_connect_acl/le_sync() callbacks&#34;).</p> <p>Hold the connection and release both from a destroy callback. The submission failure path drops both, since hci_cmd_sync_submit() does not call the destroy callback when it fails to queue.</p> https://cve.radiocsirt.org/vuln/ghsa-wjxp-4hww-crmx https://cve.radiocsirt.org/vuln/msrc_cve-2026-90255 msrc_CVE-2026-90255 https://cve.radiocsirt.org/vuln/msrc_cve-2026-90255 https://cve.radiocsirt.org/vuln/opensuse-su-2026:11880-1 <p>kernel-devel-7.2.7-1.1 on GA media</p> <p>kernel-devel-7.2.7-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2026:11880-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-90255 <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 154 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_conn: fix the SCO setup context lifetime hci_setup_sync() queues a conn_handle_t with a NULL destroy callback, so the context is only freed if hci_enhanced_setup_sync() actually runs. An entry that is cancelled instead is leaked, as _hci_cmd_sync_cancel_entry() does not release entry-&gt;data when there is no destroy callback, and hci_cmd_sync_clear() cancels every pending entry when the controller is unregistered. The context also stores a bare hci_conn pointer, so the connection can be freed while the work is queued. The dequeue in hci_conn_del() does not cover it either, as it matches on entry-&gt;data == conn and entry-&gt;data is the wrapper here. Same problem as commit 2f5d635ad590 (&#34;Bluetooth: hci_sync: hold conn in hci_connect_acl/le_sync() callbacks&#34;). Hold the connection and release both from a destroy callback. The submission failure path drops both, since hci_cmd_sync_submit() does not call the destroy callback when it fails to queue.</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 154 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_conn: fix the SCO setup context lifetime hci_setup_sync() queues a conn_handle_t with a NULL destroy callback, so the context is only freed if hci_enhanced_setup_sync() actually runs. An entry that is cancelled instead is leaked, as _hci_cmd_sync_cancel_entry() does not release entry-&gt;data when there is no destroy callback, and hci_cmd_sync_clear() cancels every pending entry when the controller is unregistered. The context also stores a bare hci_conn pointer, so the connection can be freed while the work is queued. The dequeue in hci_conn_del() does not cover it either, as it matches on entry-&gt;data == conn and entry-&gt;data is the wrapper here. Same problem as commit 2f5d635ad590 (&#34;Bluetooth: hci_sync: hold conn in hci_connect_acl/le_sync() callbacks&#34;). Hold the connection and release both from a destroy callback. The submission failure path drops both, since hci_cmd_sync_submit() does not call the destroy callback when it fails to queue.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-90255 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3444 <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel möglicherweise ausnutzen, um Berechtigungen zu erweitern, Sicherheitsmaßnahmen zu umgehen, Daten offenzulegen oder zu manipulieren, den Speicher zu beschädigen, Denial-of-Service-Zustände zu verursachen oder andere, nicht näher spezifizierte Angriffe durchzuführen.</p> <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel möglicherweise ausnutzen, um Berechtigungen zu erweitern, Sicherheitsmaßnahmen zu umgehen, Daten offenzulegen oder zu manipulieren, den Speicher zu beschädigen, Denial-of-Service-Zustände zu verursachen oder andere, nicht näher spezifizierte Angriffe durchzuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3444