How many CVEs have patched complete_delayable_msg?

1 published CVEs changed complete_delayable_msg in zephyrproject-rtos/zephyr, in 1 distinct patches totalling 48 changed lines, between 2026 and 2026.

What is the latest CVE that changed complete_delayable_msg?

CVE-2026-19936 (Bluetooth Mesh delayable message queue: unsynchronized list access leads to NULL pointer dereference), published 2026-10-12, changed lines 194 to 258 of subsys/bluetooth/mesh/delayable_msg.c.

How does complete_delayable_msg compare to the rest of zephyrproject-rtos/zephyr?

zephyrproject-rtos/zephyr has 186 CVEs with a located fix in total; 1 of them changed complete_delayable_msg.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Security data

Weaknesses (CWE)The MITRE CWE weakness catalog
Attack Patterns (CAPEC)MITRE CAPEC attack patterns
CNAsNumbering authorities and report cards
VendorsVulnerabilities by vendor
Patched FunctionsWhere CVE fixes land in code

Tools

CVSS CalculatorScore CVSS 4.0, 3.1, 3.0 & 2.0
Badge BuilderEmbeddable SVG badges for READMEs

Resources

LearnSecurity guides
Data SourcesCVE data sources

About Blog Pricing Demo

Home
Patched Functions
Zephyrproject Rtos
Zephyr
Complete_delayable_msg

RadicalNotion.AI

We do not sell or share your personal information.

Security Data

CWE Directory
CAPEC Directory
CNA Directory
CNA Leaderboard
CNA Report Cards
Vendor Directory
Patched Functions
Data Sources

Calculators

CVSS Calculator
CVSS 4.0
CVSS 3.1
CVSS 3.0
CVSS 2.0
Badge Builder

Platform

My Vulnerabilities
Insights
Notifications
Pricing

Learn

Guides
What is a CVE?
What is CVSS?
The CISA KEV catalog
What is EPSS?

Company

About
Blog
Careers
Contact
Demo

Account

Legal

Security
Privacy
Terms

RadicalNotion.AI

Security data

Weaknesses (CWE)The MITRE CWE weakness catalog
Attack Patterns (CAPEC)MITRE CAPEC attack patterns
CNAsNumbering authorities and report cards
VendorsVulnerabilities by vendor
Patched FunctionsWhere CVE fixes land in code

Tools

CVSS CalculatorScore CVSS 4.0, 3.1, 3.0 & 2.0
Badge BuilderEmbeddable SVG badges for READMEs

Resources

LearnSecurity guides
Data SourcesCVE data sources

About Blog Pricing Demo

Home
Patched Functions
Zephyrproject Rtos
Zephyr
Complete_delayable_msg

complete_delayable_msg in zephyrproject-rtos/zephyr: Patched by 1 CVEs

zephyrproject-rtos/zephyr

Function

complete_delayable_msg

Name: complete_delayable_msg in zephyrproject-rtos/zephyr: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

subsys/bluetooth/mesh/delayable_msg.c

Last patched October 12, 2026

CVEs

That changed this function

Distinct patches

Backports counted once

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

complete_delayable_msg in zephyrproject-rtos/zephyr was changed by 1 published CVE fixes in 2026, in 1 distinct patches that added or removed 48 lines in total.

zephyrproject-rtos/zephyr has 186 CVEs with a located fix in total, so 1% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed complete_delayable_msg, newest first, with the lines each fix touched.

Bluetooth Mesh delayable message queue: unsynchronized list access leads to NULL pointer dereference
CVE-2026-19936 · lines 194–258 · +46 −2
Medium · CVSS 4.8
EPSS 0.1%2026-10-12

Get an alert when the next CVE fix lands in zephyrproject-rtos/zephyr, with the patched functions.

Monitor zephyr CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

1blocksubsys/bluetooth/mesh/delayable_msg.c1 CVEs · 1 patches2026
2push_msg_from_delayable_msgssubsys/bluetooth/mesh/delayable_msg.c1 CVEs · 1 patches2026
3release_delayable_msg_ctxsubsys/bluetooth/mesh/delayable_msg.c1 CVEs · 1 patches2026
4reschedule_delayable_msgsubsys/bluetooth/mesh/delayable_msg.c1 CVEs · 1 patches2026

Other hotspots in the repository

Functions in zephyrproject-rtos/zephyr changed by the most CVE fixes.

wg_process_data_message3 CVEs · subsys/net/lib/wireguard/wg_crypto.c z_impl_updatehub_probe3 CVEs · subsys/mgmt/updatehub/updatehub.c publish_decode3 CVEs · subsys/net/lib/mqtt/mqtt_decoder.c packet_length_decode3 CVEs · subsys/net/lib/mqtt/mqtt_decoder.c updatehub_probe2 CVEs · lib/updatehub/updatehub.c start_coap_client2 CVEs · lib/updatehub/updatehub.c

All patched functions in zephyrproject-rtos/zephyr

Frequently asked questions

Common questions about CVE fixes to complete_delayable_msg.

How many CVEs have patched complete_delayable_msg?: 1 published CVEs changed complete_delayable_msg in zephyrproject-rtos/zephyr, in 1 distinct patches totalling 48 changed lines, between 2026 and 2026.
What is the latest CVE that changed complete_delayable_msg?: CVE-2026-19936 (Bluetooth Mesh delayable message queue: unsynchronized list access leads to NULL pointer dereference), published 2026-10-12, changed lines 194 to 258 of subsys/bluetooth/mesh/delayable_msg.c.
How does complete_delayable_msg compare to the rest of zephyrproject-rtos/zephyr?: zephyrproject-rtos/zephyr has 186 CVEs with a located fix in total; 1 of them changed complete_delayable_msg.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

subsys/bluetooth/mesh/delayable_msg.c on GitHub (opens in a new tab)
All patched functions in zephyrproject-rtos/zephyr
Patched functions directory

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track zephyrproject-rtos/zephyr CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing

On this page

Overview
CVEs that patched it
Other functions in these files
Other hotspots in the repository
FAQ
References