driver core: fix potential NULL pointer dereference in dev_uevent()
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 18daa52418e7e4629ed1703b64777294209d2622, Kernel 2b344e779d9afd0fcb5ee4000e4d0fc7d8d867eb, Kernel 3781e4b83e174364998855de777e184cf0b62c40 and 1 more.
In the Linux kernel, the following vulnerability has been resolved: driver core: fix potential NULL pointer dereference in dev_uevent() If userspace reads "uevent" device attribute at the same time as another threads unbinds the device from its driver, change to dev->driver from a valid pointer to NULL may result in crash. Fix this by using READ_ONCE() when fetching the pointer, and take bus' drivers klist lock to make sure driver instance will not disappear while we access it. Use WRITE_ONCE() when setting the driver pointer to ensure there is no tearing.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =2.6.22, >=16574dccd8f62dc1b585325f8a6a0aab10047ed8 <18daa52418e7e4629ed1703b64777294209d2622, >=16574dccd8f62dc1b585325f8a6a0aab10047ed8 <2b344e779d9afd0fcb5ee4000e4d0fc7d8d867eb, >=16574dccd8f62dc1b585325f8a6a0aab10047ed8 <3781e4b83e174364998855de777e184cf0b62c40, >=16574dccd8f62dc1b585325f8a6a0aab10047ed8 <abe56be73eb10a677d16066f65ff9d30251f5eee | 18daa52418e7e4629ed1703b64777294209d2622, 2b344e779d9afd0fcb5ee4000e4d0fc7d8d867eb, 3781e4b83e174364998855de777e184cf0b62c40, abe56be73eb10a677d16066f65ff9d30251f5eee |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket