CVE-2026-53326

MEDIUMNVD 5.55.5
EchelonGraph scoreHIGH confidence

Score 5.5 from GitHub Security Advisory published 2026-07-01. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
5.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
5.5
EG Score
5.5(high)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
0.8%
KEV
Not listed

Published

July 1, 2026

Last Modified

July 23, 2026

Advisory Details (6)

Auto-updated Jul 24, 2026
No patch confirmed yet.
generic

debugobjects: Don't call fill_pool() in early boot hardirq context - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7bc71bdb1c1526c7f02a6adab324394ff1327b0a
generic

debugobjects: Dont call fill_pool() in early boot hardirq context - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5d95f6b267f3d7fe54f42a3b224bb4a3d3990b41
generic

debugobjects: Dont call fill_pool() in early boot hardirq context - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/44b8b03a9fb5c575548fc72c674653d6baba142a
generic

debugobjects: Dont call fill_pool() in early boot hardirq context - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3cc90ea0dd0fb1f8db577dcdc027fc46c06049f6
generic

debugobjects: Dont call fill_pool() in early boot hardirq context - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/27335c50014102e9077b784ebd314954286afcab
generic

debugobjects: Don't call fill_pool() in early boot hardirq context - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0d046ae106255cba5eb83b23f78ee93f3620247d

Vendor Advisories for CVE-2026-53326(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 46× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-24 14:18 UTCEPSS rescore
  2. 2026-07-23 22:13 UTCEG score recompute 5.50
  3. 2026-07-23 22:13 UTCGHSA enrichment
  4. 2026-07-23 22:11 UTCNVD updateCVSS v3 → 5.5 · severity → MEDIUM
  5. 2026-07-23 14:18 UTCEPSS rescore
  6. 2026-07-23 03:19 UTCEG score recompute
  7. 2026-07-22 14:08 UTCEPSS rescore
  8. 2026-07-21 15:25 UTCEPSS rescore
  9. 2026-07-20 17:08 UTCEPSS rescore
  10. 2026-07-19 14:31 UTCEPSS rescore
  11. 2026-07-19 14:31 UTCEPSS rescore
  12. 2026-07-19 02:29 UTCEPSS rescore
  13. 2026-07-18 10:04 UTCEPSS rescore
  14. 2026-07-16 17:03 UTCEPSS rescore
  15. 2026-07-15 20:53 UTCGHSA enrichment
  16. 2026-07-15 16:57 UTCEPSS rescore
  17. 2026-07-15 16:57 UTCEPSS rescore
  18. 2026-07-15 02:00 UTCEPSS rescore
  19. 2026-07-15 02:00 UTCEPSS rescore
  20. 2026-07-13 22:31 UTCEPSS rescore
  21. 2026-07-13 06:13 UTCEPSS rescore
  22. 2026-07-13 06:13 UTCEPSS rescore
  23. 2026-07-13 00:42 UTCGHSA enrichment
  24. 2026-07-11 08:27 UTCEPSS rescore
  25. 2026-07-11 08:27 UTCEPSS rescore
Show 21 more
  1. 2026-07-10 04:33 UTCGHSA enrichment
  2. 2026-07-09 19:10 UTCEPSS rescore
  3. 2026-07-09 19:10 UTCEPSS rescore
  4. 2026-07-08 15:16 UTCEPSS rescore
  5. 2026-07-08 15:16 UTCEPSS rescore
  6. 2026-07-07 13:46 UTCEPSS rescore
  7. 2026-07-07 13:46 UTCEPSS rescore
  8. 2026-07-07 08:24 UTCGHSA enrichment
  9. 2026-07-06 16:27 UTCEPSS rescore
  10. 2026-07-06 16:27 UTCEPSS rescore
  11. 2026-07-06 02:23 UTCEPSS rescore
  12. 2026-07-06 02:23 UTCEPSS rescore
  13. 2026-07-05 02:31 UTCEPSS rescore
  14. 2026-07-05 02:30 UTCEPSS rescore
  15. 2026-07-04 12:27 UTCNVD update
  16. 2026-07-04 12:16 UTCMITRE cvelistV5
  17. 2026-07-04 12:13 UTCGHSA enrichment
  18. 2026-07-04 06:31 UTCEPSS rescore
  19. 2026-07-04 06:31 UTCEPSS rescore
  20. 2026-07-01 16:05 UTCEG score recompute
  21. 2026-07-01 16:04 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-53326?
CVE-2026-53326 is a medium vulnerability published on July 1, 2026. 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…
When was CVE-2026-53326 disclosed?
CVE-2026-53326 was first published in the National Vulnerability Database on July 1, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53326 actively exploited?
CVE-2026-53326 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53326?
CVE-2026-53326 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-53326?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53326, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-53326

Explore →

Is Your Infrastructure Affected by CVE-2026-53326?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.