<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="rss.xsl"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Zephyr Project — recent CVEs</title>
    <link>https://vulnogram.org/</link>
    <atom:link href="https://vulnogram.org/rss/zephyr" rel="self" type="application/rss+xml"/>
    <description>Most recent CVEs assigned by Zephyr Project (zephyr).</description>
    <image>
      <url>https://vulnogram.org/seaview/icons/zephyr.png</url>
      <title>Zephyr Project — recent CVEs</title>
      <link>https://vulnogram.org/</link>
    </image>
    <lastBuildDate>Wed, 21 Oct 2026 07:00:06 GMT</lastBuildDate>
    <item>
      <title>CVE-2026-77684 · 5.7 MEDIUM — Bluetooth Classic HFP Hands-Free: TX buffer leak on RFCOMM disconnect leads to permanent Bluetooth denial of service</title>
      <link>https://vulnogram.org/CVE-2026-77684</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-77684</guid>
      <description>The Bluetooth Classic Hands-Free Profile HF role in subsys/bluetooth/host/classic/hfp_hf.c does not release the AT command buffers that are still queued on hf-&gt;tx_pending when the RFCOMM DLC goes down. hfp_hf_disconnected() only cancelled the work it…</description>
      <category>Medium</category>
      <pubDate>Mon, 19 Oct 2026 22:49:41 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-19595 · 6.1 MEDIUM — Zephyr RTIO syscall verifier validates output parameters for read instead of write access</title>
      <link>https://vulnogram.org/CVE-2026-19595</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-19595</guid>
      <description>The user-mode syscall verifier z_vrfy_rtio_cqe_get_mempool_buffer() in subsys/rtio/rtio_syscalls.c validated its two output parameters, buff and buff_len, with K_SYSCALL_MEMORY_READ() rather than K_SYSCALL_MEMORY_WRITE(). Both are pure out-parameters…</description>
      <category>Medium</category>
      <pubDate>Mon, 19 Oct 2026 22:49:40 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-76788 · 8.8 HIGH — Stack out-of-bounds write in the OSDP Control Panel reply parser</title>
      <link>https://vulnogram.org/CVE-2026-76788</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-76788</guid>
      <description>The OSDP Control Panel reply parser cp_decode_response() in subsys/mgmt/osdp/src/osdp_cp.c decodes replies from a Peripheral Device into a stack-allocated struct osdp_event. For the REPLY_KEYPPAD and REPLY_RAW reply types, the payload length is taken…</description>
      <category>High</category>
      <pubDate>Mon, 19 Oct 2026 20:39:22 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-76787 · 5.9 MEDIUM — NULL pointer dereference in the UpdateHub FOTA client when probe metadata omits sha256sum</title>
      <link>https://vulnogram.org/CVE-2026-76787</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-76787</guid>
      <description>The UpdateHub firmware-over-the-air client parses the CoAP probe response with Zephyr&apos;s JSON library in z_impl_updatehub_probe() (subsys/mgmt/updatehub/updatehub.c). The decoder treats every descriptor field as optional — json_obj_parse() returns a b…</description>
      <category>Medium</category>
      <pubDate>Mon, 19 Oct 2026 20:39:20 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-75085 · 4.2 MEDIUM — Out-of-bounds read from received-frame length underflow in the STM32WBA IEEE 802.15.4 driver</title>
      <link>https://vulnogram.org/CVE-2026-75085</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-75085</guid>
      <description>The STM32WBA IEEE 802.15.4 driver in drivers/ieee802154/ieee802154_stm32wba.c computed the packet length of a received frame as pkt_len = rx_frame-&gt;length - IEEE802154_FCS_LENGTH without first checking that the radio-reported length could hold an FCS…</description>
      <category>Medium</category>
      <pubDate>Wed, 14 Oct 2026 16:46:02 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-75084 · 6.8 MEDIUM — Out-of-bounds write in the TI CC1200 IEEE 802.15.4 driver from an unvalidated radio-supplied packet length</title>
      <link>https://vulnogram.org/CVE-2026-75084</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-75084</guid>
      <description>The CC1200 sub-GHz IEEE 802.15.4 driver takes the PHY packet length from the first byte of the radio&apos;s RX FIFO in get_packet_length() and validates it in verify_rxfifo_validity() (drivers/ieee802154/ieee802154_cc1200.c). That validation only enforced…</description>
      <category>Medium</category>
      <pubDate>Wed, 14 Oct 2026 16:46:01 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-19673 · 7.1 HIGH — Out-of-bounds read and net_buf length underflow in Zephyr Ethernet L2 when parsing a truncated VLAN header</title>
      <link>https://vulnogram.org/CVE-2026-19673</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-19673</guid>
      <description>ethernet_recv() in subsys/net/l2/ethernet/ethernet.c validates only that the first net_buf of a received frame holds a plain 14-byte struct net_eth_hdr. When the ethertype is 0x8100 and VLAN is enabled on the interface, the same buffer is reinterpret…</description>
      <category>High</category>
      <pubDate>Wed, 14 Oct 2026 16:45:57 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-75083 · 5.9 MEDIUM — Integer underflow of the radio-reported frame length causes an out-of-bounds write in the NXP KW41Z IEEE 802.15.4 driver</title>
      <link>https://vulnogram.org/CVE-2026-75083</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-75083</guid>
      <description>The receive path of the NXP KW41Z IEEE 802.15.4 driver, kw41z_rx() in drivers/ieee802154/ieee802154_kw41z.c, computed the payload size as pkt_len = len - KW41Z_FCS_LENGTH in a uint8_t, where len is the frame length reported by the radio. The interrup…</description>
      <category>Medium</category>
      <pubDate>Wed, 14 Oct 2026 16:45:56 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-19940 · 6.5 MEDIUM — Bluetooth HFP AG reuses a connection slot while a delayable work item is still armed, corrupting kernel timeout bookkeeping</title>
      <link>https://vulnogram.org/CVE-2026-19940</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-19940</guid>
      <description>The Bluetooth Classic Hands-Free Profile Audio Gateway implementation in subsys/bluetooth/host/classic/hfp_ag.c keeps its struct bt_hfp_ag objects in a static pool indexed by ACL connection index. On link teardown, hfp_ag_disconnected() cancels ag-&gt;t…</description>
      <category>Medium</category>
      <pubDate>Tue, 13 Oct 2026 16:40:10 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-19939 · 6.3 MEDIUM — Bluetooth Classic AVDTP: stale timeout work on signalling-channel disconnect leads to kernel timeout-list corruption</title>
      <link>https://vulnogram.org/CVE-2026-19939</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-19939</guid>
      <description>The AVDTP signalling layer arms a 6-second command timeout (AVDTP_TIMEOUT) in avdtp_send_cmd() whenever the local device issues an AVDTP request. Every response handler in subsys/bluetooth/host/classic/avdtp.c cancels session-&gt;timeout_work before cle…</description>
      <category>Medium</category>
      <pubDate>Tue, 13 Oct 2026 16:39:16 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-19938 · 5.9 MEDIUM — Use-after-free of an ATT PDU buffer when signing an outgoing Bluetooth ATT Signed Write Command fails</title>
      <link>https://vulnogram.org/CVE-2026-19938</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-19938</guid>
      <description>The Bluetooth host&apos;s ATT transmit path releases a buffer it does not own when signing fails. chan_send() in subsys/bluetooth/host/att.c documents (and every other error exit implements) the contract that on failure the caller retains ownership of the…</description>
      <category>Medium</category>
      <pubDate>Mon, 12 Oct 2026 23:19:55 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-19937 · 5.7 MEDIUM — Bluetooth Mesh Access layer permanently leaks delayable-message contexts, disabling all model responses</title>
      <link>https://vulnogram.org/CVE-2026-19937</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-19937</guid>
      <description>The Bluetooth Mesh Access layer delayable-message machinery in subsys/bluetooth/mesh/delayable_msg.c manages a static pool of CONFIG_BT_MESH_ACCESS_DELAYABLE_MSG_COUNT message contexts (default 4) threaded onto a free_ctx or busy_ctx list. release_de…</description>
      <category>Medium</category>
      <pubDate>Mon, 12 Oct 2026 23:19:54 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-19936 · 4.8 MEDIUM — Bluetooth Mesh delayable message queue: unsynchronized list access leads to NULL pointer dereference</title>
      <link>https://vulnogram.org/CVE-2026-19936</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-19936</guid>
      <description>The Bluetooth Mesh Access-layer delayable message queue in subsys/bluetooth/mesh/delayable_msg.c shares three intrusive lists (busy_ctx, free_ctx, free_chunks) and one k_work_delayable between two cooperative threads with no synchronization: bt_mesh_…</description>
      <category>Medium</category>
      <pubDate>Mon, 12 Oct 2026 23:19:53 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-19740 · 6.5 MEDIUM — Bluetooth LE Controller: retained RX node leak and reachable assertion in the PHY Update procedure</title>
      <link>https://vulnogram.org/CVE-2026-19740</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-19740</guid>
      <description>The Link Layer Control Procedure (LLCP) implementation of the Zephyr software Bluetooth LE Controller retains the receive node that carried an accepted LL_PHY_UPDATE_IND so that it can later be reused for the host notification when the update instant…</description>
      <category>Medium</category>
      <pubDate>Sun, 11 Oct 2026 17:15:08 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-19739 · 6.5 MEDIUM — Bluetooth LE controller leaks a retained RX node when an unexpected LL Control PDU arrives during a Connection Update</title>
      <link>https://vulnogram.org/CVE-2026-19739</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-19739</guid>
      <description>The Bluetooth Link Layer control procedure code in subsys/bluetooth/controller/ll_sw/ull_llcp_conn_upd.c retains the received RX node while a Connection Update / Connection Parameter procedure waits for its instant, so the node can later carry the ho…</description>
      <category>Medium</category>
      <pubDate>Sun, 11 Oct 2026 17:15:06 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-19738 · 6.5 MEDIUM — Retained RX node leak and reachable assertion in Bluetooth Controller CIS Create procedures</title>
      <link>https://vulnogram.org/CVE-2026-19738</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-19738</guid>
      <description>The Bluetooth Link Layer Control Procedure (LLCP) implementation for Connected Isochronous Stream (CIS) creation retains an RX node (ctx-&gt;node_ref.rx, marked NODE_RX_TYPE_RETAIN) so it can later be reused as the host notification — on the peripheral…</description>
      <category>Medium</category>
      <pubDate>Sun, 11 Oct 2026 17:15:04 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-19935 · 7.5 HIGH — Use-after-free of an L2CAP CoC channel object in the Zephyr Bluetooth host: RX work item is not cancelled on channel teardown</title>
      <link>https://vulnogram.org/CVE-2026-19935</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-19935</guid>
      <description>The Bluetooth LE host queues received L2CAP connection-oriented channel (CoC) data for deferred processing through a struct k_work embedded in the channel object (le_chan-&gt;rx_work, handler l2cap_rx_process()) whenever the channel uses a dynamic PSM (…</description>
      <category>High</category>
      <pubDate>Sun, 11 Oct 2026 17:15:03 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-19737 · 5.5 MEDIUM — NULL pointer dereference in the ESP32 I2S driver when triggering an unsupported direction</title>
      <link>https://vulnogram.org/CVE-2026-19737</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-19737</guid>
      <description>i2s_esp32_trigger_check() in drivers/i2s/i2s_esp32.c validates the requested direction only for I2S_DIR_BOTH. The I2S_DIR_RX and I2S_DIR_TX branches read dev_cfg-&gt;rx.data-&gt;configured / dev_cfg-&gt;tx.data-&gt;configured without first checking the stream po…</description>
      <category>Medium</category>
      <pubDate>Sun, 11 Oct 2026 17:15:01 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-18418 · 3.4 LOW — Out-of-bounds read when the zbus proxy agent IPC backend logs a rejected peer frame&apos;s channel name</title>
      <link>https://vulnogram.org/CVE-2026-18418</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-18418</guid>
      <description>The zbus proxy agent IPC backend in subsys/zbus/proxy_agent/zbus_proxy_agent_ipc.c logged the channel name of a rejected inter-domain frame with a plain %s conversion. The frame type struct zbus_proxy_msg carries a fixed-size channel_name[] array as…</description>
      <category>Low</category>
      <pubDate>Sun, 11 Oct 2026 17:15:00 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-19736 · 7.8 HIGH — Out-of-bounds write in the NXP MCUX TRNG entropy driver for non-word-multiple request lengths</title>
      <link>https://vulnogram.org/CVE-2026-19736</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-19736</guid>
      <description>The NXP MCUX TRNG entropy driver in drivers/entropy/entropy_mcux_trng.c passed the caller&apos;s byte count straight to the vendor SDK routine TRNG_GetRandomData(). On i.MX RT5xx and RT6xx parts the SDK compiles its TRNG_SW_HEALTH_TESTS variant, which alw…</description>
      <category>High</category>
      <pubDate>Sun, 11 Oct 2026 17:14:58 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-19735 · 4.8 MEDIUM — Predictable TCP initial sequence numbers when the RFC 6528 secret key generation fails silently in the Zephyr TCP stack</title>
      <link>https://vulnogram.org/CVE-2026-19735</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-19735</guid>
      <description>The RFC 6528 initial-sequence-number implementation in subsys/net/ip/tcp.c derived every TCP ISN from SHA-256(unique_key || four-tuple) plus a uptime-derived offset, where unique_key is a 128-bit secret filled once by sys_csrand_get(). The return val…</description>
      <category>Medium</category>
      <pubDate>Sun, 11 Oct 2026 17:14:56 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-19577 · 7.1 HIGH — Out-of-bounds read in IPv6 route forwarding when the nexthop neighbor has no link-layer address</title>
      <link>https://vulnogram.org/CVE-2026-19577</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-19577</guid>
      <description>net_route_ipv6_packet() in subsys/net/ip/route_ipv6.c resolved the nexthop&apos;s link-layer address with net_nbr_get_lladdr(nbr-&gt;idx) without first checking whether the neighbor cache entry actually had a linked link-layer address. An unresolved neighbor…</description>
      <category>High</category>
      <pubDate>Sun, 11 Oct 2026 17:14:55 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-19576 · 6.8 MEDIUM — Stack out-of-bounds write in the Goodix GT911 touch controller driver from an unvalidated device-reported touch point count</title>
      <link>https://vulnogram.org/CVE-2026-19576</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-19576</guid>
      <description>The Goodix GT9xx input driver in drivers/input/input_gt911.c reads the touch point count from the controller&apos;s status register and masks it with GT911_TOUCH_POINTS_MSK (0x0F), yielding a value of 0..15. In gt911_process() that value is used directly…</description>
      <category>Medium</category>
      <pubDate>Sun, 11 Oct 2026 17:14:53 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-19669 · 7.8 HIGH — Unbounded variable-length array in fuel gauge syscall verifiers allows kernel stack overflow from user mode</title>
      <link>https://vulnogram.org/CVE-2026-19669</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-19669</guid>
      <description>The user-mode syscall verifiers z_vrfy_fuel_gauge_get_props() and z_vrfy_fuel_gauge_set_props() in drivers/fuel_gauge/fuel_gauge_syscall_handlers.c declared two variable-length arrays, union fuel_gauge_prop_val k_vals[len] and fuel_gauge_prop_t k_pro…</description>
      <category>High</category>
      <pubDate>Sun, 11 Oct 2026 17:14:51 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-19575 · 7.8 HIGH — Type confusion in the device_deinit system call allows user-mode threads to execute arbitrary kernel code</title>
      <link>https://vulnogram.org/CVE-2026-19575</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-19575</guid>
      <description>The user-mode verification handler for the device_deinit() system call, z_vrfy_device_deinit() in kernel/device.c, validated its dev argument with K_SYSCALL_OBJ_INIT(dev, K_OBJ_ANY). k_object_validate() short-circuits its type comparison when the req…</description>
      <category>High</category>
      <pubDate>Fri, 09 Oct 2026 07:16:47 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-19569 · 8.8 HIGH — Integer overflow in dynamic kernel object allocation allows user-mode threads to corrupt the kernel heap</title>
      <link>https://vulnogram.org/CVE-2026-19569</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-19569</guid>
      <description>dynamic_object_create() in kernel/userspace/userspace.c computed the backing allocation for a dynamically allocated kernel object as obj_size_get(otype) + size, and for thread stack elements as STACK_ELEMENT_DATA_SIZE(size) (a round-up plus fixed ove…</description>
      <category>High</category>
      <pubDate>Fri, 09 Oct 2026 07:16:45 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-19574 · 7 HIGH — ARM64 MMU can assign an in-use ASID to a new memory domain, breaking user-mode memory isolation</title>
      <link>https://vulnogram.org/CVE-2026-19574</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-19574</guid>
      <description>The ARM64 MMU back-end allocated address space identifiers (ASIDs) for memory domains with a bare round-robin counter in arch_mem_domain_init() (arch/arm64/core/mmu.c). VM_ASID_BITS is 8, so only 255 ASIDs exist; once the counter wrapped, arch_mem_do…</description>
      <category>High</category>
      <pubDate>Fri, 09 Oct 2026 07:16:43 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-19571 · 6.7 MEDIUM — Race condition in ITE IT8xxx2 SHI host-command backend lets a second SPI request write an unvalidated length into the in-flight request buffer</title>
      <link>https://vulnogram.org/CVE-2026-19571</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-19571</guid>
      <description>The ITE IT8xxx2 SHI host-command backend (subsys/mgmt/ec_host_cmd/backends/ec_host_cmd_backend_shi_ite.c) copied the 8-byte host-command request header from the SPI Rx FIFO directly into the shared receive buffer data-&gt;in_msg and only afterwards chec…</description>
      <category>Medium</category>
      <pubDate>Fri, 09 Oct 2026 07:16:40 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-19570 · 8.8 HIGH — Out-of-bounds write in LE Audio Broadcast Sink when copying BASE subgroup metadata into the BASS receive state</title>
      <link>https://vulnogram.org/CVE-2026-19570</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-19570</guid>
      <description>The LE Audio Broadcast Sink in subsys/bluetooth/audio/bap_broadcast_sink.c copies subgroup metadata from a received Basic Audio Announcement (BASE) into the static Broadcast Audio Scan Service parameter structure mod_src_param without any bounds chec…</description>
      <category>High</category>
      <pubDate>Fri, 09 Oct 2026 07:16:38 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-15894 · 8.8 HIGH — Bluetooth Mesh solicitation PDU stack buffer overflow via oversized advertisement</title>
      <link>https://vulnogram.org/CVE-2026-15894</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-15894</guid>
      <description>The Bluetooth Mesh On-Demand Private Proxy solicitation handler in subsys/bluetooth/mesh/solicitation.c copies a received Solicitation PDU into a fixed 17-byte stack buffer without bounding the source length. In sol_pdu_decrypt(), out is allocated as…</description>
      <category>High</category>
      <pubDate>Wed, 07 Oct 2026 08:55:25 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-19186 · 8.1 HIGH — Integer underflow in IEEE 802.15.4 frame decryption leads to out-of-bounds read and write</title>
      <link>https://vulnogram.org/CVE-2026-19186</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-19186</guid>
      <description>ieee802154_decipher_data_frame() in subsys/net/l2/ieee802154/ieee802154_frame.c computed payload_len = net_pkt_get_len(pkt) - ll_hdr_len - authtag_len without first checking that the received frame is at least ll_hdr_len + authtag_len bytes long. All…</description>
      <category>High</category>
      <pubDate>Wed, 07 Oct 2026 08:55:22 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-19185 · 7.8 HIGH — Unvalidated user-supplied buffer pointers in the I3C do_ccc system call handler allow kernel memory read/write from user mode</title>
      <link>https://vulnogram.org/CVE-2026-19185</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-19185</guid>
      <description>The system-call verifier for i3c_do_ccc() in drivers/i3c/i3c_handlers.c validated the outer struct i3c_ccc_payload, the broadcast ccc.data buffer and the targets.payloads[] array, but did not validate the per-target data buffers those array elements…</description>
      <category>High</category>
      <pubDate>Mon, 05 Oct 2026 08:06:29 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-19184 · 8.4 HIGH — Out-of-bounds write in the NXP GAU ADC driver due to byte-versus-sample buffer size validation mismatch</title>
      <link>https://vulnogram.org/CVE-2026-19184</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-19184</guid>
      <description>The NXP GAU ADC driver (drivers/adc/adc_mcux_gau_adc.c) validated the caller-supplied sequence-&gt;buffer_size, which is expressed in bytes, against the number of active channels, which is a sample count. It then stored that byte count directly in data-…</description>
      <category>High</category>
      <pubDate>Mon, 05 Oct 2026 08:06:22 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-17053 · 4.4 MEDIUM — SMBus callback-removal syscalls accept an unvalidated user pointer, letting user threads manipulate kernel callback state</title>
      <link>https://vulnogram.org/CVE-2026-17053</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-17053</guid>
      <description>The SMBus driver API exposed smbus_smbalert_remove_cb() and smbus_host_notify_remove_cb() as Zephyr syscalls. Their verifiers in drivers/smbus/smbus_handlers.c validated only the dev argument with K_SYSCALL_OBJ(dev, K_OBJ_DRIVER_SMBUS) and forwarded…</description>
      <category>Medium</category>
      <pubDate>Thu, 01 Oct 2026 15:08:52 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-18747 · 6.8 MEDIUM — Integer underflow of net_buf length in the MCUmgr serial (SMP over console) transport leads to out-of-bounds read</title>
      <link>https://vulnogram.org/CVE-2026-18747</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-18747</guid>
      <description>The MCUmgr SMP-over-console transport decodes a base64 frame, reads a 16-bit packet length from it, verifies a CRC and then unconditionally strips the trailing CRC with rx_ctxt-&gt;nb-&gt;len -= 2U; in mcumgr_serial_process_frag() (subsys/mgmt/mcumgr/trans…</description>
      <category>Medium</category>
      <pubDate>Mon, 28 Sep 2026 23:25:26 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-18746 · 5.9 MEDIUM — NULL pointer dereference in Zephyr LwM2M client when the CoAP Block1 context pool is exhausted</title>
      <link>https://vulnogram.org/CVE-2026-18746</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-18746</guid>
      <description>parse_write_op() in subsys/net/lib/lwm2m/lwm2m_message_handling.c handles inbound CoAP WRITE/CREATE requests that carry a Block1 option. For the first block of a transfer it called init_block_ctx() and then immediately stored the peer-selected block…</description>
      <category>Medium</category>
      <pubDate>Mon, 28 Sep 2026 23:25:24 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-18417 · 6.5 MEDIUM — Wild pointer dereference in Zephyr BSD sockets when a TCP listening socket reports an asynchronous error</title>
      <link>https://vulnogram.org/CVE-2026-18417</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-18417</guid>
      <description>The native BSD-socket layer recorded a pending asynchronous socket error by type-punning it into struct net_context&apos;s void user_data field (ctx-&gt;user_data = INT_TO_POINTER(-status) in zsock_accepted_cb(), zsock_received_cb(), zsock_connected_cb() and…</description>
      <category>Medium</category>
      <pubDate>Mon, 28 Sep 2026 23:25:23 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-18416 · 3.7 LOW — Out-of-bounds read in CoAP well-known-core Uri-Query href matching (match_path_uri)</title>
      <link>https://vulnogram.org/CVE-2026-18416</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-18416</guid>
      <description>The CoAP link-format helper match_path_uri() in subsys/net/lib/coap/coap_link_format.c compares a registered resource path against the URI carried in a Uri-Query href= option. That URI is not NUL terminated, but the inner character loop advanced its…</description>
      <category>Low</category>
      <pubDate>Mon, 28 Sep 2026 20:00:02 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-18415 · 6.3 MEDIUM — Out-of-bounds write in the IEEE 802.15.4 L2 transmit path for oversized non-6LoWPAN frames</title>
      <link>https://vulnogram.org/CVE-2026-18415</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-18415</guid>
      <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 whenev…</description>
      <category>Medium</category>
      <pubDate>Mon, 28 Sep 2026 20:00:01 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-18414 · 7.8 HIGH — Out-of-bounds write in the ADI MAX32 ADC driver due to incorrect adc_sequence buffer size validation</title>
      <link>https://vulnogram.org/CVE-2026-18414</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-18414</guid>
      <description>The ADC API requires each driver to reject a sampling sequence whose destination buffer is too small: the buffer_size field of struct adc_sequence in include/zephyr/drivers/adc.h documents that &quot;the driver must ensure that samples are not written bey…</description>
      <category>High</category>
      <pubDate>Mon, 28 Sep 2026 20:00:00 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-18413 · 7.8 HIGH — Out-of-bounds write in the NXP MCUX LPADC ADC driver due to missing adc_sequence buffer size validation</title>
      <link>https://vulnogram.org/CVE-2026-18413</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-18413</guid>
      <description>The ADC API requires each driver to reject a sampling sequence whose destination buffer is too small: the buffer_size field of struct adc_sequence in include/zephyr/drivers/adc.h documents that &quot;the driver must ensure that samples are not written bey…</description>
      <category>High</category>
      <pubDate>Mon, 28 Sep 2026 19:59:58 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-16513 · 7.8 HIGH — Missing write validation of user-supplied handle pointer in the RTIO syscall verifier allows arbitrary kernel write</title>
      <link>https://vulnogram.org/CVE-2026-16513</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-16513</guid>
      <description>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 ite…</description>
      <category>High</category>
      <pubDate>Mon, 28 Sep 2026 19:59:57 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-17054 · 5.3 MEDIUM — Out-of-bounds read and permanent loss of Wi-Fi reception in the ESP-hosted SPI driver&apos;s frame reassembly</title>
      <link>https://vulnogram.org/CVE-2026-17054</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-17054</guid>
      <description>The Espressif ESP-hosted Wi-Fi driver (drivers/wifi/esp_hosted/) parses frames received over SPI from the ESP co-processor in esp_hosted_event_task(). For control frames it took the 16-bit TLV field data_length straight off the wire and passed it to…</description>
      <category>Medium</category>
      <pubDate>Mon, 21 Sep 2026 21:16:05 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-15890 · 5.3 MEDIUM — AEAD nonce reuse in Zephyr secure_storage ITS default nonce provider due to missing thread synchronization</title>
      <link>https://vulnogram.org/CVE-2026-15890</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-15890</guid>
      <description>The default AEAD nonce provider for the PSA Internal Trusted Storage transform module, secure_storage_its_transform_aead_get_nonce() in subsys/secure_storage/src/its/transform/aead_get.c, stores its nonce counter in unsynchronized function-local stat…</description>
      <category>Medium</category>
      <pubDate>Mon, 21 Sep 2026 21:16:04 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-17052 · 7.8 HIGH — Missing user-pointer validation in tgpio_pin_read_ts_ec syscall handler allows arbitrary supervisor-memory write from userspace</title>
      <link>https://vulnogram.org/CVE-2026-17052</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-17052</guid>
      <description>The Time-aware GPIO syscall verification handler z_vrfy_tgpio_pin_read_ts_ec() in drivers/timeaware_gpio/timeaware_gpio_handlers.c validated only the port device object and passed the caller-supplied timestamp and event_count output pointers to the d…</description>
      <category>High</category>
      <pubDate>Mon, 21 Sep 2026 18:35:30 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-17051 · 6 MEDIUM — Out-of-bounds write in the Intel SEDI IPM driver from an unvalidated inbound doorbell length</title>
      <link>https://vulnogram.org/CVE-2026-17051</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-17051</guid>
      <description>The Intel SEDI IPM (inter-processor mailbox) driver in drivers/ipm/ipm_sedi.c handles an inbound message interrupt in ipm_event_dispose(). It read the peer-written doorbell register, extracted the payload length with IPC_HEADER_GET_LENGTH(), and pass…</description>
      <category>Medium</category>
      <pubDate>Mon, 21 Sep 2026 16:41:24 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-17050 · 5.7 MEDIUM — Double free of the USB host configuration descriptor when device enumeration fails</title>
      <link>https://vulnogram.org/CVE-2026-17050</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-17050</guid>
      <description>The experimental USB host stack allocates a per-device configuration-descriptor buffer, udev-&gt;cfg_desc, from the dedicated usb_device_heap in usbh_device_set_configuration() (subsys/usb/host/usbh_device.c). On three failure paths — a failed full-leng…</description>
      <category>Medium</category>
      <pubDate>Mon, 21 Sep 2026 16:41:23 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-16515 · 4.7 MEDIUM — ICMPv6 error messages sent for multicast-destined packets and non-unique source addresses enable network amplification in Zephyr&apos;s IPv6 stack</title>
      <link>https://vulnogram.org/CVE-2026-16515</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-16515</guid>
      <description>net_icmpv6_send_error() in subsys/net/ip/icmpv6.c implemented only one of the three RFC 4443 section 2.4 suppression rules (do not answer an ICMPv6 error with an ICMPv6 error). It did not check whether the triggering packet&apos;s source address identifie…</description>
      <category>Medium</category>
      <pubDate>Fri, 18 Sep 2026 14:30:13 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-16514 · 4.3 MEDIUM — Out-of-bounds read in gPTP Announce path-trace validation via unvalidated stepsRemoved</title>
      <link>https://vulnogram.org/CVE-2026-16514</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-16514</guid>
      <description>gptp_mi_qualify_announce() in subsys/net/l2/ethernet/gptp/gptp_mi.c walks the Path Trace TLV of a received IEEE 802.1AS Announce message, comparing each clock identity against the local one. The loop bound was taken solely from the attacker-controlle…</description>
      <category>Medium</category>
      <pubDate>Fri, 18 Sep 2026 14:30:11 GMT</pubDate>
    </item>
    <item>
      <title>CVE-2026-16512 · 3.1 LOW — Out-of-bounds read in the Zephyr gPTP receive path when handling short Ethernet frames</title>
      <link>https://vulnogram.org/CVE-2026-16512</link>
      <guid isPermaLink="true">https://vulnogram.org/CVE-2026-16512</guid>
      <description>gptp_handle_msg() in subsys/net/l2/ethernet/gptp/gptp.c dereferenced the gPTP header returned by GPTP_HDR() and switched on hdr-&gt;message_type without first checking that the received frame carries at least sizeof(struct gptp_hdr) (34) bytes of payloa…</description>
      <category>Low</category>
      <pubDate>Fri, 18 Sep 2026 14:30:10 GMT</pubDate>
    </item>
  </channel>
</rss>
