In the Linux kernel, the following vulnerability has been resolved: afunix: Fix data races in unixreleasesock/unixstreamsendmsg A data-race condition has been identified in afunix. In one data path, the write function unixreleasesock() atomically writes to sk->skshutdown using WRITEONCE. However, on the reader side, unixstreamsendmsg() does not read it atomically. Consequently, this issue is causing the following KCSAN splat to occur: BUG: KCSAN: data-race in unixreleasesock / unixstreamsendmsg write (marked) to 0xffff88867256ddbb of 1 bytes by task 7270 on cpu 28: unixreleasesock (net/unix/afunix.c:640) unixrelease (net/unix/afunix.c:1050) sockclose (net/socket.c:659 net/socket.c:1421) fput (fs/filetable.c:422) _fputsync (fs/filetable.c:508) _sesysclose (fs/open.c:1559 fs/open.c:1541) _x64sysclose (fs/open.c:1541) x64syscall (arch/x86/entry/syscall64.c:33) dosyscall64 (arch/x86/entry/common.c:?) entrySYSCALL64afterhwframe (arch/x86/entry/entry64.S:130) read to 0xffff88867256ddbb of 1 bytes by task 989 on cpu 14: unixstreamsendmsg (net/unix/afunix.c:2273) _socksendmsg (net/socket.c:730 net/socket.c:745) _syssendmsg (net/socket.c:2584) _syssendmmsg (net/socket.c:2638 net/socket.c:2724) _x64syssendmmsg (net/socket.c:2753 net/socket.c:2750 net/socket.c:2750) x64syscall (arch/x86/entry/syscall64.c:33) dosyscall64 (arch/x86/entry/common.c:?) entrySYSCALL64afterhwframe (arch/x86/entry/entry64.S:130) value changed: 0x01 -> 0x03 The line numbers are related to commit dd5a440a31fa ("Linux 6.9-rc7"). Commit e1d09c2c2f57 ("afunix: Fix data races around sk->skshutdown.") addressed a comparable issue in the past regarding sk->skshutdown. However, it overlooked resolving this particular data path. This patch only offending unixstreamsendmsg() function, since the other reads seem to be protected by unixstate_lock() as discussed in