<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Mon, 09 Nov 2026 17:59:14 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-99075 — rust_binder: reschedule node refcount update on thread exit</title>
      <link>https://db.gcve.eu/vuln/cve-2026-99075</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;rust_binder: reschedule node refcount update on thread exit&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;Dropping the refcount update leaves the node&amp;#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&amp;#39;s nodes tree
when all external references are dropped.&lt;/p&gt;
&lt;p&gt;Fix this by implementing DeliverToRead::cancel() for Node and NodeWrapper
to move the pending refcount update to the process&amp;#39;s work queue on thread
exit so another thread can deliver it to userspace.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;rust_binder: reschedule node refcount update on thread exit&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;Dropping the refcount update leaves the node&amp;#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&amp;#39;s nodes tree
when all external references are dropped.&lt;/p&gt;
&lt;p&gt;Fix this by implementing DeliverToRead::cancel() for Node and NodeWrapper
to move the pending refcount update to the process&amp;#39;s work queue on thread
exit so another thread can deliver it to userspace.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-99075</guid>
    </item>
  </channel>
</rss>
