https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 30 Sep 2026 21:15:04 +0000 https://db.gcve.eu/vuln/cve-2026-93081 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>firmware: arm_scmi: Fix SCMI device destroy lifetimes</p> <p>scmi_child_dev_find() drops the reference returned by device_find_child() before returning the scmi_device pointer. A concurrent unregister can then release the device while the destroy path is still using the returned pointer.</p> <p>Make the lookup helper return the device_find_child() reference and keep it until scmi_device_destroy() has finished unregistering the child.</p> <p>Also split device_unregister() in __scmi_device_destroy() so the SCMI bus ID is not made reusable until after device_del() has removed the old scmi_dev.N name from sysfs. This avoids a new SCMI device reusing the same ID while the old device is still registered.</p> <p>The final device release callback is also a possible cleanup path when SCMI children are deleted by driver core recursion rather than __scmi_device_destroy(). Release the SCMI bus ID from a common helper used by destroy, register-failure and final-release paths, and clear scmi_dev-&gt;id after freeing it so the final release cannot free the same ID again.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>firmware: arm_scmi: Fix SCMI device destroy lifetimes</p> <p>scmi_child_dev_find() drops the reference returned by device_find_child() before returning the scmi_device pointer. A concurrent unregister can then release the device while the destroy path is still using the returned pointer.</p> <p>Make the lookup helper return the device_find_child() reference and keep it until scmi_device_destroy() has finished unregistering the child.</p> <p>Also split device_unregister() in __scmi_device_destroy() so the SCMI bus ID is not made reusable until after device_del() has removed the old scmi_dev.N name from sysfs. This avoids a new SCMI device reusing the same ID while the old device is still registered.</p> <p>The final device release callback is also a possible cleanup path when SCMI children are deleted by driver core recursion rather than __scmi_device_destroy(). Release the SCMI bus ID from a common helper used by destroy, register-failure and final-release paths, and clear scmi_dev-&gt;id after freeing it so the final release cannot free the same ID again.</p> https://db.gcve.eu/vuln/cve-2026-93081