Linux bluetooth development
 help / color / mirror / Atom feed
From: contact@capsize.online
To: linux-bluetooth@vger.kernel.org
Cc: Capsize Security <contact@capsize.online>
Subject: [PATCH] monitor: validate Return Link Keys length before parsing (CVE-2026-105460)
Date: Mon, 26 Oct 2026 19:31:12 -0600	[thread overview]
Message-ID: <20261027013113.555921-1-contact@capsize.online> (raw)

From: Capsize Security <contact@capsize.online>

Fixes public issue bluez/bluez#2687 (also filed as GitHub PR #2715 for
reference). return_link_keys_evt() loops over evt->num_keys entries of
22 bytes while the dispatcher only enforces plen >= 1; a crafted
btsnoop capture overflows the on-stack packet buffer (ASan-confirmed).
The patch rejects short payloads with the file's too-short-packet idiom.

Verified: pristine btmon + crafted capture -> ASan stack-buffer-overflow;
patched btmon -> clean reject, exit 0; boundary matrix + unit checks pass.

Assisted-by: Muse-Code:muse-spark
---

             reply	other threads:[~2026-10-27  1:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-27  1:31 contact [this message]
2026-10-27  1:31 ` [PATCH 1/1] monitor: validate Return Link Keys length before parsing contact
2026-10-27  3:19   ` [1/1] " bluez.test.bot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20261027013113.555921-1-contact@capsize.online \
    --to=contact@capsize.online \
    --cc=linux-bluetooth@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox