Kernel crash via dangling interrupt resources
Published Jul 19, 2026 · Updated Jul 19, 2026
Use-after-free in the imgpdc interrupt controller on affected Linux Kernel branches allows local users to crash the kernel after driver removal. pdc_intc_remove() removes the IRQ domain without freeing its generic chips or clearing peripheral and syswake chained handlers, leaving global-list entries and handler pointers to freed driver memory. The imgpdc driver must be present and removed; later suspend, resume, shutdown, or spurious interrupt processing dereferences the stale resources and crashes the host.
Summary
What happened
Use-after-free in the imgpdc interrupt controller on affected Linux Kernel branches allows local users to crash the kernel after driver removal. pdc_intc_remove() removes the IRQ domain without freeing its generic chips or clearing peripheral and syswake chained handlers, leaving global-list entries and handler pointers to freed driver memory. The imgpdc driver must be present and removed; later suspend, resume, shutdown, or spurious interrupt processing dereferences the stale resources and crashes the host.
The record
- CVE
- CVE-2026-63798
- Published
- Jul 19, 2026
- Updated
- Jul 19, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-401, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 19, 2026CVE publishedPublication date reported by the CVE source.
- Jul 19, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.12
- Affected versionversion=b6ef9161e43ad58c3824bd76dc87716276f0cd70 <0405a65e4ebd9eac13a765f9f02ac05851ca5421
- Affected versionversion=b6ef9161e43ad58c3824bd76dc87716276f0cd70 <37738fdf2ab1e504d1c63ce5bc0aeb6452d8f057
- Affected versionversion=b6ef9161e43ad58c3824bd76dc87716276f0cd70 <41826e5297e67cd96a0a46fde06a5069a8ce436a
- Affected versionversion=b6ef9161e43ad58c3824bd76dc87716276f0cd70 <44567537a2623dcd2b4018a7f043cf8069579e5d
- Affected versionversion=b6ef9161e43ad58c3824bd76dc87716276f0cd70 <8176773dfceae7978b01c20b233693e072053700
- Affected versionversion=b6ef9161e43ad58c3824bd76dc87716276f0cd70 <83d7ec14b0938ad8cae008058fd6f912f4a9a312
- Affected versionversion=b6ef9161e43ad58c3824bd76dc87716276f0cd70 <b3a3831b2eb884641906fc5e46207b205b6aea13
- Affected versionversion=b6ef9161e43ad58c3824bd76dc87716276f0cd70 <c2c7733101bb8c0b29ac9ee41073eaf602821a59
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo