dbcve.org
Linux KernelOperating system · Linux

CVE-2026-53326

MEDIUM · 5.5 CVSS v3.1 Published 2026-07-01
Fix available
A fix is available. Upgrade to 7.0.13 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click 7 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A deadlock vulnerability in the Linux kernel's debugobjects subsystem occurs during early boot when interrupts fire in hard interrupt context before the scheduler is enabled. The interrupt handlers attempt to fill the debugobjects pool while potentially holding locks required by the allocation path, causing a lockdep-reported deadlock on ARM64 PREEMPT_RT kernels.

MitigationApply the kernel patch that adds a can_fill_pool() helper to exclude allocations from hard interrupt context during early boot. This is a source-code-level fix requiring kernel rebuild.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 6.19, < 7.0.13= 7.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check kernel version
    Run `uname -r` or check /proc/version and compare against affected range: >= 6.19 and < 7.0.13, or exactly 7.1
    Affected if Kernel version falls within the affected range (6.19 to 7.0.13 inclusive, or 7.1)
  2. Verify PREEMPT_RT patch is applied
    Check kernel config via `cat /boot/config-$(uname -r) | grep CONFIG_PREEMPT_RT` or look for 'PREEMPT_RT' in /proc/version
    Affected if Kernel has PREEMPT_RT enabled (the vulnerability only affects PREEMPT_RT kernels)
  3. Confirm debug object tracking is enabled
    Check kernel config via `cat /boot/config-$(uname -r) | grep CONFIG_DEBUG_OBJECTS` or check /sys/kernel/debug/object_stat
    Affected if CONFIG_DEBUG_OBJECTS is enabled in the kernel configuration
  4. Search for lockdep warnings in system logs
    Run `dmesg | grep -i lockdep` or check /var/log/dmesg, /var/log/syslog for messages containing 'debug_objects' and 'lock' or 'deadlock'
    Affected if Lockdep warnings related to debug object pool allocation appear in kernel logs

Environment is affected if running a PREEMPT_RT kernel version 6.19 through 7.0.13 or 7.1, with debug object tracking enabled, and the system experiences lockdep warnings during early boot related to debug object allocation from hard interrupt context.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 7.0.13 or later
Fixed in 7.0.13
Interim mitigation

Apply the kernel patch that adds a can_fill_pool() helper to exclude allocations from hard interrupt context during early boot. This is a source-code-level fix requiring kernel rebuild.

Recommended fix Moderate confidence

Linux Kernel 7.0.13 or later, or any 7.x release after 7.1 (e.g., 7.2, 7.3, etc.)

  1. Identify the current kernel version using 'uname -r' or 'cat /proc/version'
  2. Verify the running kernel is affected: version >= 6.19 and < 7.0.13, or exactly 7.1
  3. Check available kernel packages for your distribution (e.g., apt list --upgradable, yum list kernel, dnf list kernel)
  4. Upgrade to kernel version 7.0.13 or later, or a version beyond 7.1 (e.g., 7.2+)
  5. Reboot the system to load the new kernel
  6. Verify the new kernel version is running with 'uname -r' and confirm it is a fixed version
Caveat Kernel upgrades may require system reboot and could have compatibility implications with custom modules or specific hardware drivers; test in staging environment before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Linux Kernel Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-53326 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-53326 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data