CVE-2026-40337
Privilege Escalation and DoS via IRQ Interaction in Sentry Kernel
Publication date: 2026-04-18
Last updated on: 2026-04-18
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| camelot_os | sentry_kernel | 0.4.7 |
| camelot_os | sentry_kernel | to 0.4.7 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-283 | The product does not properly verify that a critical resource is owned by the proper entity. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The vulnerability exists in the Sentry kernel, a high security micro-kernel used in embedded systems. Specifically, tasks that have DEV or IO capabilities can interact with another task's IRQ line through the __sys_int_* syscall family. Before version 0.4.7, this interaction could lead to denial of service (DoS) attacks and covert channels between the task and the outside world.
How can this vulnerability impact me? :
This vulnerability can impact you by allowing a task with DEV or IO capabilities to cause denial of service (DoS) conditions within the system. Additionally, it can create covert channels that may leak information between the affected task and external entities, potentially compromising system security.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, upgrade the Sentry kernel to version 0.4.7 or later where the patch is applied.
As a workaround before upgrading, reduce the number of tasks that have the DEV and IO capability to a single one to limit the risk of DoS and covert channels.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows a task with DEV or IO capability to interact with another task's IRQ line, potentially leading to denial of service (DoS) and covert channels. This could impact the integrity and availability of the system.
However, there is no specific information provided about how this vulnerability directly affects compliance with common standards and regulations such as GDPR or HIPAA.