From: Tristan Madani <tristmd@gmail.com>
To: Marcel Holtmann <marcel@holtmann.org>,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: Seema Sreemantha <seema.sreemantha@intel.com>,
Kiran K <kiran.k@intel.com>,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org,
Tristan Madani <tristan@talencesecurity.com>
Subject: [PATCH bluetooth] Bluetooth: btintel: validate PPAG table element types
Date: Sat, 24 Oct 2026 20:59:42 +0000 [thread overview]
Message-ID: <20261024205942.4056250-1-tristmd@gmail.com> (raw)
From: Tristan Madani <tristan@talencesecurity.com>
btintel_set_ppag() validates that the top-level ACPI PPAG object is a
package, but does not check that the inner PPAG table at element[1] is
itself a package with integer elements. If firmware returns a
non-package type in that position, the code interprets an unrelated
union member as package.elements, dereferencing a meaningless pointer.
Add type validation for the inner package and its integer elements
before reading the domain and mode values.
Fixes: c585a92b2f9c ("Bluetooth: btintel: Set Per Platform Antenna Gain(PPAG)")
Cc: stable@vger.kernel.org
Signed-off-by: Tristan Madani <tristan@talencesecurity.com>
---
drivers/bluetooth/btintel.c | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git a/drivers/bluetooth/btintel.c b/drivers/bluetooth/btintel.c
index c69a5d226e882..aeaf80e03f8ad 100644
--- a/drivers/bluetooth/btintel.c
+++ b/drivers/bluetooth/btintel.c
@@ -2637,6 +2637,19 @@ static void btintel_set_ppag(struct hci_dev *hdev, struct intel_version_tlv *ver
/* PPAG table is located at element[1] */
p = &elements[1];
+ if (p->type != ACPI_TYPE_PACKAGE || p->package.count < 2) {
+ bt_dev_warn(hdev, "PPAG-BT: Invalid PPAG table format");
+ kfree(buffer.pointer);
+ return;
+ }
+
+ if (p->package.elements[0].type != ACPI_TYPE_INTEGER ||
+ p->package.elements[1].type != ACPI_TYPE_INTEGER) {
+ bt_dev_warn(hdev, "PPAG-BT: Invalid element types in PPAG table");
+ kfree(buffer.pointer);
+ return;
+ }
+
domain = (u32)p->package.elements[0].integer.value;
mode = (u32)p->package.elements[1].integer.value;
kfree(buffer.pointer);
--
2.47.3
reply other threads:[~2026-10-24 20:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261024205942.4056250-1-tristmd@gmail.com \
--to=tristmd@gmail.com \
--cc=kiran.k@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=seema.sreemantha@intel.com \
--cc=stable@vger.kernel.org \
--cc=tristan@talencesecurity.com \
/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
all inboxes | Powered by JetHome®