driver core: use READ_ONCE() for dev->driver in dev_has_sync_state()

Summary

In the Linux kernel, the following vulnerability has been resolved: driver core: use READ_ONCE() for dev->driver in dev_has_sync_state() dev_has_sync_state() reads dev->driver twice without holding device_lock() -- once for the NULL check and once to dereference ->sync_state. Some callers only hold device_links_write_lock, which doesn't prevent a concurrent unbind from clearing dev->driver via device_unbind_cleanup(). Fix it by reading dev->driver exactly once with READ_ONCE(), pairing with the WRITE_ONCE() in device_set_driver().

Timeline

1. Aug 28, 2026, 6:49 AM UTCCVE published
2. Oct 16, 2026, 7:19 PM UTCCISA SSVC assessment

   Exploitation: none · Automatable: no · Technical impact: total

3. Oct 16, 2026, 7:26 PM UTCRecord last updated

Affected versions

• Linux Linux

  From ac338acf514e7b578fa9e3742ec2c292323b4c1a · fixed in 89789e4c141904506163dcb91c7289a074573931; From ac338acf514e7b578fa9e3742ec2c292323b4c1a · fixed in 51b3e1de53ee5b7775c7ff90e67fdb2665fce938; From ac338acf514e7b578fa9e3742ec2c292323b4c1a · fixed in 358697929351f619143f59c6a8a15a4994748b79; From ac338acf514e7b578fa9e3742ec2c292323b4c1a · fixed in 5e79e0180515b31b2e2244dc3d256fd8b5a07021; From ac338acf514e7b578fa9e3742ec2c292323b4c1a · fixed in 860885fcd2611bca8c28dac8b2c1c7ff160f763e; From ac338acf514e7b578fa9e3742ec2c292323b4c1a · fixed in cc77f0d91e3214e4292208f02a1dc09a31f9aac7; From ac338acf514e7b578fa9e3742ec2c292323b4c1a · fixed in 9b0f4082a09760939588135d60a8e9cc994bfa3e; From ac338acf514e7b578fa9e3742ec2c292323b4c1a · fixed in e9506871a8ea304cde48ff4a57226df2aadddae3; From 5.5.13 · fixed in 5.6

• Linux Linux

  5.6

• KernelLinux

  From 5.6.0 · fixed in 5.10.261; From 5.11.0 · fixed in 5.15.212; From 5.16.0 · fixed in 6.1.178; From 6.2.0 · fixed in 6.6.145; From 6.7.0 · fixed in 6.12.97; From 6.13.0 · fixed in 6.18.40; From 6.19.0 · fixed in 7.1.5

References 8