<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-17T21:08:07.821220+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/cve-2026-98273</id>
    <title>CVE-2026-98273 — x86/kprobes: Fix crash when probing CS CALL instructions</title>
    <updated>2026-10-17T21:08:07.822165+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>x86/kprobes: Fix crash when probing CS CALL instructions</p>
<p>When using eBPF to probe CS CALL instructions within a function,
a crash can be triggered.</p>
<p>The eBPF tool probes offset 257 of the __hrtimer_run_queues()
function:</p>
<p>&lt;__hrtimer_run_queues+249&gt;:  nopl   0x0(%rax,%rax,1)
&lt;__hrtimer_run_queues+254&gt;:  mov    %r14,%rdi
&lt;__hrtimer_run_queues+257&gt;:  cs call &lt;__x86_indirect_thunk_r12&gt;
&lt;__hrtimer_run_queues+263&gt;:  mov    %eax,%r12d
&lt;__hrtimer_run_queues+266&gt;:  xchg   %ax,%ax
&lt;__hrtimer_run_queues+268&gt;:  mov    %r13,%rdi</p>
<p>Which triggers this crash:</p>
<p>BUG: unable to handle page fault for address: 00000000000f41c9
  #PF: supervisor write access in kernel mode
  #PF: error_code(0x0002) - not-present page
  PGD 0 P4D 0
  Oops: 0002 [#1] SMP NOPTI
  CPU: 1 PID: 0 Comm: swapper/1 Kdump: loaded Tainted: P
  RIP: 0010:__hrtimer_run_queues+0x106/0x230</p>
<p>Note that __hrtimer_run_queues+0x106 is __hrtimer_run_queues+262, which is
at the 6th byte of the above CS CALL instruction. Since the CS CALL
instruction occupies 6 bytes, the exception occurred in the middle of that
call instruction.</p>
<p>The root cause is that when using eBPF tools to probe in the middle of a
function, a kprobe with INT3 is used as the underlying implementation.</p>
<p>During single-step emulation of the original CALL instruction,
int3_emulate_call() assumes that the probed CALL instruction is 5 bytes
long. However, the actual CS-prefixed CALL instruction occup…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-98273"/>
  </entry>
</feed>
