CVE-2026-53326
Last modified
CVE-2026-53326 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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.. EPSS estimates a 0.17% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 6.19, < 7.0.13 | — |
| Linux | Linux Kernel | 7.1 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-53326?
How severe is CVE-2026-53326?
How do I fix CVE-2026-53326?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-53320In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53321In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53322In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-53323In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53324In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53325In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53327In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53328In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53329In the Linux kernel, the following vulnerability has been re…7
- CVE-2026-5333A security flaw has been discovered in DefaultFuction Conten…9.8
- CVE-2026-53330In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-53331In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2026-53326?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
