CVE-2026-53326

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM 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.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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(medium)
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 PROB
0%
EPSS %ILE
3%
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.

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-oem-7.0 (7.0.0-1013.13) @ resolute2026-09-18ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-18ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-31.31) @ resolute2026-09-18ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1018.18~24.04.1) @ noble2026-09-18ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (145 versions)7.0.13-1—

Weakness Classification(1)

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

All Vendor Advisories

(4)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 9× in last 7d / 41× 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.

Showing the most recent 100 of 156 total refreshes for this CVE.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 06:36 UTCEG score recompute
  3. 2026-09-18 06:36 UTCVendor advisory
  4. 2026-09-18 06:36 UTCGHSA enrichment
  5. 2026-09-16 14:08 UTCEPSS rescore
  6. 2026-09-16 05:15 UTCEPSS rescore
  7. 2026-09-13 16:47 UTCEPSS rescore
  8. 2026-09-13 12:27 UTCVendor advisory
  9. 2026-09-13 12:27 UTCGHSA enrichment
  10. 2026-09-12 14:49 UTCEG score recompute
  11. 2026-09-12 14:49 UTCVendor advisory
  12. 2026-09-12 14:49 UTCGHSA enrichment
  13. 2026-09-11 14:53 UTCEPSS rescore
  14. 2026-09-10 09:35 UTCEPSS rescore
  15. 2026-09-08 22:01 UTCEPSS rescore
  16. 2026-09-07 16:01 UTCEPSS rescore
  17. 2026-09-06 13:47 UTCEPSS rescore
  18. 2026-09-06 02:36 UTCEG score recompute
  19. 2026-09-06 02:36 UTCGHSA enrichment
  20. 2026-09-04 05:06 UTCEPSS rescore
  21. 2026-09-01 13:54 UTCEPSS rescore
  22. 2026-09-01 04:40 UTCEPSS rescore
  23. 2026-08-30 19:17 UTCEPSS rescore
  24. 2026-08-30 13:14 UTCEG score recompute
  25. 2026-08-30 13:14 UTCGHSA enrichment
Show 75 more
  1. 2026-08-30 01:22 UTCEPSS rescore
  2. 2026-08-28 21:41 UTCEPSS rescore
  3. 2026-08-27 22:28 UTCEG score recompute
  4. 2026-08-27 22:28 UTCGHSA enrichment
  5. 2026-08-27 14:25 UTCEPSS rescore
  6. 2026-08-25 13:49 UTCEPSS rescore
  7. 2026-08-24 21:02 UTCEG score recompute
  8. 2026-08-24 21:02 UTCGHSA enrichment
  9. 2026-08-23 19:23 UTCEG score recompute
  10. 2026-08-23 19:23 UTCGHSA enrichment
  11. 2026-08-23 00:19 UTCEPSS rescore
  12. 2026-08-22 21:45 UTCGHSA enrichment
  13. 2026-08-22 00:04 UTCEG score recompute
  14. 2026-08-22 00:04 UTCGHSA enrichment
  15. 2026-08-21 23:49 UTCEPSS rescore
  16. 2026-08-21 02:25 UTCGHSA enrichment
  17. 2026-08-20 04:47 UTCEG score recompute
  18. 2026-08-20 04:47 UTCGHSA enrichment
  19. 2026-08-19 17:04 UTCEPSS rescore
  20. 2026-08-18 21:00 UTCEG score recompute
  21. 2026-08-18 21:00 UTCGHSA enrichment
  22. 2026-08-18 13:48 UTCEPSS rescore
  23. 2026-08-17 13:47 UTCEPSS rescore
  24. 2026-08-17 09:48 UTCEG score recompute
  25. 2026-08-17 09:48 UTCGHSA enrichment
  26. 2026-08-16 14:56 UTCEPSS rescore
  27. 2026-08-16 12:10 UTCEG score recompute
  28. 2026-08-16 12:10 UTCGHSA enrichment
  29. 2026-08-16 02:14 UTCEPSS rescore
  30. 2026-08-15 14:33 UTCEG score recompute
  31. 2026-08-15 14:33 UTCGHSA enrichment
  32. 2026-08-15 01:30 UTCEPSS rescore
  33. 2026-08-14 16:55 UTCEG score recompute
  34. 2026-08-14 16:55 UTCGHSA enrichment
  35. 2026-08-13 22:00 UTCEPSS rescore
  36. 2026-08-13 19:08 UTCGHSA enrichment
  37. 2026-08-12 21:31 UTCEG score recompute
  38. 2026-08-12 21:31 UTCGHSA enrichment
  39. 2026-08-12 13:51 UTCEPSS rescore
  40. 2026-08-11 23:53 UTCEG score recompute
  41. 2026-08-11 23:53 UTCGHSA enrichment
  42. 2026-08-11 02:15 UTCGHSA enrichment
  43. 2026-08-10 04:38 UTCEG score recompute
  44. 2026-08-10 04:38 UTCGHSA enrichment
  45. 2026-08-09 13:46 UTCEPSS rescore
  46. 2026-08-09 07:00 UTCEG score recompute
  47. 2026-08-09 07:00 UTCGHSA enrichment
  48. 2026-08-08 16:37 UTCEPSS rescore
  49. 2026-08-08 09:23 UTCEG score recompute
  50. 2026-08-08 09:23 UTCGHSA enrichment
  51. 2026-08-07 11:45 UTCGHSA enrichment
  52. 2026-08-06 14:02 UTCEG score recompute
  53. 2026-08-06 14:02 UTCGHSA enrichment
  54. 2026-08-06 13:47 UTCEPSS rescore
  55. 2026-08-05 19:17 UTCEPSS rescore
  56. 2026-08-05 16:24 UTCGHSA enrichment
  57. 2026-08-04 14:31 UTCEG score recompute
  58. 2026-08-04 14:31 UTCGHSA enrichment
  59. 2026-08-04 10:39 UTCEPSS rescore
  60. 2026-08-03 16:37 UTCEG score recompute
  61. 2026-08-03 16:37 UTCGHSA enrichment
  62. 2026-08-03 10:36 UTCEPSS rescore
  63. 2026-08-02 18:59 UTCGHSA enrichment
  64. 2026-08-01 21:21 UTCEG score recompute
  65. 2026-08-01 21:21 UTCGHSA enrichment
  66. 2026-08-01 04:16 UTCEPSS rescore
  67. 2026-07-31 23:43 UTCEG score recompute
  68. 2026-07-31 23:43 UTCGHSA enrichment
  69. 2026-07-31 02:05 UTCEG score recompute
  70. 2026-07-31 02:05 UTCGHSA enrichment
  71. 2026-07-30 16:28 UTCEPSS rescore
  72. 2026-07-30 04:00 UTCEG score recompute
  73. 2026-07-30 04:00 UTCGHSA enrichment
  74. 2026-07-30 01:30 UTCEPSS rescore
  75. 2026-07-29 06:22 UTCEG score recompute

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% probability of exploitation in the next 30 days, which ranks it in the top 97.4% of all scored CVEs.
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

See which npm, PyPI, Go, and Maven packages are affected by 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.

Start Free Scan →Browse All CVEs