CVE-2026-81038

The Object Transfer Service server builds its Object Action Control Point (OACP) response indication in oacp_ind_send() (subsys/bluetooth/services/ots/ots_oacp.c). Before this fix the four-byte Checksum Value field was appended whenever the requested op code was BT_GATT_OTS_OACP_PROC_CHECKSUM_CALC, regardless of the result code. The response payload is a bare, uninitialized four-byte stack buffer declared with NET_BUF_SIMPLE_DEFINE(resp_param, sizeof(uint32_t)) in bt_gatt_ots_oacp_write(), and it is filled only on the success path of oacp_checksum_proc_validate(). On every failure path the buffer is still empty, so net_buf_simple_pull_le32() was invoked on a zero-length buffer. The OACP characteristic and its client characteristic configuration descriptor are declared with BT_GATT_PERM_WRITE and BT_GATT_PERM_READ | BT_GATT_PERM_WRITE, so no pairing, encryption, or authentication is required. Any peer within radio range that can connect to a device running the OTS server can enable OACP indications and write a nine-byte Calculate Checksum command that fails validation — for example by issuing it with no object selected, which returns BT_GATT_OTS_OACP_RES_INV_OBJ. Because oacp_command_decode() accepts the Calculate Checksum op code unconditionally (it is not guarded by CONFIG_BT_OTS_OACP_CHECKSUM_SUPPORT), builds without checksum support are reachable too: they answer BT_GATT_OTS_OACP_RES_OPCODE_NOT_SUP and take the same bad path. On builds with CONFIG_ASSERT enabled, the zero-length pull trips the assertion inside net_buf_simple_pull_mem() and panics the device, giving a remotely triggered denial of service. On builds with assertions disabled there is no check: the pull returns the untouched stack array and four bytes of uninitialized stack memory are copied into the indication and transmitted to the peer, repeatable on every request. The disclosure is bounded to four bytes per request and the write stays inside the seven-byte res indication buffer, so there is no memory corruption; the impact is uninitialized-memory disclosure plus an availability loss in assertion-enabled configurations.

• CWE-617
• CWE-908

• https://github.com/zephyrproject-rtos/zephyr/commit/36145a6f1164e2e0a18c8c83d5b1be6e7d3f6e23
• https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-7c9w-mhqw-5g86

Published

Oct 26, 2026

Last Modified

Oct 26, 2026

Status

Awaiting Analysis

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2026-81031IDURAR ERP CRM changes the password of whichever account a r…7.2
• CVE-2026-81032NebulaGraph exposes its runtime configuration over an unauth…9.8
• CVE-2026-81033Automatisch reveals whether an address is registered through…5.3
• CVE-2026-81034Netmaker disables certificate verification on the connection…6.5
• CVE-2026-81035Midday allows any member of a team to delete it. The delete …8.1
• CVE-2026-81036Stalwart Mail Server does not compare an OAuth redirect targ…8.1
• CVE-2026-81039The Bluetooth host pre-allocates a bt_conn object (a "reserv…4.3
• CVE-2026-81046Dell ThinOS 10, versions prior to 2605_10.2616, contain a Pr…9.4
• CVE-2026-81048Dell ThinOS 10, versions prior to 2605_10.2616, contain an I…8.8
• CVE-2026-81049Dell ThinOS 10, versions prior to 2605_10.2616, contain a Mi…6.7
• CVE-2026-81051Dell ThinOS 10, versions prior to 2605_10.2616, contain a Se…6.6
• CVE-2026-81052Dell ThinOS 10, versions prior to 2605_10.2616, contain a Do…6.8