NVD / CVE Program· CNA Linux

CVE-2026-53326: debugobjects: Don't call fill_pool() in early boot hardirq context

Noroxi assessment

Priority: Monitor (action score 22/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.12% (FIRST EPSS).
Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: Linux Linux 0d046ae106255cba5eb83b23f78ee93f3620247d, 27335c50014102e9077b784ebd314954286afcab, 3cc90ea0dd0fb1f8db577dcdc027fc46c06049f6.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 0d046ae106255cba5eb83b23f78ee93f3620247d, 27335c50014102e9077b784ebd314954286afcab, 3cc90ea0dd0fb1f8db577dcdc027fc46c06049f6 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 5.5 · v3.1—No exploit Fix available

Denial of service

Published: Jul 1, 2026
Updated: Jul 23, 2026
EPSS: 0.1% · 2th percentile
CWE: CWE-667

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 22 / 40 · 5.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.1%

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
linux	linux kernel	cpe:2.3:o:linux:linux_kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

linux linux kernel6.19 and later · before 7.0.13
linux linux kernel7.1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

Linux Linux
- 6.19affected
- 13abb2b11ac3b6cb89822f152e770081893e4bc3 and later · before 3cc90ea0dd0fb1f8db577dcdc027fc46c06049f6affected · git
- 0d2a64411b0974a469ff56e62441055147e5a194 and later · before 5d95f6b267f3d7fe54f42a3b224bb4a3d3990b41affected · git
- c93859a52b0d6953cdaa17fd7fb46a6871b015cf and later · before 27335c50014102e9077b784ebd314954286afcabaffected · git
- a460935022f512e167b4c5d4c12d85f89ba6aabd and later · before 44b8b03a9fb5c575548fc72c674653d6baba142aaffected · git
- 06e0ae988f6e3499785c407429953ade19c1096b and later · before 7bc71bdb1c1526c7f02a6adab324394ff1327b0aaffected · git
- 06e0ae988f6e3499785c407429953ade19c1096b and later · before 0d046ae106255cba5eb83b23f78ee93f3620247daffected · git
- before 6.19not affected · semver
- 7.0.13 and later · up to and including 7.0.*not affected · semver
- 7.1 and laternot affected · original_commit_for_fix

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:14	linux	before 7.0.13-1	7.0.13-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
90Now
CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
89Now
CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
85Now

Published before and after this one in the same product

← EarlierCVE-2026-53321Jun 26, 2026 · io_uring/napi: cap busy_poll_to 10 msec
22Monitor
← EarlierCVE-2026-53325Jun 29, 2026 · agp/amd64: Fix broken error propagation in agp_amd64_probe()
22Monitor
Later →CVE-2026-53327Jul 1, 2026 · debugobjects: Do not fill_pool() if pi_blocked_on
22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Linux Linux	0d046ae106255cba5eb83b23f78ee93f3620247d	Vendor (CNA)
Linux Linux	27335c50014102e9077b784ebd314954286afcab	Vendor (CNA)
Linux Linux	3cc90ea0dd0fb1f8db577dcdc027fc46c06049f6	Vendor (CNA)
Linux Linux	44b8b03a9fb5c575548fc72c674653d6baba142a	Vendor (CNA)
Linux Linux	5d95f6b267f3d7fe54f42a3b224bb4a3d3990b41	Vendor (CNA)
Linux Linux	7bc71bdb1c1526c7f02a6adab324394ff1327b0a	Vendor (CNA)
debian:linux	7.0.13-1 · Debian:14	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).