CVE-2026-99718

Source
https://cve.org/CVERecord?id=CVE-2026-99718
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99718.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2026-99718
Published
2026-11-20T05:50:56Z
Modified
2026-11-20T07:01:12Z
Summary
hwmon: (peci/dimmtemp) Fix devres leak and UAF on concurrent unbind
Details

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.

Database specific
{
    "cna_assigner": "Linux",
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99718.json"
}
References

Affected packages

Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

Affected ranges

Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
73bc1b885daeb684fbcd16cc4e979cac6a831b12
Fixed
f27cb64b04af01370fbe2d23ba9aeb3401d6def8
Fixed
c7dcea6bdc6c36c649c1fdd29909b232bcac28c9
Fixed
3f6bd7aeea5c3bd5ced9e23184155065f551ea96
Fixed
61bc4514b8e99e9733c04de028885f6fc906d628

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99718.json"

Linux / Kernel

Package

Name
Kernel

Affected ranges

Type
ECOSYSTEM
Events
Introduced
5.18.0
Fixed
6.12.118
Type
ECOSYSTEM
Events
Introduced
6.13.0
Fixed
6.18.64
Type
ECOSYSTEM
Events
Introduced
6.19.0
Fixed
7.3.5

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99718.json"