summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python
diff options
context:
space:
mode:
authorRavindra <ravindra@intel.com>2026-09-15 10:42:15 +0530
committerLuiz Augusto von Dentz <luiz.von.dentz@intel.com>2026-09-21 09:37:20 -0400
commit37a11129345337efd6eef8e62b03b6348cd0dd8b (patch)
tree41f1643bb744c0d3e3f97c70995bebb122a17e61 /tools/perf/scripts/python
parentf0ca020cbb9bb7f3f4ea8ba1dfcf30a282aec91e (diff)
downloadlinux-37a11129345337efd6eef8e62b03b6348cd0dd8b.tar.gz
linux-37a11129345337efd6eef8e62b03b6348cd0dd8b.zip
Bluetooth: btintel_pcie: validate device-supplied DMA indices
In btintel_pcie_msix_rx_handle(), the driver processes RX completion descriptors (urbd1) written by the PCIe device into DMA-coherent memory. urbd1->frbd_tag (a 16-bit field fully controlled by the device firmware via DMA) is used directly as an array index into rxq->bufs[] without any bounds check. rxq->bufs[] has only BTINTEL_PCIE_RX_DESCS_COUNT (64) entries, while frbd_tag can be any value 0-65535. A malicious or malfunctioning device can write an out-of-range frbd_tag, causing the driver to dereference an out-of-bounds data_buf pointer. Additionally, cr_hia is read from a DMA-shared index array also writable by the device; if the device sets cr_hia >= rxq->count, the while-loop never terminates because cr_tia is wrapped via modulo rxq->count and can never equal an out-of-range cr_hia. Add bounds validation for cr_hia and frbd_tag in the RX path, and cr_hia in the TX path. Log invalid values with bt_dev_err before returning. Fixes: c2b636b3f788 ("Bluetooth: btintel_pcie: Add support for PCIe transport") Signed-off-by: Ravindra <ravindra@intel.com> Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions