<?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 03:11:24 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-53642 — x86: fix clear_user_rep_good() exception handling annotation</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2023-53642</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;x86: fix clear_user_rep_good() exception handling annotation&lt;/p&gt;
&lt;p&gt;This code no longer exists in mainline, because it was removed in
commit d2c95f9d6802 (&amp;#34;x86: don&amp;#39;t use REP_GOOD or ERMS for user memory
clearing&amp;#34;) upstream.&lt;/p&gt;
&lt;p&gt;However, rather than backport the full range of x86 memory clearing and
copying cleanups, fix the exception table annotation placement for the
final &amp;#39;rep movsb&amp;#39; in clear_user_rep_good(): rather than pointing at the
actual instruction that did the user space access, it pointed to the
register move just before it.&lt;/p&gt;
&lt;p&gt;That made sense from a code flow standpoint, but not from an actual
usage standpoint: it means that if user access takes an exception, the
exception handler won&amp;#39;t actually find the instruction in the exception
tables.&lt;/p&gt;
&lt;p&gt;As a result, rather than fixing it up and returning -EFAULT, it would
then turn it into a kernel oops report instead, something like:&lt;/p&gt;
&lt;p&gt;BUG: unable to handle page fault for address: 0000000020081000
    #PF: supervisor write access in kernel mode
    #PF: error_code(0x0002) - not-present page
    ...
    RIP: 0010:clear_user_rep_good+0x1c/0x30 arch/x86/lib/clear_page_64.S:147
    ...
    Call Trace:
      __clear_user arch/x86/include/asm/uaccess_64.h:103 [inline]
      clear_user arch/x86/include/asm/uaccess_64.h:124 [inline]
      iov_iter_zero+0x709/0x1290 lib/iov_iter.c:800
      iomap_dio_hole_iter fs/iomap/direct-io.c:389 [inline]
      iomap_dio_iter fs/ioma…&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;x86: fix clear_user_rep_good() exception handling annotation&lt;/p&gt;
&lt;p&gt;This code no longer exists in mainline, because it was removed in
commit d2c95f9d6802 (&amp;#34;x86: don&amp;#39;t use REP_GOOD or ERMS for user memory
clearing&amp;#34;) upstream.&lt;/p&gt;
&lt;p&gt;However, rather than backport the full range of x86 memory clearing and
copying cleanups, fix the exception table annotation placement for the
final &amp;#39;rep movsb&amp;#39; in clear_user_rep_good(): rather than pointing at the
actual instruction that did the user space access, it pointed to the
register move just before it.&lt;/p&gt;
&lt;p&gt;That made sense from a code flow standpoint, but not from an actual
usage standpoint: it means that if user access takes an exception, the
exception handler won&amp;#39;t actually find the instruction in the exception
tables.&lt;/p&gt;
&lt;p&gt;As a result, rather than fixing it up and returning -EFAULT, it would
then turn it into a kernel oops report instead, something like:&lt;/p&gt;
&lt;p&gt;BUG: unable to handle page fault for address: 0000000020081000
    #PF: supervisor write access in kernel mode
    #PF: error_code(0x0002) - not-present page
    ...
    RIP: 0010:clear_user_rep_good+0x1c/0x30 arch/x86/lib/clear_page_64.S:147
    ...
    Call Trace:
      __clear_user arch/x86/include/asm/uaccess_64.h:103 [inline]
      clear_user arch/x86/include/asm/uaccess_64.h:124 [inline]
      iov_iter_zero+0x709/0x1290 lib/iov_iter.c:800
      iomap_dio_hole_iter fs/iomap/direct-io.c:389 [inline]
      iomap_dio_iter fs/ioma…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2023-53642</guid>
    </item>
  </channel>
</rss>
