Is there a public exploit for CVE-2026-78116?

No public exploit for CVE-2026-78116 was found in Exploit-DB, Metasploit, Nuclei templates or public proof-of-concept repositories. That is an absence of evidence rather than proof that none exists.

How severe is CVE-2026-78116?

CVE-2026-78116 scores CVSS 5.2 (v3.1), rated medium. EPSS puts the chance of exploitation in the next 30 days at 0.21%.

What does CVE-2026-78116 affect?

CVE-2026-78116 affects zephyrproject Zephyr.

5.2 Medium

The Broadcom AFBR-S50 time-of-flight sensor driver double-completes an RTIO submission when sensor data evaluation fails.

CVE-2026-78116

The Broadcom AFBR-S50 time-of-flight sensor driver double-completes an RTIO submission when sensor data evaluation fails. In datareadyworkhandler() (drivers/sensor/broadcom/afbrs50/afbrs50.c), a non-STATUSOK return from ArgusEvaluateData() calls handleerroronresult(), which finalises the request with rtioiodevsqeerr(), but execution then fell through to the tail of the function and finalised the very same struct rtioiodevsqe a second time with rtioiodevsqeok(). Unlike the other error branches in the same function, this one did not return. Both completion helpers reach rtioexecutordone() in subsys/rtio/rtioexecutor.c, which returns the submission to the pool via rtiosqepoolfree() and, for streaming (multishot) submissions, also releases the RX buffer with rtioreleasebuffer(). The second completion therefore reads a freed rtioiodevsqe, pushes the same mpsc node onto the submission queue while it is already on the pool free list — splicing the two lists together — and re-submits the freed request so the next measurement is written through an already-released buffer. For one-shot submissions it emits a spurious success completion carrying stale userdata and frees the same pool entry…

Assessment

CVSS: 5.2 (v3.1)
Severity: Medium
EPSS: 0.21% chance of exploitation in the next 30 days
Known exploited: Not listed in CISA KEV
Exploit availability: Nothing found in Exploit-DB, Metasploit, Nuclei or public PoC repositories
Published: 21 October 2026
Last updated: 4 November 2026
Affected: zephyrproject · Zephyr
Assigner: zephyr

CVSS vectorCVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H

At the source

EUVD (ENISA)

References

Community proofs of concept

No community proof of concept yet. If you have one for a published vulnerability and the right to share it, add it below — it will appear here once reviewed.

Submit a proof of concept

Only for publicly disclosed vulnerabilities, and only material from testing you were authorised to perform. This platform does not buy, sell, or broker exploits — see earning from vulnerability research for legitimate bounty programs. Submissions are reviewed before they appear. Text only; do not include live credentials, personal data, or anything targeting systems you are not permitted to test.

Title *

Proof of concept *

Write-up (optional)

Affected versions (optional)

Name or handle (optional)

References (optional, one URL per line)

Licence for your contribution *

Private contact (optional, never shown)

Before you submit * This vulnerability is already publicly disclosed (it has a published CVE). This material comes only from testing I was authorised to perform. I have the legal right to publish this content and am not breaching any agreement by doing so. It contains no live credentials, personal data, or anything targeting systems I am not authorised to test. I understand it will be reviewed before it appears publicly and may be rejected. I agree to the submission terms.

What is 7 + 8? *

Query this programmatically

Agents can read this through the MCP endpoint, or over HTTP:

curl https://cve.zerocrew.in/api/cve/CVE-2026-78116