CVE-2026-64073
7.8 · HIGHOverview
CVE-2026-64073 is a high-severity vulnerability. It was published on July 19, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).
This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.
Technical Description
In the Linux kernel, the following vulnerability has been resolved:
irq_work: Fix use-after-free in irq_work_single() on PREEMPT_RT
On PREEMPT_RT, non-HARD irq_work runs in per-CPU kthreads via
run_irq_workd(), so irq_work_sync() uses rcuwait() to wait for BUSY==0.
After irq_work_single() clears BUSY via atomic_cmpxchg(), it still
dereferences @work for irq_work_is_hard() and rcuwait_wake_up().
An irq_work_sync() caller on another CPU that enters after BUSY is cleared
can observe BUSY==0 immediately, return, and free the work before those
accesses complete — causing a use-after-free.
Fix this by wrapping run_irq_workd() in guard(rcu)() so that the entire
irq_work_single() execution is within an RCU read-side critical
section. Then add synchronize_rcu() in irq_work_sync() after
rcuwait_wait_event() to ensure the caller waits for the RCU grace period
before returning, preventing premature frees.
Remediation
Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.
References
Frequently Asked Questions
What is CVE-2026-64073?
CVE-2026-64073 is a high-severity vulnerability. It was published on July 19, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).
How severe is CVE-2026-64073?
This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.
How do I fix or remediate CVE-2026-64073?
Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.
How can CyberStrike help with CVE-2026-64073?
CyberStrike's AI-powered security agents can automatically detect CVE-2026-64073 across your infrastructure using autonomous pentesting, DAST scanning, and HackBrowser. The platform continuously monitors for known vulnerabilities and provides actionable remediation guidance prioritized by real-world exploitability.
How CyberStrike Helps
AI agents map your attack surface to find vulnerabilities like this one.
Automated penetration testing that runs continuously, not just quarterly.
AI-driven PR review catches vulnerable dependencies before they ship.
Browser-based exploitation validates findings with real proof-of-concept.
Related HIGH CVEs from 2026
View all →H3 is a minimal H(TTP) framework built for high performance and portability. Prior to 1.15.5, there
OpenProject is an open-source, web-based project management software. To enable the real time collab
OpenSift is an AI study tool that sifts through large datasets using semantic search and generative
Budibase is a low code platform for creating internal tools, workflows, and admin panels. In 3.24.0
FileBrowser Quantum is a free, self-hosted, web-based file manager. Prior to 1.3.1-beta and 1.2.2-st
Shopware is an open commerce platform. Prior to 6.6.10.15 and 6.7.8.1, a vulnerability in the Shopwa
ChurchCRM is an open-source church management system. Prior to 7.1.0, a stored cross-site scripting
A Stored Cross-Site Scripting vulnerability was discovered in the Assets and Nodes functionality due
Postiz is an AI social media scheduling tool. Prior to version 2.21.6, a file upload validation bypa
A server-side request forgery (SSRF) vulnerability was identified in GitHub Enterprise Server that a
Cross-Site Scripting (XSS) vulnerability exists in HTMLy version 3.1.1 in the content creation funct
An Improper Certificate Validation in Ivanti EPMM before versions 12.6.1.1, 12.7.0.1, and 12.8.0.1 a