Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-64420mfd: cros_ec: Delay dev_set_drvdata() until probe success

Description

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

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 3 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-64420, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.0CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1High7.0CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.12% · top 98% of all CVEs (18 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.0.

Affected products

  • Linux · Linux

    • affected 1c1d152cc5ac3a67d199728a9ba0b4f54a498f8b – < 24522713034d521ea4b5f5f36342e2b2f7e73bd6
    • affected 1c1d152cc5ac3a67d199728a9ba0b4f54a498f8b – < f7e81dc181d9fe8ab977158042cd193e8cc12091
    • affected 1c1d152cc5ac3a67d199728a9ba0b4f54a498f8b – < 257203d83204b192d1265a916b42ca0d499bb117
    • affected 1c1d152cc5ac3a67d199728a9ba0b4f54a498f8b – < 729ae27dc2503a7c1f92da1859efb45da03e4fa0
    • affected 1c1d152cc5ac3a67d199728a9ba0b4f54a498f8b – < ed2941e5db016a0c600b25f1972620e6e223d9fa
    • affected 1c1d152cc5ac3a67d199728a9ba0b4f54a498f8b – < b5f41d5bf08e7b1b14fa0bd640975e6d78dc006d
    • affected 1c1d152cc5ac3a67d199728a9ba0b4f54a498f8b – < fc030c5b116f668d4ca86dca63742ddbc98d1665
    • affected 1c1d152cc5ac3a67d199728a9ba0b4f54a498f8b – < 8b2c1d41bc36c100b38ce5ee6def246c527eaf8a
  • Linux · Linux

    • affected 4.12
    • unaffected < 4.12
    • unaffected 5.10.261 – ≤ 5.10.*
    • unaffected 5.15.212 – ≤ 5.15.*
    • unaffected 6.1.178 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.96 – ≤ 6.12.*
    • unaffected 6.18.39 – ≤ 6.18.*
    • unaffected 7.1.4 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-64420 badge
[![CVE-2026-64420](https://cveledger.app/badge/CVE-2026-64420.svg)](https://cveledger.app/cve/CVE-2026-64420)

Record last updated .