Patch Forecast
Yellow warning
Plan into this sprint.

CVE-2026-18415

Zephyrproject Zephyr: out-of-bounds write can lead to denial of service

Risk score
43/100
CVSS
7.1 v3.1
Exploit chance (30 days)
0.1%
Published
28 Sep 2026

Open in the live forecast Today's forecast

What to know

What it is
ieee802154_send() in subsys/net/l2/ieee802154/ieee802154.c copies the outgoing packet into a single fixed 125-byte transmit buffer (tx_frame_buf_pool, sized IEEE802154_MTU). In builds with CONFIG_NET_L2_IEEE802154_FRAGMENT enabled (the default whenever CONFIG_NET_6LO is set), the branch taken when 6LoWPAN fragmentatio…
Affected
Zephyrproject Zephyr
Fix
Apply the vendor's security update; see the linked advisory.
Exploitation
No known exploitation

Story map

Story map: Zephyrproject ZephyrTHE FLAWSTHE FIXCVE-2026-18415Out-of-bounds write can leadto denial of serviceCVSS 7.1 · EPSS 0%CVE-2026-16513Out-of-bounds write can leadto denial of serviceCVSS 7.8 · EPSS 0%CVE-2026-18413Out-of-bounds writeCVSS 7.8 · EPSS 0%CVE-2026-18414Out-of-bounds writeCVSS 7.8 · EPSS 0%Upgrade Zephyrproject…4.3.0or later on your release lineWho is exposedZephyrproject Zephyr before4.3.0YELLOW · PLAN IT INZephyrprojectZephyrThe userspace verifierz_vrfy_rtio_sqe_copy_in_get_handles() insubsys/rtio/rtio_syscalls.c(subsys/rtio/rtio_handlers.cbefore v4.3.0) validated theRTIO object handle and the…Where it standsPublic proof of conceptCONNECTS TOSame weaknessOut-of-bounds write (CWE-787)279 other warnings in 30 days →Same productEarlier Zephyrproject Zephyr warnings1 in the last 90 days →
Story map: the flaws, the fix, how it unfolded and what it connects to. Boxes link to the record or article.

At a glance

Zephyrproject Zephyr: Yellow, plan it in. The userspace verifier z_vrfy_rtio_sqe_copy_in_get_handles() in subsys/rtio/rtio_syscalls.c (subsys/rtio/rtio_handlers.c before v4.3.0) validated the RTIO object handle and the sqes input array, but not the handle out-parameter. On the first loop iteration it executed *handle = sqe, storing the kernel address of the n…

The flaws

  • CVE-2026-18415: Out-of-bounds write can lead to denial of service (CVSS 7.1 · EPSS 0%)
  • CVE-2026-16513: Out-of-bounds write can lead to denial of service (CVSS 7.8 · EPSS 0%)
  • CVE-2026-18413: Out-of-bounds write (CVSS 7.8 · EPSS 0%)
  • CVE-2026-18414: Out-of-bounds write (CVSS 7.8 · EPSS 0%)

The fix

Upgrade Zephyrproject Zephyr: 4.3.0 or later on your release line

Who is exposed: Zephyrproject Zephyr before 4.3.0

Where it stands

  • Public proof of concept

Connects to

Why it is Yellow

  • CVSS 7.1 high

References

Original description

ieee802154_send() in subsys/net/l2/ieee802154/ieee802154.c copies the outgoing packet into a single fixed 125-byte transmit buffer (tx_frame_buf_pool, sized IEEE802154_MTU). In builds with CONFIG_NET_L2_IEEE802154_FRAGMENT enabled (the default whenever CONFIG_NET_6LO is set), the branch taken when 6LoWPAN fragmentation is not required performed an unchecked net_buf_add_mem(frame_buf, pkt_buf->data, pkt_buf->len). The only guard was __ASSERT_NO_MSG() inside net_buf_simple_add(), which is compiled out without CONFIG_ASSERT, so an oversized packet silently overran the frame buffer. The defect is not reachable from the radio: for NET_AF_INET6 packets ieee802154_6lo_encode_pkt() compares the whole packet length against IEEE802154_MTU and takes the fragmentation path when it does not fit, so every buffer copied on the unfragmented branch is within bounds. It is reachable through NET_AF_PACKET sockets bound to an 802.15.4 interface: for NET_SOCK_RAW the 6LoWPAN block is skipped entirely and for NET_SOCK_DGRAM it returns early on the address-family test, leaving no length validation anywhere on the transmit path (net_context_sendto() and net_if_tx() apply none, and pkt_buffer_length() does not clamp the allocation for this L2). An application — or, in a CONFIG_USERSPACE build, an unprivileged application thread using the zsock_socket()/zsock_sendto() syscalls — can therefore drive a supervisor-mode out-of-bounds write of chosen bytes past the 125-byte pool buffer. With the default CONFIG_NET_BUF_FIXED_DATA_SIZE of 128 bytes the overrun is bounded to roughly ll_hdr_len + 3 bytes; with CONFIG_NET_BUF_VARIABLE_DATA_SIZE a single storage buffer can be as large as CONFIG_NET_PKT_BUF_TX_DATA_POOL_SIZE, making the overrun far larger. The consequence is corruption of memory adjacent to the pool, with a crash or further compromise of kernel state as the practical impact. The fix validates ll_hdr_len + net_pkt_get_len(pkt) + authtag_len against IEEE802154_MTU before any copy and adds a tailroom-checking copy_pkt_to_frame() helper that returns -EMSGSIZE instead of overrunning the buffer. The same change also linearizes the whole net_buf chain into one MAC frame, so packet storage boundaries no longer become frame boundaries on the wire.

Last activity 28 Sep 2026. Patch Forecast updates every hour.