https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 09 Nov 2026 17:25:16 +0000 https://db.gcve.eu/vuln/fkie_cve-2026-99075 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>rust_binder: reschedule node refcount update on thread exit</p> <p>When a thread exits via BINDER_THREAD_EXIT, its pending work items are cancelled. If a thread exits while holding a pending node refcount increment (e.g. pushed as deferred work to that thread), the refcount increment was previously dropped because Node::cancel() and NodeWrapper::cancel() were no-ops.</p> <p>Dropping the refcount update leaves the node&#39;s delivery state and count state desynchronized, and userspace will not receive the notification, which can cause the node to never be freed from the process&#39;s nodes tree when all external references are dropped.</p> <p>Fix this by implementing DeliverToRead::cancel() for Node and NodeWrapper to move the pending refcount update to the process&#39;s work queue on thread exit so another thread can deliver it to userspace.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>rust_binder: reschedule node refcount update on thread exit</p> <p>When a thread exits via BINDER_THREAD_EXIT, its pending work items are cancelled. If a thread exits while holding a pending node refcount increment (e.g. pushed as deferred work to that thread), the refcount increment was previously dropped because Node::cancel() and NodeWrapper::cancel() were no-ops.</p> <p>Dropping the refcount update leaves the node&#39;s delivery state and count state desynchronized, and userspace will not receive the notification, which can cause the node to never be freed from the process&#39;s nodes tree when all external references are dropped.</p> <p>Fix this by implementing DeliverToRead::cancel() for Node and NodeWrapper to move the pending refcount update to the process&#39;s work queue on thread exit so another thread can deliver it to userspace.</p> https://db.gcve.eu/vuln/fkie_cve-2026-99075 https://db.gcve.eu/vuln/ghsa-gxfj-h7rr-9wq9 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>rust_binder: reschedule node refcount update on thread exit</p> <p>When a thread exits via BINDER_THREAD_EXIT, its pending work items are cancelled. If a thread exits while holding a pending node refcount increment (e.g. pushed as deferred work to that thread), the refcount increment was previously dropped because Node::cancel() and NodeWrapper::cancel() were no-ops.</p> <p>Dropping the refcount update leaves the node&#39;s delivery state and count state desynchronized, and userspace will not receive the notification, which can cause the node to never be freed from the process&#39;s nodes tree when all external references are dropped.</p> <p>Fix this by implementing DeliverToRead::cancel() for Node and NodeWrapper to move the pending refcount update to the process&#39;s work queue on thread exit so another thread can deliver it to userspace.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>rust_binder: reschedule node refcount update on thread exit</p> <p>When a thread exits via BINDER_THREAD_EXIT, its pending work items are cancelled. If a thread exits while holding a pending node refcount increment (e.g. pushed as deferred work to that thread), the refcount increment was previously dropped because Node::cancel() and NodeWrapper::cancel() were no-ops.</p> <p>Dropping the refcount update leaves the node&#39;s delivery state and count state desynchronized, and userspace will not receive the notification, which can cause the node to never be freed from the process&#39;s nodes tree when all external references are dropped.</p> <p>Fix this by implementing DeliverToRead::cancel() for Node and NodeWrapper to move the pending refcount update to the process&#39;s work queue on thread exit so another thread can deliver it to userspace.</p> https://db.gcve.eu/vuln/ghsa-gxfj-h7rr-9wq9 https://db.gcve.eu/vuln/msrc_cve-2026-99075 msrc_CVE-2026-99075 https://db.gcve.eu/vuln/msrc_cve-2026-99075 https://db.gcve.eu/vuln/ubuntu-cve-2026-99075 <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 118 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: rust_binder: reschedule node refcount update on thread exit When a thread exits via BINDER_THREAD_EXIT, its pending work items are cancelled. If a thread exits while holding a pending node refcount increment (e.g. pushed as deferred work to that thread), the refcount increment was previously dropped because Node::cancel() and NodeWrapper::cancel() were no-ops. Dropping the refcount update leaves the node&#39;s delivery state and count state desynchronized, and userspace will not receive the notification, which can cause the node to never be freed from the process&#39;s nodes tree when all external references are dropped. Fix this by implementing DeliverToRead::cancel() for Node and NodeWrapper to move the pending refcount update to the process&#39;s work queue on thread exit so another thread can deliver it to userspace.</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 118 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: rust_binder: reschedule node refcount update on thread exit When a thread exits via BINDER_THREAD_EXIT, its pending work items are cancelled. If a thread exits while holding a pending node refcount increment (e.g. pushed as deferred work to that thread), the refcount increment was previously dropped because Node::cancel() and NodeWrapper::cancel() were no-ops. Dropping the refcount update leaves the node&#39;s delivery state and count state desynchronized, and userspace will not receive the notification, which can cause the node to never be freed from the process&#39;s nodes tree when all external references are dropped. Fix this by implementing DeliverToRead::cancel() for Node and NodeWrapper to move the pending refcount update to the process&#39;s work queue on thread exit so another thread can deliver it to userspace.</p> https://db.gcve.eu/vuln/ubuntu-cve-2026-99075 https://db.gcve.eu/vuln/wid-sec-w-2026-4152 <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-4152