CVE-2026-53326 json
debugobjects: Don't call fill_pool() in early boot hardirq context
published 2026-07-01 4 mo ago modified 2026-07-23 3 mo ago also EUVD-2026-40960
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 2%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 7.0.13, 7.1
- linux Debian 14 7.0.13-1
debian advisories DEBIAN-CVE-2026-53326
- linux Ubuntu 26.04 LTS 7.0.0-31.31
- linux-aws Ubuntu 26.04 LTS 7.0.0-1012.12
- linux-gcp Ubuntu 26.04 LTS 7.0.0-1011.11
- linux-gke Ubuntu 26.04 LTS 7.0.0-1006.7
- linux-ibm Ubuntu 26.04 LTS 7.0.0-1013.13
- linux-azure Ubuntu 26.04 LTS 7.0.0-1014.14
- linux-raspi Ubuntu 26.04 LTS 7.0.0-1019.19
- linux-riscv Ubuntu 26.04 LTS 7.0.0-31.31.1
ubuntu advisories UBUNTU-CVE-2026-53326
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/3cc90ea0dd0fb1f8db577dcdc027fc46c06049f6 commit
- git.kernel.org/stable/c/5d95f6b267f3d7fe54f42a3b224bb4a3d3990b41 commit
- git.kernel.org/stable/c/27335c50014102e9077b784ebd314954286afcab commit
- git.kernel.org/stable/c/44b8b03a9fb5c575548fc72c674653d6baba142a commit
- git.kernel.org/stable/c/7bc71bdb1c1526c7f02a6adab324394ff1327b0a commit
- git.kernel.org/stable/c/0d046ae106255cba5eb83b23f78ee93f3620247d commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-53326 updated cvss 5.5
kernel: debugobjects: Don't call fill_pool() in early boot hardirq context
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 moreaffected: no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.13% chance of exploitation in the next 30 days, higher than 2% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Weakness
-
- CWE-667 Improper Locking
- Technology feeds
References
-
git.kernel.org
/stable/c/3cc90ea0dd0fb1f8db577dcdc027fc46c06049f6
patch
-
git.kernel.org
/stable/c/5d95f6b267f3d7fe54f42a3b224bb4a3d3990b41
patch
-
git.kernel.org
/stable/c/27335c50014102e9077b784ebd314954286afcab
patch
-
git.kernel.org
/stable/c/44b8b03a9fb5c575548fc72c674653d6baba142a
patch
-
git.kernel.org
/stable/c/7bc71bdb1c1526c7f02a6adab324394ff1327b0a
patch
-
git.kernel.org
/stable/c/0d046ae106255cba5eb83b23f78ee93f3620247d
patch
Sources
- CVE List CVE-2026-53326
- NVD CVE-2026-53326
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.