https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 03 Nov 2026 18:46:55 +0000 https://db.gcve.eu/vuln/fkie_cve-2026-98690 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>thunderbolt: Fix domain reference leak when DPRX read is canceled</p> <p>tb_tunnel_one_dp() takes a domain reference which is only dropped once tb_dp_tunnel_active() has run on the work queue. If that work is cancelled that reference is leaked. Since commit f5cc545f5969 (&#34;thunderbolt: Wait for tb_domain_release() to complete when driver is removed&#34;) instead of just leaking memory this now also blocks in the completion wait forever when unbinding the driver.</p> <p>This can be triggered whenever a DP tunnel is torn down before the DPRX read has completed, e.g. by unplugging within the timeout, and then unbinding the driver.</p> <p>That reference only exists to keep the domain around while the DPRX work is scheduled so let the work itself own it: take it in tb_dp_dprx_start() and drop it in both places that end the work. Get/put are then paired inside the same file and it doesn&#39;t matter anymore if the callback ever runs.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>thunderbolt: Fix domain reference leak when DPRX read is canceled</p> <p>tb_tunnel_one_dp() takes a domain reference which is only dropped once tb_dp_tunnel_active() has run on the work queue. If that work is cancelled that reference is leaked. Since commit f5cc545f5969 (&#34;thunderbolt: Wait for tb_domain_release() to complete when driver is removed&#34;) instead of just leaking memory this now also blocks in the completion wait forever when unbinding the driver.</p> <p>This can be triggered whenever a DP tunnel is torn down before the DPRX read has completed, e.g. by unplugging within the timeout, and then unbinding the driver.</p> <p>That reference only exists to keep the domain around while the DPRX work is scheduled so let the work itself own it: take it in tb_dp_dprx_start() and drop it in both places that end the work. Get/put are then paired inside the same file and it doesn&#39;t matter anymore if the callback ever runs.</p> https://db.gcve.eu/vuln/fkie_cve-2026-98690 https://db.gcve.eu/vuln/ghsa-wqqh-3g59-38q4 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>thunderbolt: Fix domain reference leak when DPRX read is canceled</p> <p>tb_tunnel_one_dp() takes a domain reference which is only dropped once tb_dp_tunnel_active() has run on the work queue. If that work is cancelled that reference is leaked. Since commit f5cc545f5969 (&#34;thunderbolt: Wait for tb_domain_release() to complete when driver is removed&#34;) instead of just leaking memory this now also blocks in the completion wait forever when unbinding the driver.</p> <p>This can be triggered whenever a DP tunnel is torn down before the DPRX read has completed, e.g. by unplugging within the timeout, and then unbinding the driver.</p> <p>That reference only exists to keep the domain around while the DPRX work is scheduled so let the work itself own it: take it in tb_dp_dprx_start() and drop it in both places that end the work. Get/put are then paired inside the same file and it doesn&#39;t matter anymore if the callback ever runs.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>thunderbolt: Fix domain reference leak when DPRX read is canceled</p> <p>tb_tunnel_one_dp() takes a domain reference which is only dropped once tb_dp_tunnel_active() has run on the work queue. If that work is cancelled that reference is leaked. Since commit f5cc545f5969 (&#34;thunderbolt: Wait for tb_domain_release() to complete when driver is removed&#34;) instead of just leaking memory this now also blocks in the completion wait forever when unbinding the driver.</p> <p>This can be triggered whenever a DP tunnel is torn down before the DPRX read has completed, e.g. by unplugging within the timeout, and then unbinding the driver.</p> <p>That reference only exists to keep the domain around while the DPRX work is scheduled so let the work itself own it: take it in tb_dp_dprx_start() and drop it in both places that end the work. Get/put are then paired inside the same file and it doesn&#39;t matter anymore if the callback ever runs.</p> https://db.gcve.eu/vuln/ghsa-wqqh-3g59-38q4 https://db.gcve.eu/vuln/msrc_cve-2026-98690 msrc_CVE-2026-98690 https://db.gcve.eu/vuln/msrc_cve-2026-98690 https://db.gcve.eu/vuln/ubuntu-cve-2026-98690 <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 120 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: thunderbolt: Fix domain reference leak when DPRX read is canceled tb_tunnel_one_dp() takes a domain reference which is only dropped once tb_dp_tunnel_active() has run on the work queue. If that work is cancelled that reference is leaked. Since commit f5cc545f5969 (&#34;thunderbolt: Wait for tb_domain_release() to complete when driver is removed&#34;) instead of just leaking memory this now also blocks in the completion wait forever when unbinding the driver. This can be triggered whenever a DP tunnel is torn down before the DPRX read has completed, e.g. by unplugging within the timeout, and then unbinding the driver. That reference only exists to keep the domain around while the DPRX work is scheduled so let the work itself own it: take it in tb_dp_dprx_start() and drop it in both places that end the work. Get/put are then paired inside the same file and it doesn&#39;t matter anymore if the callback ever runs.</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 120 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: thunderbolt: Fix domain reference leak when DPRX read is canceled tb_tunnel_one_dp() takes a domain reference which is only dropped once tb_dp_tunnel_active() has run on the work queue. If that work is cancelled that reference is leaked. Since commit f5cc545f5969 (&#34;thunderbolt: Wait for tb_domain_release() to complete when driver is removed&#34;) instead of just leaking memory this now also blocks in the completion wait forever when unbinding the driver. This can be triggered whenever a DP tunnel is torn down before the DPRX read has completed, e.g. by unplugging within the timeout, and then unbinding the driver. That reference only exists to keep the domain around while the DPRX work is scheduled so let the work itself own it: take it in tb_dp_dprx_start() and drop it in both places that end the work. Get/put are then paired inside the same file and it doesn&#39;t matter anymore if the callback ever runs.</p> https://db.gcve.eu/vuln/ubuntu-cve-2026-98690 https://db.gcve.eu/vuln/wid-sec-w-2026-4019 <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen.</p> <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen.</p> https://db.gcve.eu/vuln/wid-sec-w-2026-4019