<?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://cve.radiocsirt.org</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>Thu, 08 Oct 2026 16:01:44 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-42240 — x86/bhi: Avoid warning in #DB handler due to BHI mitigation</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2024-42240</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/bhi: Avoid warning in #DB handler due to BHI mitigation&lt;/p&gt;
&lt;p&gt;When BHI mitigation is enabled, if SYSENTER is invoked with the TF flag set
then entry_SYSENTER_compat() uses CLEAR_BRANCH_HISTORY and calls the
clear_bhb_loop() before the TF flag is cleared. This causes the #DB handler
(exc_debug_kernel()) to issue a warning because single-step is used outside the
entry_SYSENTER_compat() function.&lt;/p&gt;
&lt;p&gt;To address this issue, entry_SYSENTER_compat() should use CLEAR_BRANCH_HISTORY
after making sure the TF flag is cleared.&lt;/p&gt;
&lt;p&gt;The problem can be reproduced with the following sequence:&lt;/p&gt;
&lt;p&gt;$ cat sysenter_step.c
  int main()
  { asm(&amp;#34;pushf; pop %ax; bts $8,%ax; push %ax; popf; sysenter&amp;#34;); }&lt;/p&gt;
&lt;p&gt;$ gcc -o sysenter_step sysenter_step.c&lt;/p&gt;
&lt;p&gt;$ ./sysenter_step
  Segmentation fault (core dumped)&lt;/p&gt;
&lt;p&gt;The program is expected to crash, and the #DB handler will issue a warning.&lt;/p&gt;
&lt;p&gt;Kernel log:&lt;/p&gt;
&lt;p&gt;WARNING: CPU: 27 PID: 7000 at arch/x86/kernel/traps.c:1009 exc_debug_kernel+0xd2/0x160
  ...
  RIP: 0010:exc_debug_kernel+0xd2/0x160
  ...
  Call Trace:
  &amp;lt;#DB&amp;gt;
   ? show_regs+0x68/0x80
   ? __warn+0x8c/0x140
   ? exc_debug_kernel+0xd2/0x160
   ? report_bug+0x175/0x1a0
   ? handle_bug+0x44/0x90
   ? exc_invalid_op+0x1c/0x70
   ? asm_exc_invalid_op+0x1f/0x30
   ? exc_debug_kernel+0xd2/0x160
   exc_debug+0x43/0x50
   asm_exc_debug+0x1e/0x40
  RIP: 0010:clear_bhb_loop+0x0/0xb0
  ...
  &amp;lt;/#DB&amp;gt;
  &amp;lt;TASK&amp;gt;
   ? entry_SYSENTER_compat_after_hwframe+0x6e/0x8d…&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/bhi: Avoid warning in #DB handler due to BHI mitigation&lt;/p&gt;
&lt;p&gt;When BHI mitigation is enabled, if SYSENTER is invoked with the TF flag set
then entry_SYSENTER_compat() uses CLEAR_BRANCH_HISTORY and calls the
clear_bhb_loop() before the TF flag is cleared. This causes the #DB handler
(exc_debug_kernel()) to issue a warning because single-step is used outside the
entry_SYSENTER_compat() function.&lt;/p&gt;
&lt;p&gt;To address this issue, entry_SYSENTER_compat() should use CLEAR_BRANCH_HISTORY
after making sure the TF flag is cleared.&lt;/p&gt;
&lt;p&gt;The problem can be reproduced with the following sequence:&lt;/p&gt;
&lt;p&gt;$ cat sysenter_step.c
  int main()
  { asm(&amp;#34;pushf; pop %ax; bts $8,%ax; push %ax; popf; sysenter&amp;#34;); }&lt;/p&gt;
&lt;p&gt;$ gcc -o sysenter_step sysenter_step.c&lt;/p&gt;
&lt;p&gt;$ ./sysenter_step
  Segmentation fault (core dumped)&lt;/p&gt;
&lt;p&gt;The program is expected to crash, and the #DB handler will issue a warning.&lt;/p&gt;
&lt;p&gt;Kernel log:&lt;/p&gt;
&lt;p&gt;WARNING: CPU: 27 PID: 7000 at arch/x86/kernel/traps.c:1009 exc_debug_kernel+0xd2/0x160
  ...
  RIP: 0010:exc_debug_kernel+0xd2/0x160
  ...
  Call Trace:
  &amp;lt;#DB&amp;gt;
   ? show_regs+0x68/0x80
   ? __warn+0x8c/0x140
   ? exc_debug_kernel+0xd2/0x160
   ? report_bug+0x175/0x1a0
   ? handle_bug+0x44/0x90
   ? exc_invalid_op+0x1c/0x70
   ? asm_exc_invalid_op+0x1f/0x30
   ? exc_debug_kernel+0xd2/0x160
   exc_debug+0x43/0x50
   asm_exc_debug+0x1e/0x40
  RIP: 0010:clear_bhb_loop+0x0/0xb0
  ...
  &amp;lt;/#DB&amp;gt;
  &amp;lt;TASK&amp;gt;
   ? entry_SYSENTER_compat_after_hwframe+0x6e/0x8d…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2024-42240</guid>
    </item>
  </channel>
</rss>
