<?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://db.gcve.eu</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 12:18:25 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-90305 — ARM: 9483/1: select HAVE_POSIX_CPU_TIMERS_TASK_WORK</title>
      <link>https://db.gcve.eu/vuln/cve-2026-90305</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;ARM: 9483/1: select HAVE_POSIX_CPU_TIMERS_TASK_WORK&lt;/p&gt;
&lt;p&gt;Commit c6e61c06d606 (&amp;#34;ARM: 9463/1: Allow to enable RT&amp;#34;) enabled PREEMPT_RT
on ARM but did not select HAVE_POSIX_CPU_TIMERS_TASK_WORK. This leaves
CONFIG_POSIX_CPU_TIMERS_TASK_WORK disabled, so CPU timers expire in hard
IRQ context.&lt;/p&gt;
&lt;p&gt;On PREEMPT_RT this makes run_posix_cpu_timers() take the sleeping
sighand-&amp;gt;siglock:&lt;/p&gt;
&lt;p&gt;BUG: sleeping function called from invalid context at spinlock_rt.c:48
    rt_spin_lock from lock_task_sighand
    lock_task_sighand from run_posix_cpu_timers
    run_posix_cpu_timers from update_process_times&lt;/p&gt;
&lt;p&gt;ARM handles TIF_NOTIFY_RESUME on all return-to-user paths, including v7-M.
ARM32 KVM host support was removed by commit 541ad0150ca4 (&amp;#34;arm: Remove
32bit KVM host support&amp;#34;), so the select need not be conditional on KVM.&lt;/p&gt;
&lt;p&gt;Select it to defer POSIX CPU timer expiry to task context.&lt;/p&gt;
&lt;p&gt;Reproduced with setrlimit(RLIMIT_CPU, ...) and a busy loop. The same path
is used by setitimer(ITIMER_PROF or ITIMER_VIRTUAL) and POSIX CPU timers
created with timer_create().&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;ARM: 9483/1: select HAVE_POSIX_CPU_TIMERS_TASK_WORK&lt;/p&gt;
&lt;p&gt;Commit c6e61c06d606 (&amp;#34;ARM: 9463/1: Allow to enable RT&amp;#34;) enabled PREEMPT_RT
on ARM but did not select HAVE_POSIX_CPU_TIMERS_TASK_WORK. This leaves
CONFIG_POSIX_CPU_TIMERS_TASK_WORK disabled, so CPU timers expire in hard
IRQ context.&lt;/p&gt;
&lt;p&gt;On PREEMPT_RT this makes run_posix_cpu_timers() take the sleeping
sighand-&amp;gt;siglock:&lt;/p&gt;
&lt;p&gt;BUG: sleeping function called from invalid context at spinlock_rt.c:48
    rt_spin_lock from lock_task_sighand
    lock_task_sighand from run_posix_cpu_timers
    run_posix_cpu_timers from update_process_times&lt;/p&gt;
&lt;p&gt;ARM handles TIF_NOTIFY_RESUME on all return-to-user paths, including v7-M.
ARM32 KVM host support was removed by commit 541ad0150ca4 (&amp;#34;arm: Remove
32bit KVM host support&amp;#34;), so the select need not be conditional on KVM.&lt;/p&gt;
&lt;p&gt;Select it to defer POSIX CPU timer expiry to task context.&lt;/p&gt;
&lt;p&gt;Reproduced with setrlimit(RLIMIT_CPU, ...) and a busy loop. The same path
is used by setitimer(ITIMER_PROF or ITIMER_VIRTUAL) and POSIX CPU timers
created with timer_create().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-90305</guid>
    </item>
  </channel>
</rss>
