hwmon: (peci/dimmtemp) Fix devres leak and UAF on concurrent unbind
Summary
| CVE | CVE-2026-99718 |
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-11-20 06:18:08 UTC |
| Updated | 2026-11-20 06:18:08 UTC |
| Description | In the Linux kernel, the following vulnerability has been resolved:
hwmon: (peci/dimmtemp) Fix devres leak and UAF on concurrent unbind
When a peci_dimmtemp device is unbound concurrently with its delayed
initialization work (detect_work), newly allocated devm resources and
the hwmon device are leaked, leading to a use-after-free when reading
the lingering hwmon sysfs attributes.
In peci_dimmtemp_probe(), detect_work is registered for cancellation via
devm_delayed_work_autocancel(). During driver detach, devres_release_all()
first moves all existing entries from dev->devres_head onto a local todo
list before invoking their release callbacks in reverse order. If
create_dimm_temp_info_delayed() is already running when
devm_delayed_work_drop() calls cancel_delayed_work_sync(),
create_dimm_temp_info() can allocate dimmtemp_label strings via
devm_kzalloc()/devm_kasprintf() and register the hwmon device via
devm_hwmon_device_register_with_info(), appending new devres entries to
the now-empty dev->devres_head. Once the work finishes,
devres_release_all() frees priv and priv->name from the local todo list
without re-evaluating dev->devres_head, leaving the late devres
allocations and registered hwmon device behind with a dangling priv
pointer.
Cancel detect_work synchronously in a driver .remove() callback instead
of relying on devm_delayed_work_autocancel() so that the work is fully
drained before devres_release_all() detaches dev->devres_head, allowing
any devm resources registered by the delayed work to be released in
proper reverse order. Also only schedule detect_work when
check_populated_dimms() returns -EAGAIN so that probe failure paths do
not leave delayed work pending. |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected 73bc1b885daeb684fbcd16cc4e979cac6a831b12 f27cb64b04af01370fbe2d23ba9aeb3401d6def8 git |
Not specified |
| CNA |
Linux |
Linux |
affected 73bc1b885daeb684fbcd16cc4e979cac6a831b12 c7dcea6bdc6c36c649c1fdd29909b232bcac28c9 git |
Not specified |
| CNA |
Linux |
Linux |
affected 73bc1b885daeb684fbcd16cc4e979cac6a831b12 3f6bd7aeea5c3bd5ced9e23184155065f551ea96 git |
Not specified |
| CNA |
Linux |
Linux |
affected 73bc1b885daeb684fbcd16cc4e979cac6a831b12 61bc4514b8e99e9733c04de028885f6fc906d628 git |
Not specified |
| CNA |
Linux |
Linux |
affected 5.18 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 5.18 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.118 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.64 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.3.5 7.3.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.4-rc2 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/f27cb64b04af01370fbe2d23ba9aeb3401d6def8 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/c7dcea6bdc6c36c649c1fdd29909b232bcac28c9 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/61bc4514b8e99e9733c04de028885f6fc906d628 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/3f6bd7aeea5c3bd5ced9e23184155065f551ea96 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.