{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2024-35924",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2024-35924"
  ],
  "published": "2024-05-19T10:11:49Z",
  "summary": "usb: typec: ucsi: Limit read size on v1.2",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nusb: typec: ucsi: Limit read size on v1.2\n\nBetween UCSI 1.2 and UCSI 2.0, the size of the MESSAGE_IN region was\nincreased from 16 to 256. In order to avoid overflowing reads for older\nsystems, add a mechanism to use the read UCSI version to truncate read\nsizes on UCSI v1.2.",
  "severity": [
    {
      "type": "CVSS_V3",
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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": null,
            "compiled_filter": false
          }
        }
      }
    }
  ],
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.cve.org/CVERecord?id=CVE-2024-35924"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/266f403ec47573046dee4bcebda82777ce702c40"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/0defcaa09d3b21e8387829ee3a652c43fa91e13f"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/b3db266fb031fba88c423d4bb8983a73a3db6527"
    }
  ],
  "database_specific": {
    "source": "https://git.kernel.org/pub/scm/linux/security/vulns.git",
    "upstream_modified": "2026-08-05T11:52:36Z",
    "severity": {
      "source": "kernel CNA",
      "cvss_v3_score": 7.1,
      "cvss_v3_severity": "High",
      "scenario": "AV:L - The UCSI core is a local platform driver (ACPI OpRegion, I2C, or pmic_glink transport) with no network or adjacent-network exposure; the over-read is driven by local UCSI transactions and the leaked bytes are harvested locally through /sys/class/typec and /sys/class/power_supply attributes or the UCSI debugfs response file.\nAC:L - There is no race and no dependence on memory layout the attacker cannot influence \u2014 any UCSI command requesting more than 16 bytes on a PPM reporting version \u22641.2 deterministically reads past the MESSAGE_IN window, and UCSI 1.x PPMs were the common case on shipping hardware.\nPR:L - The typec class attributes populated from the over-read buffers (usb_power_delivery_revision, number_of_alternate_modes, power_operation_mode, supported_accessory_modes) and the ucsi power-supply properties derived from src_pdos are all DEVICE_ATTR_RO/0444, so an ordinary unprivileged local user can read the disclosed bytes; no capability or root is required to observe the leak.\nUI:N - The oversized MESSAGE_IN reads are issued by the driver itself during registration, resume, and connector-change work handling; no victim action is needed for the out-of-bounds access to occur or for its results to be exposed.\nS:U - The out-of-bounds read stays within the kernel's own memory (memremap'd OpRegion, or the slab objects backing struct pmic_glink_ucsi / struct ucsi_ccg) and is consumed by the same kernel; no VM, IOMMU, or sandbox boundary is crossed.\nC:H - Up to 240 bytes beyond the 16-byte MESSAGE_IN window can be copied out \u2014 past read_buf[48] inside struct pmic_glink_ucsi, past the trailing op_data member of struct ucsi_ccg, or past the ACPI OpRegion \u2014 which is far more than a strictly bounded few-byte read and can expose adjacent heap contents (including pointers) through world-readable sysfs.\nI:N - The defect is purely an over-long read; every destination buffer is sized to the requested length, so no out-of-bounds write, allocation-size confusion, or control-flow corruption primitive is created.\nA:H - Reading hundreds of bytes past the end of a memremap'd ACPI/MMIO OpRegion can fault on platforms where the mapping does not extend that far, and the slab over-reads in the ccg and glink backends trip KASAN, so the bug can take the machine down."
    }
  }
}