GHSA-F3Q9-4Q8H-J7XP

Vulnerability from github – Published: 2026-10-18 18:31 – Updated: 2026-10-18 18:31
VLAI
Details

In the Linux kernel, the following vulnerability has been resolved:

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.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-98601"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-10-18T16:17:12Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: btintel_pcie: validate device-supplied DMA indices\n\nIn btintel_pcie_msix_rx_handle(), the driver processes RX completion\ndescriptors (urbd1) written by the PCIe device into DMA-coherent memory.\nurbd1-\u003efrbd_tag (a 16-bit field fully controlled by the device firmware\nvia DMA) is used directly as an array index into rxq-\u003ebufs[] without any\nbounds check. rxq-\u003ebufs[] has only BTINTEL_PCIE_RX_DESCS_COUNT (64)\nentries, while frbd_tag can be any value 0-65535. A malicious or\nmalfunctioning device can write an out-of-range frbd_tag, causing the\ndriver to dereference an out-of-bounds data_buf pointer.\n\nAdditionally, cr_hia is read from a DMA-shared index array also writable\nby the device; if the device sets cr_hia \u003e= rxq-\u003ecount, the while-loop\nnever terminates because cr_tia is wrapped via modulo rxq-\u003ecount and can\nnever equal an out-of-range cr_hia.\n\nAdd bounds validation for cr_hia and frbd_tag in the RX path, and cr_hia\nin the TX path. Log invalid values with bt_dev_err before returning.",
  "id": "GHSA-f3q9-4q8h-j7xp",
  "modified": "2026-10-18T18:31:56Z",
  "published": "2026-10-18T18:31:56Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98601"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/37a11129345337efd6eef8e62b03b6348cd0dd8b"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/8ec5838a35b03ac0cf3602452a369898051ffaf9"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/b29b70bfa12133423924fcd0327c19a802f7e368"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/f42cd95e679d5b78611cd2208cd1c41ad0045ffa"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

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.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.