mfd: cros_ec: Delay dev_set_drvdata() until probe success
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.96, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 1c1d152cc5ac3a67d199728a9ba0b4f54a498f8b · fixed in 24522713034d521ea4b5f5f36342e2b2f7e73bd6; From 1c1d152cc5ac3a67d199728a9ba0b4f54a498f8b · fixed in f7e81dc181d9fe8ab977158042cd193e8cc12091; From 1c1d152cc5ac3a67d199728a9ba0b4f54a498f8b · fixed in 257203d83204b192d1265a916b42ca0d499bb117; From 1c1d152cc5ac3a67d199728a9ba0b4f54a498f8b · fixed in 729ae27dc2503a7c1f92da1859efb45da03e4fa0; From 1c1d152cc5ac3a67d199728a9ba0b4f54a498f8b · fixed in ed2941e5db016a0c600b25f1972620e6e223d9fa; From 1c1d152cc5ac3a67d199728a9ba0b4f54a498f8b · fixed in b5f41d5bf08e7b1b14fa0bd640975e6d78dc006d; From 1c1d152cc5ac3a67d199728a9ba0b4f54a498f8b · fixed in fc030c5b116f668d4ca86dca63742ddbc98d1665; From 1c1d152cc5ac3a67d199728a9ba0b4f54a498f8b · fixed in 8b2c1d41bc36c100b38ce5ee6def246c527eaf8a
- Linux Linux
4.12
- KernelLinux
From 4.12.0 · fixed in 5.10.261; From 5.11.0 · fixed in 5.15.212; From 5.16.0 · fixed in 6.1.178; From 6.2.0 · fixed in 6.6.145; From 6.7.0 · fixed in 6.12.96; From 6.13.0 · fixed in 6.18.39; From 6.19.0 · fixed in 7.1.4
References 8
git.kernel.org
- stable/c/24522713034d521ea4b5f5f36342e2b2f7e73bd6
- stable/c/f7e81dc181d9fe8ab977158042cd193e8cc12091
- stable/c/257203d83204b192d1265a916b42ca0d499bb117
- stable/c/729ae27dc2503a7c1f92da1859efb45da03e4fa0
- stable/c/ed2941e5db016a0c600b25f1972620e6e223d9fa
- stable/c/b5f41d5bf08e7b1b14fa0bd640975e6d78dc006d
- stable/c/fc030c5b116f668d4ca86dca63742ddbc98d1665
- stable/c/8b2c1d41bc36c100b38ce5ee6def246c527eaf8a