driver core: fix potential NULL pointer dereference in dev_uevent()
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.6.89, 6.12.26, 6.14.5
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From 16574dccd8f62dc1b585325f8a6a0aab10047ed8 · fixed in abe56be73eb10a677d16066f65ff9d30251f5eee; From 16574dccd8f62dc1b585325f8a6a0aab10047ed8 · fixed in 2b344e779d9afd0fcb5ee4000e4d0fc7d8d867eb; From 16574dccd8f62dc1b585325f8a6a0aab10047ed8 · fixed in 3781e4b83e174364998855de777e184cf0b62c40; From 16574dccd8f62dc1b585325f8a6a0aab10047ed8 · fixed in 18daa52418e7e4629ed1703b64777294209d2622
- Linux Linux
2.6.22
- KernelLinux
From 2.6.22 · fixed in 6.6.89; From 6.7.0 · fixed in 6.12.26; From 6.13.0 · fixed in 6.14.5