LiveActive security incident?Get immediate response
CVE Record

CVE-2025-68804: platform/chrome: cros_ec_ishtp: Fix UAF after unbinding driver

In the Linux kernel, the following vulnerability has been resolved: platform/chrome: cros_ec_ishtp: Fix UAF after unbinding driver After unbinding the driver, another kthread `cros_ec_console_log_work` is still accessing the device, resulting an UAF and crash. The driver doesn't unregister the EC device in .remove() which should shutdown sub-devices synchronously. Fix it.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel use-after-free flaw in the Chrome EC ISHTP driver path. When the driver is unbound, a remaining worker thread can still access the device, causing a crash. Business impact appears availability-focused from the sources; severity and CVSS are not provided.

Executive priority

Treat as a targeted kernel stability issue until severity data improves. Patch through normal kernel maintenance, with higher priority for fleets using the affected Chrome EC driver path or seeing related crashes.

Technical view

The cros_ec_ishtp driver fails to unregister the EC device during remove(), leaving cros_ec_console_log_work able to access freed device state after unbind. The upstream fix synchronously shuts down sub-devices by unregistering the EC device in remove().

Likely exposure

Exposure is limited to Linux systems using affected kernel versions with the platform/chrome cros_ec_ishtp driver path. The CVE record lists Linux as affected, but does not provide deployment prevalence, CPEs, or distribution-specific package mappings.

Exploitation context

CISA KEV status is false in the provided bundle, and no cited source claims active exploitation. The described trigger is driver unbinding followed by a lingering kernel thread access, leading to UAF and crash.

Researcher notes

The evidence supports a lifecycle cleanup bug in driver remove(). The source bundle does not include CVSS, CWE, exploitability analysis, or distro advisories. Validation should focus on kernel lineage, driver presence, and whether the unregister-on-remove fix is backported.

Mitigation direction

  • Apply vendor kernel updates that include the referenced Linux stable fixes.
  • Confirm distribution advisories before assuming a specific fixed package version.
  • Avoid unnecessary cros_ec_ishtp driver unbind operations until patched.
  • Prioritize patching systems where this driver is present and operationally important.

Validation and detection

  • Inventory Linux kernels against the CVE affected version entries.
  • Check whether the cros_ec_ishtp driver path is present and in use.
  • Verify the running kernel includes a referenced stable commit or vendor backport.
  • Review kernel crash reports for UAF or panic events after driver unbinds.
Prepared
Confidence
medium
Sources
9

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-68804 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
8Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux26a14267aff218c60b89007fdb44ca392ba6122c, 26a14267aff218c60b89007fdb44ca392ba6122c, 26a14267aff218c60b89007fdb44ca392ba6122c, 26a14267aff218c60b89007fdb44ca392ba6122c, 26a14267aff218c60b89007fdb44ca392ba6122c, 26a14267aff218c60b89007fdb44ca392ba6122c, 26a14267aff218c60b89007fdb44ca392ba6122cunaffected
LinuxLinux5.3, 0, 5.10.248, 5.15.198, 6.1.160, 6.6.120, 6.12.64, 6.18.3, 6.19affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.