ubuntu-cve-2026-10658
Vulnerability from osv_ubuntu
Published
2026-06-23 01:16
Modified
2026-07-15 17:48
Summary
Details

bt_iso_recv() in subsys/bluetooth/host/iso.c pulled the ISO SDU header (4 bytes) or, when the timestamp flag is set, the timestamped SDU header (8 bytes) from the inbound HCI ISO Data buffer via net_buf_pull_mem() without first checking buf->len. The upstream hci_iso() handler enforces buf->len == the controller-declared ISO Data_Load length, so a malicious or buggy controller / adjacent BLE peer on an established CIS/BIS can present a first-fragment (BT_ISO_START) or single (BT_ISO_SINGLE) PDU shorter than the SDU header. Because net_buf_simple_pull_mem only guards length with __ASSERT_NO_MSG (compiled out when CONFIG_ASSERT is disabled, the production default), the pull underflows buf->len (uint16_t, e.g. 0 - 8 = 0xFFF8) and advances buf->data past valid data: the subsequent reads of hdr->slen and hdr->sn are out-of-bounds reads of adjacent pool memory. For the multi-fragment (START) case the corrupted buffer is retained as iso->rx, and a following CONT/END fragment's net_buf_tailroom() guard underflows to a near-SIZE_MAX value, defeating the bounds check and causing net_buf_add_mem() to memcpy attacker-supplied fragment data far past the RX pool buffer (out-of-bounds write). The flaw affects ISO receive builds (CONFIG_BT_ISO_RX, selected by the default-off LE Audio options BT_ISO_PERIPHERAL/BT_ISO_CENTRAL/BT_ISO_SYNC_RECEIVER) and has existed since the ISO subsystem was introduced (v2.6.0) through v4.4.0. The fix adds explicit buf->len < sizeof(ts_hdr) and buf->len < sizeof(hdr) checks that drop the buffer before pulling.


