CVE-2026-53327

NONEPre-NVD 0.0Trending — 5 sources updated this week
0.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No confirmed exploitation signals yet
CISA-KEV: Not listedEPSS: 0%CVSS: —Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

debugobjects: Do not fill_pool() if pi_blocked_on

On RT enabled kernels, fill_pool() ends up calling rtlock_lock(), which asserts if current::pi_blocked_on is set, because a task can obviously only block on one lock as otherwise the priority inheritenace chain gets corrupted.

Prevent this by expanding the conditional to take current::pi_blocked_on into account.

CVSS v3
—
EG Score
0.0(none)
EPSS
6.9%
KEV
Not listed

Published

July 1, 2026

Last Modified

July 4, 2026

References (6)

Vendor Advisories for CVE-2026-53327(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

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

  1. 2026-07-07 06:02 UTCGHSA enrichment
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-06 02:23 UTCEPSS rescore
  6. 2026-07-05 02:31 UTCEPSS rescore
  7. 2026-07-05 02:30 UTCEPSS rescore
  8. 2026-07-04 12:27 UTCNVD update
  9. 2026-07-04 12:16 UTCMITRE cvelistV5
  10. 2026-07-04 11:03 UTCEG score recompute
  11. 2026-07-04 11:03 UTCGHSA enrichment
  12. 2026-07-04 06:31 UTCEPSS rescore
  13. 2026-07-04 06:31 UTCEPSS rescore
  14. 2026-07-01 16:05 UTCEG score recompute
  15. 2026-07-01 16:04 UTCGHSA enrichment

Frequently asked(4)

What is CVE-2026-53327?
CVE-2026-53327 is a none vulnerability published on July 1, 2026. In the Linux kernel, the following vulnerability has been resolved: debugobjects: Do not fillpool() if piblocked_on On RT enabled kernels, fillpool() ends up calling rtlocklock(), which asserts if current::piblockedon is set, because a task can obviously only block on one lock as otherwise the…
When was CVE-2026-53327 disclosed?
CVE-2026-53327 was first published in the National Vulnerability Database on July 1, 2026, with the most recent update on July 4, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53327 actively exploited?
CVE-2026-53327 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 6.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2026-53327?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53327, 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

Explore the affected products and dependency analysis for CVE-2026-53327

Explore →

Is Your Infrastructure Affected by CVE-2026-53327?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs