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-53326debugobjects: Don't call fill_pool() in early boot hardirq context

Description

In the Linux kernel, the following vulnerability has been resolved: debugobjects: Don't call fill_pool() in early boot hardirq context When booting a debug PREEMPT_RT kernel on an ARM64 system, a "inconsistent {HARDIRQ-ON-W} -> {IN-HARDIRQ-W} usage" lockdep warning message was reported to the console. During early boot, interrupts are enabled before the scheduler is enabled. In this window (before SYSTEM_SCHEDULING is set) interrupts can fire and in the hard interrupt context handler attempt to fill the pool This can lead to a deadlock when the interrupt occurred when the interrupt hits a region which holds a lock that is required to be taken in the allocation path. Add a new can_fill_pool() helper and reorder the exception rule and forbid this scenario by excluding allocations from hard interrupt context.

Timeline

  1. ID reserved

    By Linux

  2. · 22 days later

    Published

  3. · 3 days 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-53326, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.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.13% · top 98% of all CVEs (15 Nov 2026)
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 13abb2b11ac3b6cb89822f152e770081893e4bc3 – < 3cc90ea0dd0fb1f8db577dcdc027fc46c06049f6
    • affected 0d2a64411b0974a469ff56e62441055147e5a194 – < 5d95f6b267f3d7fe54f42a3b224bb4a3d3990b41
    • affected c93859a52b0d6953cdaa17fd7fb46a6871b015cf – < 27335c50014102e9077b784ebd314954286afcab
    • affected a460935022f512e167b4c5d4c12d85f89ba6aabd – < 44b8b03a9fb5c575548fc72c674653d6baba142a
    • affected 06e0ae988f6e3499785c407429953ade19c1096b – < 7bc71bdb1c1526c7f02a6adab324394ff1327b0a
    • affected 06e0ae988f6e3499785c407429953ade19c1096b – < 0d046ae106255cba5eb83b23f78ee93f3620247d
  • Linux · Linux

    • affected 6.19
    • unaffected < 6.19
    • unaffected 7.0.13 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .