Kernel code execution via uninitialized mqueue inode
Published Mar 11, 2021 · Updated Aug 19, 2026
Kernel code execution in Microsoft Azure Sphere 21.01 allows local users to run unsigned code via crafted message-queue syscalls. The custom kernel's mqueue_alloc_inode function uses kmalloc without calling inode_init_once, leaving i_lru pointers attacker-controlled after heap grooming. Creating and destroying an IPC namespace, or opening a message queue with oversized attributes, reaches the flaw and grants kernel-level execution.
Summary
What happened
Kernel code execution in Microsoft Azure Sphere 21.01 allows local users to run unsigned code via crafted message-queue syscalls. The custom kernel's mqueue_alloc_inode function uses kmalloc without calling inode_init_once, leaving i_lru pointers attacker-controlled after heap grooming. Creating and destroying an IPC namespace, or opening a message queue with oversized attributes, reaches the flaw and grants kernel-level execution.
The record
- CVE
- CVE-2021-27080
- Published
- Mar 11, 2021
- Updated
- Aug 19, 2026
- Vendor
- Microsoft
- Product
- Azure Sphere
- Classifications
- CWE-457, T1068
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 11, 2021CVE publishedPublication date reported by the CVE source.
- Aug 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=-
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
- Azure Sphere mqueue inode trigger demonstrationproof of concept · demonstrated
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