CVE-2026-31688 Details
Description
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
A vulnerability in the Linux kernel's driver core has been addressed, specifically related to the handling of device locks during driver matching. The issue arose because the function 'driver_match_device()' was called from three different locations, two of which did not hold the necessary device lock. This inconsistency meant that bus match callbacks could be called without the lock, leading to a race condition. The vulnerability was particularly problematic for buses using the 'driver_override' field, causing a use-after-free error. The issue has been resolved by introducing a new function, 'driver_match_device_locked()', which ensures the device lock is held, and by replacing the unlocked calls in 'bind_store()' and '__driver_attach()' with this new helper. Stress testing the updated paths confirmed the absence of recurrence of the use-after-free issue and no lock dependency warnings.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No CVSS 3.x data is available for this CVE.
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
No references are available for this CVE.
Weakness Enumeration
No weakness enumeration is available for this CVE.
Affected Products
No affected product data is available for this CVE.
Change History
5 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Rejected | kernel.org |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Jun 17, 2026 | CVE Modified | kernel.org |
| May 6, 2026 | Initial Analysis | [email protected] |
| Apr 27, 2026 | New CVE Received | kernel.org |