HomeDefault status
unaffected
675b453e024154dd547921c6e6d5b58747ba7e0e (git) before 6e0c7503a5803d568d56a9f9bca662cd94a14908
affected
675b453e024154dd547921c6e6d5b58747ba7e0e (git) before 1c90f930e7b410dd2d75a2a19a85e19c64e98ad5
affected
675b453e024154dd547921c6e6d5b58747ba7e0e (git) before 2fa8961d3a6a1c2395d8d560ffed2c782681bade
affected
Default status
affected
6.7
affected
Any version before 6.7
unaffected
6.12.70 (semver)
unaffected
6.18.10 (semver)
unaffected
6.19 (original_commit_for_fix)
unaffected
Description
In the Linux kernel, the following vulnerability has been resolved: nvmet-tcp: fixup hang in nvmet_tcp_listen_data_ready() When the socket is closed while in TCP_LISTEN a callback is run to flush all outstanding packets, which in turns calls nvmet_tcp_listen_data_ready() with the sk_callback_lock held. So we need to check if we are in TCP_LISTEN before attempting to get the sk_callback_lock() to avoid a deadlock.
Product status
675b453e024154dd547921c6e6d5b58747ba7e0e (git) before 6e0c7503a5803d568d56a9f9bca662cd94a14908
675b453e024154dd547921c6e6d5b58747ba7e0e (git) before 1c90f930e7b410dd2d75a2a19a85e19c64e98ad5
675b453e024154dd547921c6e6d5b58747ba7e0e (git) before 2fa8961d3a6a1c2395d8d560ffed2c782681bade
6.7
Any version before 6.7
6.12.70 (semver)
6.18.10 (semver)
6.19 (original_commit_for_fix)
References
git.kernel.org/...c/6e0c7503a5803d568d56a9f9bca662cd94a14908
git.kernel.org/...c/1c90f930e7b410dd2d75a2a19a85e19c64e98ad5
git.kernel.org/...c/2fa8961d3a6a1c2395d8d560ffed2c782681bade