Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1336 CNY

100%

CVE-2026-13213— Bluetooth HAS: NULL-pointer dereference DoS when a bonded peer reconnects before bt_has_register

Quick assessment

Affected
zephyrproject zephyr
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

以下是对该漏洞描述信息的中文翻译: 在 文件中,Hearing Access Service (HAS) GATT 服务器无条件地通过 安装了连接回调。这意味着,即使应用程序尚未调用 ,只要建立了安全性连接, 函数就会运行。在服务属性指针 、 和 被 解析并设置 标志之前,这些指针始终保持为 NULL(空指针)。 当启用 配置时, 会在系统启动时恢复每个已配对客户端的持久化上下文,并无条件地将 设置为 (非零值)。如果此前已配对的 peer 在 被调用之前的启动窗口期内重新连接并重新建立安全性, 函数会检测到非零标

CVSS 5.3 · Medium
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-13213

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
Bluetooth HAS: NULL-pointer dereference DoS when a bonded peer reconnects before bt_has_register
Source: CVE Program / CVE List V5
Vulnerability Description
The Hearing Access Service (HAS) GATT server in subsys/bluetooth/audio/has.c installs a connection-callback set unconditionally via BT_CONN_CB_DEFINE, so security_changed() runs for every connection that establishes security even before the application has called bt_has_register(). The service attribute pointers hearing_aid_features_attr, preset_control_point_attr, and active_preset_index_attr remain NULL until bt_has_register() resolves them and sets has.registered. With CONFIG_BT_SETTINGS, settings_set_cb() restores each bonded client's persisted context at boot and unconditionally sets context->flags to BONDED_CLIENT_INIT_FLAGS (non-zero). When a previously bonded peer reconnects and re-establishes security during the startup window before bt_has_register() has been called, security_changed() sees the non-zero flags and schedules notify_work_handler, which calls bt_gatt_is_subscribed() with a still-NULL attribute pointer. That triggers an assertion (__ASSERT(attr, ...) in bt_gatt_is_subscribed()), or a NULL dereference of attr->uuid when assertions are compiled out. The result is a remotely triggerable (Bluetooth, adjacent) crash of the HAS peripheral. Exploitation requires the peer to have previously bonded with the device and to reconnect within the boot-time race window before the application registers the service; a peer that reconnects persistently can prolong the outage. Impact is denial of service only, with no memory corruption or information disclosure. The fix adds an early if (!has.registered) { return; } guard in security_changed(), so no notification work is scheduled until the GATT service is registered and its attribute pointers are valid.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
Source: CVE Program / CVE List V5
Vulnerability Type
空指针解引用
Source: CVE Program / CVE List V5

Affected Products

Vendor Product Affected Versions CPE Subscribe
zephyrproject zephyr 3.6.0 ~ 4.4.2 -

II. Public POCs for CVE-2026-13213

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-13213

登录查看更多情报信息。

Patches & Fixes for CVE-2026-13213 (1)

Vendor Advisories for CVE-2026-13213 (1)

Same Patch Batch · zephyrproject · 2026-08-24 · 4 CVEs total

CVE-2026-13212 8.8 HIGH Zephyr virtio driver calls an arbitrary function pointer from an out-of-range used-ring de
CVE-2026-9728 6.4 MEDIUM TOCTOU race in mbox_send syscall verifier allows userspace to leak kernel memory
CVE-2026-13343 5.3 MEDIUM Uninitialised stack memory disclosure in the MIDI 2.0 UMP Stream responder

IV. Related Vulnerabilities

V. Comments for CVE-2026-13213

No comments yet


Leave a comment