<?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://vulnerability.circl.lu</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>Tue, 29 Sep 2026 12:48:34 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-80777 — futex/pi: Plug private futex exec() race</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-80777</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;futex/pi: Plug private futex exec() race&lt;/p&gt;
&lt;p&gt;The check for private futexes whether the waiter&amp;#39;s mm, which is stored in
the futex_key and copied into the pi_state, is the same as the owner&amp;#39;s mm
is not sufficient for exec(). exec() has a gap where the mm check fails to
give the correct answer:&lt;/p&gt;
&lt;p&gt;exec()
  ...
    exec_release_mm()
      futex_exec_release()
        tsk::futex::exit_state = EXITING;
        cleanup_robust_list();
1)      tsk::futex::exit_state = OK;
    ...
    old_mm = tsk::mm;
2)  tsk::mm = -&amp;gt;mm;&lt;/p&gt;
&lt;p&gt;Between #1 and #2 the check for the mm is wrong as that mm is about to be
swapped out and eventually freed.&lt;/p&gt;
&lt;p&gt;Plug this gap by:&lt;/p&gt;
&lt;p&gt;1) Setting tsk::futex::exit_state to FUTEX_STATE_DEAD in
     futex_exec_release()&lt;/p&gt;
&lt;p&gt;2) Setting tsk::futex::exit_state to FUTEX_STATE_OK after
     the mm has been switched.&lt;/p&gt;
&lt;p&gt;From a futex point of view the task is dead after it finished the robust
list cleanup up to the point where it sets the state to OK again.&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;futex/pi: Plug private futex exec() race&lt;/p&gt;
&lt;p&gt;The check for private futexes whether the waiter&amp;#39;s mm, which is stored in
the futex_key and copied into the pi_state, is the same as the owner&amp;#39;s mm
is not sufficient for exec(). exec() has a gap where the mm check fails to
give the correct answer:&lt;/p&gt;
&lt;p&gt;exec()
  ...
    exec_release_mm()
      futex_exec_release()
        tsk::futex::exit_state = EXITING;
        cleanup_robust_list();
1)      tsk::futex::exit_state = OK;
    ...
    old_mm = tsk::mm;
2)  tsk::mm = -&amp;gt;mm;&lt;/p&gt;
&lt;p&gt;Between #1 and #2 the check for the mm is wrong as that mm is about to be
swapped out and eventually freed.&lt;/p&gt;
&lt;p&gt;Plug this gap by:&lt;/p&gt;
&lt;p&gt;1) Setting tsk::futex::exit_state to FUTEX_STATE_DEAD in
     futex_exec_release()&lt;/p&gt;
&lt;p&gt;2) Setting tsk::futex::exit_state to FUTEX_STATE_OK after
     the mm has been switched.&lt;/p&gt;
&lt;p&gt;From a futex point of view the task is dead after it finished the robust
list cleanup up to the point where it sets the state to OK again.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-80777</guid>
    </item>
  </channel>
</rss>