{
  "affected": [
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "libzephyr4",
            "binary_version": "3.1.2-1build1"
          },
          {
            "binary_name": "libzephyr4-krb5",
            "binary_version": "3.1.2-1build1"
          },
          {
            "binary_name": "zephyr-clients",
            "binary_version": "3.1.2-1build1"
          },
          {
            "binary_name": "zephyr-server",
            "binary_version": "3.1.2-1build1"
          },
          {
            "binary_name": "zephyr-server-krb5",
            "binary_version": "3.1.2-1build1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:16.04:LTS",
        "name": "zephyr",
        "purl": "pkg:deb/ubuntu/zephyr@3.1.2-1build1?arch=source\u0026distro=xenial"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "3.1.2-1",
        "3.1.2-1build1"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "libzephyr4",
            "binary_version": "3.1.2-1build2"
          },
          {
            "binary_name": "libzephyr4-krb5",
            "binary_version": "3.1.2-1build2"
          },
          {
            "binary_name": "zephyr-clients",
            "binary_version": "3.1.2-1build2"
          },
          {
            "binary_name": "zephyr-server",
            "binary_version": "3.1.2-1build2"
          },
          {
            "binary_name": "zephyr-server-krb5",
            "binary_version": "3.1.2-1build2"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:18.04:LTS",
        "name": "zephyr",
        "purl": "pkg:deb/ubuntu/zephyr@3.1.2-1build2?arch=source\u0026distro=bionic"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "3.1.2-1build1",
        "3.1.2-1build2"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "libzephyr4",
            "binary_version": "3.1.2-1build3"
          },
          {
            "binary_name": "libzephyr4-krb5",
            "binary_version": "3.1.2-1build3"
          },
          {
            "binary_name": "zephyr-clients",
            "binary_version": "3.1.2-1build3"
          },
          {
            "binary_name": "zephyr-server",
            "binary_version": "3.1.2-1build3"
          },
          {
            "binary_name": "zephyr-server-krb5",
            "binary_version": "3.1.2-1build3"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:20.04:LTS",
        "name": "zephyr",
        "purl": "pkg:deb/ubuntu/zephyr@3.1.2-1build3?arch=source\u0026distro=focal"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "3.1.2-1build3"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "libzephyr4",
            "binary_version": "3.1.2-1build3"
          },
          {
            "binary_name": "libzephyr4-krb5",
            "binary_version": "3.1.2-1build3"
          },
          {
            "binary_name": "zephyr-clients",
            "binary_version": "3.1.2-1build3"
          },
          {
            "binary_name": "zephyr-server",
            "binary_version": "3.1.2-1build3"
          },
          {
            "binary_name": "zephyr-server-krb5",
            "binary_version": "3.1.2-1build3"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "zephyr",
        "purl": "pkg:deb/ubuntu/zephyr@3.1.2-1build3?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "3.1.2-1build3"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "libzephyr4",
            "binary_version": "3.1.2-1.1build1"
          },
          {
            "binary_name": "libzephyr4-krb5",
            "binary_version": "3.1.2-1.1build1"
          },
          {
            "binary_name": "zephyr-clients",
            "binary_version": "3.1.2-1.1build1"
          },
          {
            "binary_name": "zephyr-server",
            "binary_version": "3.1.2-1.1build1"
          },
          {
            "binary_name": "zephyr-server-krb5",
            "binary_version": "3.1.2-1.1build1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:24.04:LTS",
        "name": "zephyr",
        "purl": "pkg:deb/ubuntu/zephyr@3.1.2-1.1build1?arch=source\u0026distro=noble"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "3.1.2-1.1",
        "3.1.2-1.1build1"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "libzephyr4",
            "binary_version": "3.1.2-1.1build1"
          },
          {
            "binary_name": "libzephyr4-krb5",
            "binary_version": "3.1.2-1.1build1"
          },
          {
            "binary_name": "zephyr-clients",
            "binary_version": "3.1.2-1.1build1"
          },
          {
            "binary_name": "zephyr-server",
            "binary_version": "3.1.2-1.1build1"
          },
          {
            "binary_name": "zephyr-server-krb5",
            "binary_version": "3.1.2-1.1build1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:25.10",
        "name": "zephyr",
        "purl": "pkg:deb/ubuntu/zephyr@3.1.2-1.1build1?arch=source\u0026distro=questing"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "3.1.2-1.1build1"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "libzephyr4",
            "binary_version": "3.1.2-4"
          },
          {
            "binary_name": "libzephyr4-krb5",
            "binary_version": "3.1.2-4"
          },
          {
            "binary_name": "zephyr-clients",
            "binary_version": "3.1.2-4"
          },
          {
            "binary_name": "zephyr-server",
            "binary_version": "3.1.2-4"
          },
          {
            "binary_name": "zephyr-server-krb5",
            "binary_version": "3.1.2-4"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:26.04:LTS",
        "name": "zephyr",
        "purl": "pkg:deb/ubuntu/zephyr@3.1.2-4?arch=source\u0026distro=resolute"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "3.1.2-1.1build1",
        "3.1.2-4"
      ]
    }
  ],
  "aliases": [],
  "details": "bt_iso_recv() in subsys/bluetooth/host/iso.c pulled the ISO SDU header (4 bytes) or, when the timestamp flag is set, the timestamped SDU header (8 bytes) from the inbound HCI ISO Data buffer via net_buf_pull_mem() without first checking buf-\u003elen. The upstream hci_iso() handler enforces buf-\u003elen == the controller-declared ISO Data_Load length, so a malicious or buggy controller / adjacent BLE peer on an established CIS/BIS can present a first-fragment (BT_ISO_START) or single (BT_ISO_SINGLE) PDU shorter than the SDU header. Because net_buf_simple_pull_mem only guards length with __ASSERT_NO_MSG (compiled out when CONFIG_ASSERT is disabled, the production default), the pull underflows buf-\u003elen (uint16_t, e.g. 0 - 8 = 0xFFF8) and advances buf-\u003edata past valid data: the subsequent reads of hdr-\u003eslen and hdr-\u003esn are out-of-bounds reads of adjacent pool memory. For the multi-fragment (START) case the corrupted buffer is retained as iso-\u003erx, and a following CONT/END fragment\u0027s net_buf_tailroom() guard underflows to a near-SIZE_MAX value, defeating the bounds check and causing net_buf_add_mem() to memcpy attacker-supplied fragment data far past the RX pool buffer (out-of-bounds write). The flaw affects ISO receive builds (CONFIG_BT_ISO_RX, selected by the default-off LE Audio options BT_ISO_PERIPHERAL/BT_ISO_CENTRAL/BT_ISO_SYNC_RECEIVER) and has existed since the ISO subsystem was introduced (v2.6.0) through v4.4.0. The fix adds explicit buf-\u003elen \u003c sizeof(ts_hdr) and buf-\u003elen \u003c sizeof(hdr) checks that drop the buffer before pulling.",
  "id": "UBUNTU-CVE-2026-10658",
  "modified": "2026-07-15T17:48:10Z",
  "published": "2026-06-23T01:16:00Z",
  "references": [
    {
      "type": "REPORT",
      "url": "https://ubuntu.com/security/CVE-2026-10658"
    },
    {
      "type": "REPORT",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-10658"
    },
    {
      "type": "REPORT",
      "url": "https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-26g8-rmpf-j6cw"
    }
  ],
  "related": [],
  "schema_version": "1.7.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H",
      "type": "CVSS_V3"
    },
    {
      "score": "medium",
      "type": "Ubuntu"
    }
  ],
  "upstream": [
    "CVE-2026-10658"
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…