{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2023-52766",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2023-52766"
  ],
  "published": "2024-05-21T15:34:20Z",
  "summary": "i3c: mipi-i3c-hci: Fix out of bounds access in hci_dma_irq_handler",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\ni3c: mipi-i3c-hci: Fix out of bounds access in hci_dma_irq_handler\n\nDo not loop over ring headers in hci_dma_irq_handler() that are not\nallocated and enabled in hci_dma_init(). Otherwise out of bounds access\nwill occur from rings->headers[i] access when i >= number of allocated\nring headers.",
  "severity": [
    {
      "type": "CVSS_V3",
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
    }
  ],
  "affected": [
    {
      "package": {
        "ecosystem": "Raspberry Pi OS:12",
        "name": "linux"
      },
      "versions": [
        "1:6.1.47-1+rpt4"
      ],
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-2712",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v6",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v7",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v7l",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v8",
            "binary_version": "1:6.1.47-1+rpt4"
          }
        ]
      },
      "database_specific": {
        "per_version": {
          "1:6.1.47-1+rpt4": {
            "linux_commit": "655fc658a15ae7a6f37103754adb39ba52a9a14e",
            "upstream_version": "6.1.47",
            "assessment": "commit ancestry (strak rule)",
            "upstream_fixed": "6.1.64",
            "compiled_filter": false
          }
        }
      }
    }
  ],
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.cve.org/CVERecord?id=CVE-2023-52766"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/d23ad76f240c0f597b7a9eb79905d246f27d40df"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/8be39f66915b40d26ea2c18ba84b5c3d5da6809b"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/7c2b91b30d74d7c407118ad72502d4ca28af1af6"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/4c86cb2321bd9c72d3b945ce7f747961beda8e65"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/45a832f989e520095429589d5b01b0c65da9b574"
    }
  ],
  "database_specific": {
    "source": "https://git.kernel.org/pub/scm/linux/security/vulns.git",
    "upstream_modified": "2026-08-05T11:24:39Z",
    "severity": {
      "source": "kernel CNA",
      "cvss_v3_score": 7.8,
      "cvss_v3_severity": "High",
      "scenario": "AV:L - The vulnerable path is the platform driver's hard-IRQ handler (i3c_hci_irq_handler \u2192 hci_dma_irq_handler), reached when local I3C/I2C bus activity raises host-controller ring interrupts. There is no network or adjacent-link packet path into this HCI master driver.\nAC:L - On multi-ring-capable HCI hardware the interrupt mask can present bits beyond the single software-enabled ring, and a local attacker can reliably induce those IRQs via I3C/I2C client transfers; no attacker-uncontrollable race or layout precondition is required to hit the OOB once those bits are set.\nPR:L - The IRQ handler itself has no capability check, and bus traffic that raises ring interrupts is reachable through ordinary local I3C/I2C client paths (sensors, i2c-adapter users) without real init-namespace root or CAP_SYS_MODULE.\nUI:N - Once the attacker can generate the relevant bus traffic, the host controller delivers the interrupt and the handler runs with no separate victim action required.\nS:U - The OOB access and resulting MMIO/memory corruption stay inside the host kernel's I3C HCI authority and do not cross a VM, IOMMU, or sandbox boundary.\nC:H - The handler out-of-bounds-reads adjacent heap as struct hci_rh_data and then performs MMIO reads and IBI/xfer processing through those corrupted pointers, which is a high-impact disclosure/memory-corruption read primitive.\nI:H - The same corrupted rh->regs is used for rh_reg_write(), and hci_dma_xfer_done()/hci_dma_process_ibi() write through OOB-sourced pointers, yielding an arbitrary MMIO/memory write primitive exploitable for control-flow hijacking.\nA:H - Dereferencing an out-of-bounds or garbage rh in hard-IRQ context causes kernel oops/panic or persistent controller failure, which is full availability loss."
    }
  }
}