nvmet-tcp: Incorrect Locking in state_change sk callback
Summary
GSD-2021-1000369: nvmet-tcp: fix incorrect locking in state_change sk callback. Affects Kernel versions >= 872d26a391da92ed8f0c0f5cb5fef428067b7f30, < 60ade0d56b06537a28884745059b3801c78e03bc. No fix is published. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The nvmet-tcp package is a component of the Linux Kernel ecosystem. It provides support for the NVMe over TCP protocol, allowing remote access to NVMe storage devices over a TCP/IP network. The package is responsible for handling state changes in the TCP socket (sk) callback.
Vulnerability Detail
The vulnerability in nvmet-tcp arises from incorrect locking in the state_change sk callback. This flaw can potentially lead to race conditions and other synchronization issues, which may result in unexpected behavior or crashes. Although the impact and attack plausibility have not been proven, it is crucial to address this vulnerability to ensure the stability and security of the system.
How To Fix
No fixed version is published for this vulnerability.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Conclusion
The nvmet-tcp package in the Linux Kernel is vulnerable to incorrect locking in the state_change sk callback. It is recommended to update the Kernel to version v5.10.37 or later to fix this vulnerability. For further support on vulnerability remediation, you can contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
nvmet-tcp is a component of the Linux Kernel that enables remote access to NVMe storage devices over a TCP/IP network.
The impact of this vulnerability is not yet proven, but it can potentially lead to race conditions and synchronization issues, resulting in unexpected behavior or crashes.
To fix this vulnerability, update the Linux Kernel to version v5.10.37 or later, which includes the necessary fix for the incorrect locking in the state_change sk callback.
No specific workarounds have been mentioned for this vulnerability.
For more information about this vulnerability, you can refer to the source link provided in the database_specific section of the vulnerability details.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.