All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Ravindra <ravindra@intel.com>
Cc: linux-bluetooth@vger.kernel.org, ravishankar.srivatsa@intel.com,
	chethan.tumkur.narayan@intel.com, kiran.k@intel.com
Subject: Re: [PATCH v1] Bluetooth: btintel_pcie: validate device-supplied DMA indices
Date: Mon, 21 Sep 2026 14:10:11 +0000	[thread overview]
Message-ID: <178999981163.3047822.11881464017430827292.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260915051215.2691851-1-ravindra@intel.com>

Hello:

This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Tue, 15 Sep 2026 10:42:15 +0530 you wrote:
> 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.
> 
> [...]

Here is the summary with links:
  - [v1] Bluetooth: btintel_pcie: validate device-supplied DMA indices
    https://git.kernel.org/bluetooth/bluetooth-next/c/37a111293453

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-09-21 14:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-15  5:12 [PATCH v1] Bluetooth: btintel_pcie: validate device-supplied DMA indices Ravindra
2026-09-15  7:30 ` [v1] " bluez.test.bot
2026-09-21 14:10 ` patchwork-bot+bluetooth [this message]

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=178999981163.3047822.11881464017430827292.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=chethan.tumkur.narayan@intel.com \
    --cc=kiran.k@intel.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=ravindra@intel.com \
    --cc=ravishankar.srivatsa@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.