FKIE_CVE-2026-93190

Vulnerability from fkie_nvd - Published: 2026-09-17 17:18 - Updated: 2026-10-19 10:17
Severity
8.4 (High) - CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Summary
In the Linux kernel, the following vulnerability has been resolved: platform/chrome: cros_ec_typec: Reject out-of-bounds PD cap count cros_typec_register_partner_pdos() copies the partner PDOs from the EC TYPEC_STATUS response into the fixed caps_desc.pdo[PDO_MAX_OBJECTS] array. memcpy(caps_desc.pdo, resp->source_cap_pdos, sizeof(u32) * resp->source_cap_count); ... memcpy(caps_desc.pdo, resp->sink_cap_pdos, sizeof(u32) * resp->sink_cap_count); PDO_MAX_OBJECTS is 7. source_cap_count and sink_cap_count are u8 fields from the EC. The only check is that they are not both zero. If either is larger than 7, the memcpy writes past the end of the array on the stack. A count of 255 overflows it by about 1 KB. The EC source arrays are only seven entries wide. A larger count reads past them too. The ChromeOS EC firmware caps these counts today, so a compliant setup does not hit this. The kernel should still validate these values rather than trust them. Validate the counts in cros_typec_register_partner_pdos() next to the memcpy. Skip the PDO registration if either count is above PDO_MAX_OBJECTS. The rest of cros_typec_handle_status() still runs so events are handled and cleared.
References
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/2a7a4e45a3aa4f4ef7013eb64649f6184b76a293
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/4e37371cb4e3b8ff564d7760029236a7bd614562
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/54d6b0ee9b8ba434089b11843effc111dc2e6ead
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/7617b210a2200b76d8f171819390468c7d189c80
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/a0a8cd9fc9c48b95095bcec4b146f7a99486f58e
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/e4728288473a5024a8bdba7d43f346719606fea0
Impacted products
Vendor Product Version
To clipboard 

{
  "affected": [
    {
      "affectedData": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/platform/chrome/cros_ec_typec.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "7617b210a2200b76d8f171819390468c7d189c80",
              "status": "affected",
              "version": "348a2e8c93d3ca622cf1b293cd2f597c9db74d9d",
              "versionType": "git"
            },
            {
              "lessThan": "4e37371cb4e3b8ff564d7760029236a7bd614562",
              "status": "affected",
              "version": "348a2e8c93d3ca622cf1b293cd2f597c9db74d9d",
              "versionType": "git"
            },
            {
              "lessThan": "2a7a4e45a3aa4f4ef7013eb64649f6184b76a293",
              "status": "affected",
              "version": "348a2e8c93d3ca622cf1b293cd2f597c9db74d9d",
              "versionType": "git"
            },
            {
              "lessThan": "e4728288473a5024a8bdba7d43f346719606fea0",
              "status": "affected",
              "version": "348a2e8c93d3ca622cf1b293cd2f597c9db74d9d",
              "versionType": "git"
            },
            {
              "lessThan": "54d6b0ee9b8ba434089b11843effc111dc2e6ead",
              "status": "affected",
              "version": "348a2e8c93d3ca622cf1b293cd2f597c9db74d9d",
              "versionType": "git"
            },
            {
              "lessThan": "a0a8cd9fc9c48b95095bcec4b146f7a99486f58e",
              "status": "affected",
              "version": "348a2e8c93d3ca622cf1b293cd2f597c9db74d9d",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/platform/chrome/cros_ec_typec.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.1"
            },
            {
              "lessThan": "6.1",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.1.*",
              "status": "unaffected",
              "version": "6.1.188",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.6.*",
              "status": "unaffected",
              "version": "6.6.157",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.110",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.52",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.2.*",
              "status": "unaffected",
              "version": "7.2.6",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.3",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nplatform/chrome: cros_ec_typec: Reject out-of-bounds PD cap count\n\ncros_typec_register_partner_pdos() copies the partner PDOs from the EC\nTYPEC_STATUS response into the fixed caps_desc.pdo[PDO_MAX_OBJECTS] array.\n\n\tmemcpy(caps_desc.pdo, resp-\u003esource_cap_pdos,\n\t       sizeof(u32) * resp-\u003esource_cap_count);\n\t...\n\tmemcpy(caps_desc.pdo, resp-\u003esink_cap_pdos,\n\t       sizeof(u32) * resp-\u003esink_cap_count);\n\nPDO_MAX_OBJECTS is 7. source_cap_count and sink_cap_count are u8 fields\nfrom the EC. The only check is that they are not both zero. If either is\nlarger than 7, the memcpy writes past the end of the array on the stack.\nA count of 255 overflows it by about 1 KB. The EC source arrays are only\nseven entries wide. A larger count reads past them too.\n\nThe ChromeOS EC firmware caps these counts today, so a compliant setup\ndoes not hit this. The kernel should still validate these values rather\nthan trust them.\n\nValidate the counts in cros_typec_register_partner_pdos() next to the\nmemcpy. Skip the PDO registration if either count is above PDO_MAX_OBJECTS.\nThe rest of cros_typec_handle_status() still runs so events are handled\nand cleared."
    }
  ],
  "id": "CVE-2026-93190",
  "lastModified": "2026-10-19T10:17:09.583",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "LOCAL",
          "availabilityImpact": "HIGH",
          "baseScore": 8.4,
          "baseSeverity": "HIGH",
          "confidentialityImpact": "HIGH",
          "integrityImpact": "HIGH",
          "privilegesRequired": "NONE",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
          "version": "3.1"
        },
        "exploitabilityScore": 2.5,
        "impactScore": 5.9,
        "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "type": "Secondary"
      }
    ]
  },
  "published": "2026-09-17T17:18:15.177",
  "references": [
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/2a7a4e45a3aa4f4ef7013eb64649f6184b76a293"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/4e37371cb4e3b8ff564d7760029236a7bd614562"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/54d6b0ee9b8ba434089b11843effc111dc2e6ead"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/7617b210a2200b76d8f171819390468c7d189c80"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/a0a8cd9fc9c48b95095bcec4b146f7a99486f58e"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/e4728288473a5024a8bdba7d43f346719606fea0"
    }
  ],
  "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
  "vulnStatus": "Received"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




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
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Loading timeline…




    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.