AI Science Tracker

Zephyr RTIO syscall verifier reverses user-buffer memory permission checks

Zephyr RTOS RTIO syscall verifier · AI involvement attributed to Claude (model/version not identified)

Finding and attribution

In `rtio_vrfy_sqe()`, permission-check results from `K_SYSCALL_MEMORY()` were accumulated with the wrong polarity. On builds with CONFIG_USERSPACE and CONFIG_RTIO, an unprivileged user-mode thread with an RTIO context and iodev grant could supply a pointer to kernel memory; the verifier accepted it and a driver dereferenced it in supervisor mode. The advisory describes arbitrary kernel reads through TX, writes through RX, or a kernel fault.

Product: Zephyr RTOS RTIO syscall verifier. AI system: Claude (model/version not identified). Team / organization: Anthropic and Ada Logics; Zephyr Project maintainers.

CVE identifiers: CVE-2026-87041.

AI and human contribution (source account): The primary Zephyr advisory explicitly says Claude, Anthropic’s AI assistant, discovered the vulnerability; Ada Logics performed manual triage and report writing with Anthropic Research.

Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.

Discovery context: The public GHSA was published Nov 4, after the stated Nov 2 embargo. It rates the issue High. Exploitability requires a user-mode thread already granted RTIO access and an image built with CONFIG_USERSPACE and CONFIG_RTIO. No exploitation-in-the-wild claim is made.

Remediation status: fix documented. Fixed in Zephyr 4.3.2 and 4.5.0, with backports merged for v4.4, v4.3 and v3.7 branches. The advisory recommends rejecting nonzero K_SYSCALL_MEMORY results and checking TXRX transmit buffers read-only. Deployment status is not checked.

A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.

Disclosed 4 Nov 2026. AI attribution dated 4 Nov 2026. Sources checked 14 Nov 2026; these are separate dates, not a live installation check.

Recorded CVSS: High · highest recorded score 7.8. Documented technical effects: data disclosure, data modification.

Severity, consequences and exploitation evidence

Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.

CVE-2026-87041: data disclosure, data modification.
Prerequisites / affected scope: A user-mode thread granted an RTIO context/device can submit pointers to arbitrary kernel memory; RTIO RX can write peripheral data to chosen kernel memory and TX can transmit kernel memory over the bus..
Exploitation evidence: The cited source does not establish exploitation in the wild.. Impact source · checked 16 Nov 2026.

Documented fix: Fixed in Zephyr 4.3.2 and 4.5.0, with backports merged for v4.4, v4.3 and v3.7 branches. The advisory recommends rejecting nonzero K_SYSCALL_MEMORY results and checking TXRX transmit buffers read-only. Deployment status is not checked.

Original evidence

Download this source record (JSON)

Open this case in the interactive tracker · Browse all static security cases