CVE-2018-5814: Race Condition
In the Linux Kernel before version 4.16.11, 4.14.43, 4.9.102, and 4.4.133, multiple race condition errors when handling probe, disconnect, and rebind operations can be exploited to trigger a use-after-free condition or a NULL pointer dereference by sending multiple USB over IP packets.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.176-1Fixed in 6.1.187-1Fixed in 6.12.107-1Fixed in 6.12.111-1Fixed in 7.2.9-1Fixed in 7.2.10-1 - Upgrade
Upgrade
Linux Kernelto a version that resolves this vulnerability.Fixed in 4.16.11 - Upgrade
Upgrade
Linux Kernelto a version that resolves this vulnerability.Fixed in 4.14.43 - Upgrade
Upgrade
Linux Kernelto a version that resolves this vulnerability.Fixed in 4.9.102 - Upgrade
Upgrade
Linux Kernelto a version that resolves this vulnerability.Fixed in 4.4.133
Event History
Frequently Asked Questions
What is the severity of CVE-2018-5814?
CVE-2018-5814 is categorized as a high severity vulnerability due to its potential to cause use-after-free conditions and null pointer dereferences.
How do I fix CVE-2018-5814?
To fix CVE-2018-5814, upgrade to Linux Kernel versions 4.16.11 or newer, 4.14.43 or newer, 4.9.102 or newer, or 4.4.133 or newer.
Which Linux versions are affected by CVE-2018-5814?
CVE-2018-5814 affects Linux Kernel versions prior to 4.16.11, 4.14.43, 4.9.102, and 4.4.133.
What are the consequences of exploiting CVE-2018-5814?
Exploiting CVE-2018-5814 can lead to application crashes and potential system instability due to race condition vulnerabilities.
Is there a workaround for CVE-2018-5814?
As of now, the recommended action is to apply the fix by upgrading the affected Linux Kernel versions as no specific workarounds are documented.