<?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>Sun, 04 Oct 2026 15:39:42 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-43311 — soc/tegra: pmc: Fix unsafe generic_handle_irq() call</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-43311</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;soc/tegra: pmc: Fix unsafe generic_handle_irq() call&lt;/p&gt;
&lt;p&gt;Currently, when resuming from system suspend on Tegra platforms,
the following warning is observed:&lt;/p&gt;
&lt;p&gt;WARNING: CPU: 0 PID: 14459 at kernel/irq/irqdesc.c:666
Call trace:
 handle_irq_desc+0x20/0x58 (P)
 tegra186_pmc_wake_syscore_resume+0xe4/0x15c
 syscore_resume+0x3c/0xb8
 suspend_devices_and_enter+0x510/0x540
 pm_suspend+0x16c/0x1d8&lt;/p&gt;
&lt;p&gt;The warning occurs because generic_handle_irq() is being called from
a non-interrupt context which is considered as unsafe.&lt;/p&gt;
&lt;p&gt;Fix this warning by deferring generic_handle_irq() call to an IRQ work
which gets executed in hard IRQ context where generic_handle_irq()
can be called safely.&lt;/p&gt;
&lt;p&gt;When PREEMPT_RT kernels are used, regular IRQ work (initialized with
init_irq_work) is deferred to run in per-CPU kthreads in preemptible
context rather than hard IRQ context. Hence, use the IRQ_WORK_INIT_HARD
variant so that with PREEMPT_RT kernels, the IRQ work is processed in
hardirq context instead of being deferred to a thread which is required
for calling generic_handle_irq().&lt;/p&gt;
&lt;p&gt;On non-PREEMPT_RT kernels, both init_irq_work() and IRQ_WORK_INIT_HARD()
execute in IRQ context, so this change has no functional impact for
standard kernel configurations.&lt;/p&gt;
&lt;p&gt;[treding@nvidia.com: miscellaneous cleanups]&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;soc/tegra: pmc: Fix unsafe generic_handle_irq() call&lt;/p&gt;
&lt;p&gt;Currently, when resuming from system suspend on Tegra platforms,
the following warning is observed:&lt;/p&gt;
&lt;p&gt;WARNING: CPU: 0 PID: 14459 at kernel/irq/irqdesc.c:666
Call trace:
 handle_irq_desc+0x20/0x58 (P)
 tegra186_pmc_wake_syscore_resume+0xe4/0x15c
 syscore_resume+0x3c/0xb8
 suspend_devices_and_enter+0x510/0x540
 pm_suspend+0x16c/0x1d8&lt;/p&gt;
&lt;p&gt;The warning occurs because generic_handle_irq() is being called from
a non-interrupt context which is considered as unsafe.&lt;/p&gt;
&lt;p&gt;Fix this warning by deferring generic_handle_irq() call to an IRQ work
which gets executed in hard IRQ context where generic_handle_irq()
can be called safely.&lt;/p&gt;
&lt;p&gt;When PREEMPT_RT kernels are used, regular IRQ work (initialized with
init_irq_work) is deferred to run in per-CPU kthreads in preemptible
context rather than hard IRQ context. Hence, use the IRQ_WORK_INIT_HARD
variant so that with PREEMPT_RT kernels, the IRQ work is processed in
hardirq context instead of being deferred to a thread which is required
for calling generic_handle_irq().&lt;/p&gt;
&lt;p&gt;On non-PREEMPT_RT kernels, both init_irq_work() and IRQ_WORK_INIT_HARD()
execute in IRQ context, so this change has no functional impact for
standard kernel configurations.&lt;/p&gt;
&lt;p&gt;[treding@nvidia.com: miscellaneous cleanups]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-43311</guid>
    </item>
  </channel>
</rss>
