CVE-2026-64420

CVE CVE-2026-64420EUVD EUVD-2026-48964Published 2026-07-25T08:50:59.000ZLast changed 2026-08-05T12:41:51.000ZCVSS 7.0

What the advisory describes

In the Linux kernel, the following vulnerability has been resolved: mfd: cros_ec: Delay dev_set_drvdata() until probe success If ec_device_probe() fails, cros_ec_class_release releases memory for the cros_ec_dev structure. However, because the drvdata was already set, sub-drivers like cros_ec_typec can still retrieve the stale pointer via the platform device. This leads to a use-after-free when cros_ec_typec attempts to access &typec->ec->ec->dev on a device that has already been released. Move dev_set_drvdata() to ensure that the pointer is only made available once all initialization steps have succeeded. sysfs: cannot create duplicate filename '/class/chromeos/cros_ec' Call trace: sysfs_do_create_link_sd+0x94/0xdc sysfs_create_link+0x30/0x44 device_add_class_symlinks+0x90/0x13c device_add+0xf0/0x50c ec_device_probe+0x150/0x4f0 platform_probe+0xa0/0xe0 ... BUG: KASAN: invalid-access in __memcpy+0x44/0x230 Write at addr f5ffff809e2d33ac by task kworker/u32:5/125 Pointer tag: [f5], memory tag: [fe] Tainted : [W]=WARN, [O]=OOT_MODULE Hardware name: Google Navi unprovisioned 0x7FFFFFFF/sku0 board/sku3 Workqueue: events_unbound deferred_probe_work_func Call trace: __memcpy+0x44/0x230 cros_ec_check_features+0x60/0xcc [cros_ec_proto] cros_typec_probe+0xe8/0x6e0 [cros_ec_typec] platform_probe+0xa0/0xe0

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

Linux — Linux 1c1d152cc5ac3a67d199728a9ba0b4f54a498f8b <b5f41d5bf08e7b1b14fa0bd640975e6d78dc006d; patch: 5.15.212; 1c1d152cc5ac3a67d199728a9ba0b4f54a498f8b <24522713034d521ea4b5f5f36342e2b2f7e73bd6; patch: 7.1.4; patch: 0; 1c1d152cc5ac3a67d199728a9ba0b4f54a498f8b <fc030c5b116f668d4ca86dca63742ddbc98d1665; 1c1d152cc5ac3a67d199728a9ba0b4f54a498f8b <257203d83204b192d1265a916b42ca0d499bb117; patch: 6.18.39; 1c1d152cc5ac3a67d199728a9ba0b4f54a498f8b <f7e81dc181d9fe8ab977158042cd193e8cc12091; patch: 6.12.96; patch: 6.1.178; patch: 6.6.145; patch: 5.10.261; 4.12; 1c1d152cc5ac3a67d199728a9ba0b4f54a498f8b <729ae27dc2503a7c1f92da1859efb45da03e4fa0; 1c1d152cc5ac3a67d199728a9ba0b4f54a498f8b <8b2c1d41bc36c100b38ce5ee6def246c527eaf8a; 1c1d152cc5ac3a67d199728a9ba0b4f54a498f8b <ed2941e5db016a0c600b25f1972620e6e223d9fa; patch: 7.2-rc1

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

Linux — Linux

Does this concern one of your customers?

This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.

Try it for 28 days

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.