Service interruption via unchecked IRQ ownership
Published Apr 17, 2026 · Updated Apr 17, 2026
Unverified IRQ ownership in Camelot-OS Sentry kernel before 0.4.7 allows local users to disrupt tasks via interrupt syscalls. The gate_int_acknowledge, gate_int_disable, and gate_int_enable handlers act on a supplied IRQ without verifying that the current task owns it. A task must hold a DEV or IO capability; it can manipulate another task's IRQ, interrupting service or creating a covert channel across the isolation boundary.
Summary
What happened
Unverified IRQ ownership in Camelot-OS Sentry kernel before 0.4.7 allows local users to disrupt tasks via interrupt syscalls. The gate_int_acknowledge, gate_int_disable, and gate_int_enable handlers act on a supplied IRQ without verifying that the current task owns it. A task must hold a DEV or IO capability; it can manipulate another task's IRQ, interrupting service or creating a covert channel across the isolation boundary.
The record
- CVE
- CVE-2026-40337
- Published
- Apr 17, 2026
- Updated
- Apr 17, 2026
- Vendor
- Camelot-OS
- Product
- Sentry kernel
- Classifications
- CWE-283, T1499.004
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Apr 17, 2026CVE publishedPublication date reported by the CVE source.
- Apr 17, 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=< 0.4.7
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