PT-2026-152486

CVE-2026-99606

·

Published

2026-11-20

·

Updated

2026-11-20

Description by

Score
N/A
Not available

No severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.

In the Linux kernel, the following vulnerability has been resolved:
net/smc: don't spin in smc rx recvmsg() while a pipe holds spliced data
While bytes spliced off the RMB are still in a pipe, recvmsg() waits for the pipe to release them before it copies the data behind them. The path to that wait skips the timeout and signal checks, and smc rx wait() returns at once on RCV SHUTDOWN. With a signal pending, after SHUT RD, or once the peer closes or shuts down writing, recvmsg() spins on a CPU until the pipe is drained, and SIGKILL cannot stop it. MSG DONTWAIT and an expired SO RCVTIMEO wait there too instead of returning -EAGAIN.
Check the timeout and signals before that wait, and end it when the pipe releases the data or the connection is killed, not on RCV SHUTDOWN. A zero-length read returns 0 without waiting for the pipe; a non-blocking one returns -EAGAIN while poll() still reports the socket readable (splice() can still take those bytes). The wait sets SOCKWQ ASYNC WAITDATA like smc rx wait(), so a byte arriving behind the pipe raises no SIGIO on a reader already asleep for it, and a full barrier orders its wait queue entry before its read of splice pending, so no wake is lost.
Vendors
Affected products
Related identifiers
Found an issue in the description? Have something to add? Feel free to write us 👾