Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-43311soc/tegra: pmc: Fix unsafe generic_handle_irq() call

Description

In the Linux kernel, the following vulnerability has been resolved: soc/tegra: pmc: Fix unsafe generic_handle_irq() call Currently, when resuming from system suspend on Tegra platforms, the following warning is observed: 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 The warning occurs because generic_handle_irq() is being called from a non-interrupt context which is considered as unsafe. 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. 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(). 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. [[email protected]: miscellaneous cleanups]

Timeline

  1. ID reserved

    By Linux

  2. · 7 days later

    Published

  3. · 6 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-43311, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.12% · top 98% of all CVEs (15 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 0474cc8489bda9a8cd6a10252e7e6af29c849438 – < d1c9c79eb06ed7c4e0a090ba5b1d4e475f7d0681
    • affected 0474cc8489bda9a8cd6a10252e7e6af29c849438 – < 5330afc068e90c538dd25aa8f82b3735bdb6d461
    • affected 0474cc8489bda9a8cd6a10252e7e6af29c849438 – < 57a79c5df057deb7c1d0ebc066698c795092530f
    • affected 0474cc8489bda9a8cd6a10252e7e6af29c849438 – < 64016227dcdb968b7030eda04304f3d0df5d209d
    • affected 0474cc8489bda9a8cd6a10252e7e6af29c849438 – < e6d96073af681780820c94079b978474a8a44413
  • Linux · Linux

    • affected 6.2
    • unaffected < 6.2
    • unaffected 6.6.143 – ≤ 6.6.*
    • unaffected 6.12.114 – ≤ 6.12.*
    • unaffected 6.18.57 – ≤ 6.18.*
    • unaffected 6.19.6 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-43311 badge
[![CVE-2026-43311](https://cveledger.app/badge/CVE-2026-43311.svg)](https://cveledger.app/cve/CVE-2026-43311)

Record last updated .