CVE-2026-9771
Last modified
CVE-2026-9771 is a high-severity vulnerability rated 8.8/10 on the CVSS scale. The flash_copy() system call is verified by z_vrfy_flash_copy() in drivers/flash/flash_util.c. On builds with CONFIG_USERSPACE enabled, this handler is the kernel-side trust boundary for a user-mode caller. EPSS estimates a 0.14% chance of exploitation in the next 30 days.
Description
The flash_copy() system call is verified by z_vrfy_flash_copy() in drivers/flash/flash_util.c. On builds with CONFIG_USERSPACE enabled, this handler is the kernel-side trust boundary for a user-mode caller. Prior to the fix it validated only the output buffer (K_SYSCALL_MEMORY_WRITE) and passed the two struct device * arguments, src_dev and dst_dev, directly into the implementation without any object validation — unlike every sibling flash syscall, which guards its device pointer with K_SYSCALL_DRIVER_FLASH. A user-mode thread fully controls the values of src_dev/dst_dev and the contents of its own address space. The implementation z_impl_flash_copy() dereferences these pointers and calls through their driver-API function tables (e.g. api->get_parameters(dst_dev), flash_read(src_dev, ...), flash_write(dst_dev, ...)). By supplying a pointer to a forged struct device whose api table contains attacker-chosen function pointers, an unprivileged thread can cause the kernel to call arbitrary code in supervisor mode; passing any arbitrary or invalid address otherwise yields a kernel crash or out-of-bounds read. The result is a local privilege escalation out of the userspace sandbox (with kernel denial-of-service and information disclosure as lesser outcomes). The fix adds K_SYSCALL_DRIVER_FLASH(src_dev, read) and K_SYSCALL_DRIVER_FLASH(dst_dev, write) to z_vrfy_flash_copy(), which verify each device is a registered flash-driver kernel object the calling thread is permitted to use before any dereference, closing the path completely.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| zephyrproject | zephyr | >= 4.0.0, < 4.3.2; >= 4.4.0, < 4.4.2 |
References
Timeline
- Published
- Last Modified
- Status
- Awaiting Analysis
Frequently Asked Questions
What is CVE-2026-9771?
How severe is CVE-2026-9771?
How do I fix CVE-2026-9771?
How Strix Helps
- Uncovering a hidden BOLA in Appsmith's snapshot logicStrix autonomously discovered a BOLA/IDOR vulnerability in Appsmith's snapshot deletion path.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-97692BACnet Stack is a BACnet open source protocol stack C librar…7.7
- CVE-2026-97693Yuxi is a large-model-based intelligent knowledge base and k…9.9
- CVE-2026-9770Kasa EC71 v4 and EC70 v4 firmware contains a static cryptogr…5.3
- CVE-2026-97701Zulip is an open-source team collaboration tool. In Zulip Se…6.5
- CVE-2026-97702Open edX Platform enables the authoring and delivery of onli…5.3
- CVE-2026-97705Moleculer is a progressive microservices framework for Node.…7.5
- CVE-2026-97711Serialize JavaScript serializes JavaScript values to a super…2.3
- CVE-2026-97712Sonatype Nexus Repository 3 allows a user that holds the rol…8.7
- CVE-2026-97714CVE-2026-97714 is a is a vulnerability in the authentication…8.2
- CVE-2026-97715CVE-2026-97715 is a vulnerability in the client registration…7.1
- CVE-2026-97716CVE-2026-97716 is a vulnerability in the connection set up s…8.7
- CVE-2026-97717CVE-2026-97717 is a vulnerability in the proxy sub-system of…6
Are you affected by CVE-2026-9771?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
