<?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>Wed, 30 Sep 2026 17:34:08 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-93164 — uprobes/x86: Move optimized uprobe from nop5 to nop10</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-93164</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;uprobes/x86: Move optimized uprobe from nop5 to nop10&lt;/p&gt;
&lt;p&gt;Andrii reported an issue with optimized uprobes [1] that can clobber
redzone area with call instruction storing return address on stack
where user code may keep temporary data without adjusting rsp.&lt;/p&gt;
&lt;p&gt;Fixing this by moving the optimized uprobes on top of 10-bytes nop
instruction, so we can squeeze another instruction to escape the
redzone area before doing the call, like:&lt;/p&gt;
&lt;p&gt;lea -0x80(%rsp), %rsp
  call tramp&lt;/p&gt;
&lt;p&gt;Note the lea instruction is used to adjust the rsp register without
changing the flags.&lt;/p&gt;
&lt;p&gt;We use nop10 and following transformation to optimized instructions
above and back as suggested by Peterz [2].&lt;/p&gt;
&lt;p&gt;Optimize path (int3_update_optimize):&lt;/p&gt;
&lt;p&gt;1) Initial state after set_swbp() installed the uprobe:
      cc 2e 0f 1f 84 00 00 00 00 00&lt;/p&gt;
&lt;p&gt;From offset 0 this is INT3 followed by the tail of the original
     10-byte NOP.&lt;/p&gt;
&lt;p&gt;After a previous unoptimization bytes 5..9 may still contain the
     old call instruction, which remains valid for threads already there.&lt;/p&gt;
&lt;p&gt;2) Rewrite the LEA tail and call displacement:
      cc [8d 64 24 80 e8 d0 d1 d2 d3]&lt;/p&gt;
&lt;p&gt;From offset 0 this traps on the uprobe INT3.  Bytes 1..9 are not
     executable entry points while byte 0 is trapped.&lt;/p&gt;
&lt;p&gt;3) Publish the first LEA byte:
      [48] 8d 64 24 80 e8 d0 d1 d2 d3&lt;/p&gt;
&lt;p&gt;From offset 0 this is:
        lea -0x80(%rsp), %rsp
        call &amp;lt;uprobe-trampoline&amp;gt;&lt;/p&gt;
&lt;p&gt;Unoptimize path (…&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;uprobes/x86: Move optimized uprobe from nop5 to nop10&lt;/p&gt;
&lt;p&gt;Andrii reported an issue with optimized uprobes [1] that can clobber
redzone area with call instruction storing return address on stack
where user code may keep temporary data without adjusting rsp.&lt;/p&gt;
&lt;p&gt;Fixing this by moving the optimized uprobes on top of 10-bytes nop
instruction, so we can squeeze another instruction to escape the
redzone area before doing the call, like:&lt;/p&gt;
&lt;p&gt;lea -0x80(%rsp), %rsp
  call tramp&lt;/p&gt;
&lt;p&gt;Note the lea instruction is used to adjust the rsp register without
changing the flags.&lt;/p&gt;
&lt;p&gt;We use nop10 and following transformation to optimized instructions
above and back as suggested by Peterz [2].&lt;/p&gt;
&lt;p&gt;Optimize path (int3_update_optimize):&lt;/p&gt;
&lt;p&gt;1) Initial state after set_swbp() installed the uprobe:
      cc 2e 0f 1f 84 00 00 00 00 00&lt;/p&gt;
&lt;p&gt;From offset 0 this is INT3 followed by the tail of the original
     10-byte NOP.&lt;/p&gt;
&lt;p&gt;After a previous unoptimization bytes 5..9 may still contain the
     old call instruction, which remains valid for threads already there.&lt;/p&gt;
&lt;p&gt;2) Rewrite the LEA tail and call displacement:
      cc [8d 64 24 80 e8 d0 d1 d2 d3]&lt;/p&gt;
&lt;p&gt;From offset 0 this traps on the uprobe INT3.  Bytes 1..9 are not
     executable entry points while byte 0 is trapped.&lt;/p&gt;
&lt;p&gt;3) Publish the first LEA byte:
      [48] 8d 64 24 80 e8 d0 d1 d2 d3&lt;/p&gt;
&lt;p&gt;From offset 0 this is:
        lea -0x80(%rsp), %rsp
        call &amp;lt;uprobe-trampoline&amp;gt;&lt;/p&gt;
&lt;p&gt;Unoptimize path (…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-93164</guid>
    </item>
  </channel>
</rss>
