Kernel-memory disclosure via queue-set type confusion
Published Aug 21, 2026 · Updated Aug 21, 2026
Out-of-bounds read in FreeRTOS Kernel 7.4.0 through 11.3.0 allows local users to read privileged kernel memory through queue sets. xQueueAddToSet() accepts a non-conforming handle without validating its type, and a later queue-set operation treats that memory as the wrong structure and copies over-read bytes into application-readable storage. An unprivileged task can reach the disclosure only on MPU-enabled ports built with configUSE_QUEUE_SETS=1; builds without queue sets are not exposed.
Summary
What happened
Out-of-bounds read in FreeRTOS Kernel 7.4.0 through 11.3.0 allows local users to read privileged kernel memory through queue sets. xQueueAddToSet() accepts a non-conforming handle without validating its type, and a later queue-set operation treats that memory as the wrong structure and copies over-read bytes into application-readable storage. An unprivileged task can reach the disclosure only on MPU-enabled ports built with configUSE_QUEUE_SETS=1; builds without queue sets are not exposed.
The record
- CVE
- CVE-2026-77237
- Published
- Aug 21, 2026
- Updated
- Aug 21, 2026
- Vendor
- FreeRTOS
- Product
- FreeRTOS Kernel
- Classifications
- CWE-843, CWE-125, CAPEC-129, T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 21, 2026CVE publishedPublication date reported by the CVE source.
- Aug 21, 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=7.4.0 <=11.3.0
What conditions does exploitation require?
What is affected?
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