Skip to main content
CVE-2026-10651VulnerabilityPublished Updated

Zephyr: bt_sdp_parse_attribute()

Affects zephyrSource GCVE Database

0
Authoritative record:CVE-2026-10651· High 7.1

Not known to be exploited · CVSS 7.1 High.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 3.1 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Ubuntu 26.10zephyrpkg:deb/ubuntu/zephyr?arch=source&distro=stonkingOther threatsAffected
  • =3.1.2-4
Fixed in–
Ubuntu 26.04 LTSzephyrpkg:deb/ubuntu/zephyr?arch=source&distro=resoluteOther threatsAffected
  • =3.1.2-1.1build1
  • =3.1.2-4
Fixed in–
Ubuntu 25.10zephyrpkg:deb/ubuntu/zephyr?arch=source&distro=questingOther threatsAffected
  • =3.1.2-1.1build1
Fixed in–
Ubuntu 24.04 LTSzephyrpkg:deb/ubuntu/zephyr?arch=source&distro=nobleOther threatsAffected
  • =3.1.2-1.1
  • =3.1.2-1.1build1
Fixed in–
Ubuntu 22.04 LTSzephyrpkg:deb/ubuntu/zephyr?arch=source&distro=jammyOther threatsAffected
  • =3.1.2-1build3
Fixed in–
Ubuntu 20.04 LTSzephyrpkg:deb/ubuntu/zephyr?arch=source&distro=focalOther threatsAffected
  • =3.1.2-1build3
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

bt_sdp_parse_attribute() in subsys/bluetooth/host/classic/sdp.c validated only that the SDP record buffer held the type-marker byte plus the 2-byte attribute ID (a check of buf->len < 3) but then read a fourth byte, the data-element descriptor (type), via net_buf_simple_pull_u8(). Because net_buf_simple_pull_u8() dereferences buf->data[0] before its only bounds guard (an __ASSERT_NO_MSG that compiles out when CONFIG_ASSERT is disabled, the production default), a record of exactly three bytes (0x09 followed by a 2-byte attribute ID) causes a one-byte read past the end of the logical buffer. The parser is reachable from inbound, remote-controlled data: a Bluetooth BR/EDR peer acting as an SDP server returns discovery-response records that are stored verbatim in the client receive buffer and parsed via the public bt_sdp_get_attr()/bt_sdp_has_attr()/bt_sdp_record_parse() helpers. The over-read is bounded to a single byte that is used only as an internal length selector and is never leaked to the attacker; subsequent length checks then reject the malformed record. Realistic impact is therefore limited to an edge-case denial of service (a fault only if the record ends exactly at a mapped-memory boundary, or a deterministic assert panic when CONFIG_ASSERT=y). Affects Zephyr v4.3.0 and v4.4.0; fixed by adding sizeof(type) to the length check.

References

Community reviews

Loading reviews…