CVE-2025-38682

published 4 Sep 2025 · updated 11 May 2026

i2c: core: Fix double-free of fwnode in i2c_unregister_device()

5.0MediumEPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 1c24e5fc0c7096e00c202a6a3e0c342c1afb47c2 and Kernel ffe02f7c4e36090154646612e67d331832f92037.

In the Linux kernel, the following vulnerability has been resolved: i2c: core: Fix double-free of fwnode in i2c_unregister_device() Before commit df6d7277e552 ("i2c: core: Do not dereference fwnode in struct device"), i2c_unregister_device() only called fwnode_handle_put() on of_node-s in the form of calling of_node_put(client->dev.of_node). But after this commit the i2c_client's fwnode now unconditionally gets fwnode_handle_put() on it. When the i2c_client has no primary (ACPI / OF) fwnode but it does have a software fwnode, the software-node will be the primary node and fwnode_handle_put() will put() it. But for the software fwnode device_remove_software_node() will also put() it leading to a double free: [ 82.665598] ------------[ cut here ]------------ [ 82.665609] refcount_t: underflow; use-after-free. [ 82.665808] WARNING: CPU: 3 PID: 1502 at lib/refcount.c:28 refcount_warn_saturate+0xba/0x11 ... [ 82.666830] RIP: 0010:refcount_warn_saturate+0xba/0x110 ... [ 82.666962] <TASK> [ 82.666971] i2c_unregister_device+0x60/0x90 Fix this by not calling fwnode_handle_put() when the primary fwnode is a software-node.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=6.16, >=df6d7277e5525d6cce63127dd93ebec4c6354fa0 <1c24e5fc0c7096e00c202a6a3e0c342c1afb47c2, >=df6d7277e5525d6cce63127dd93ebec4c6354fa0 <ffe02f7c4e36090154646612e67d331832f920371c24e5fc0c7096e00c202a6a3e0c342c1afb47c2, ffe02f7c4e36090154646612e67d331832f92037

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2025-38682 severity on Zeptric[![CVE-2025-38682](https://zeptric.io/badge/cve/CVE-2025-38682.svg)](https://zeptric.io/cve/CVE-2025-38682)