CVE-2026-99606: net/smc: don't spin in smc_rx_recvmsg() while a pipe holds spliced data

Published Nov 20, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

net/smc: don't spin in smcrxrecvmsg() 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 smcrxwait() returns at once on RCVSHUTDOWN. With a signal pending, after SHUTRD, or once the peer closes or shuts down writing, recvmsg() spins on a CPU until the pipe is drained, and SIGKILL cannot stop it. MSGDONTWAIT and an expired SORCVTIMEO 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 RCVSHUTDOWN. 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 SOCKWQASYNCWAITDATA like smcrxwait(), 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 splicepending, so no wake is lost.

Affected Software

7 affected componentsFixes available
linux/kernel>=4.18.0<6.12.118
6.12.118
linux/kernel>=6.13.0<6.18.64
6.18.64
linux/kernel>=6.19.0<7.3.5
7.3.5
debian/linux*
debian/linux*
debian/linux*
debian/linux<=6.1.176-1, <=6.1.192-2, <=6.12.107-1, <=6.12.117-1, <=7.3.4-1
7.3.5-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.12.118
  2. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.18.64
  3. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 7.3.5
  4. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 7.3.5-1
  5. Compensating control

    In net/smc smc_rx_recvmsg(), check for pending signals and an expired SO_RCVTIMEO before waiting, and end the wait when the pipe releases the spliced data or the connection is killed—not merely on RCV_SHUTDOWN.

Event History

Nov 20, 2026
CVE Published
via MITRE·05:49 AM
Data Sourced
via MITRE·05:49 AM
Description
Data Sourced
via OSV·05:49 AM
DescriptionAffected Software
Data Sourced
via NVD·06:17 AM
Description

Frequently Asked Questions

1

What conditions are required to trigger the CPU spin?

Bytes previously spliced from an SMC socket receive buffer must still be held in a pipe, and recvmsg() must then wait for data behind those bytes. The problematic behavior occurs with a pending signal, after SHUT_RD, or after the peer closes or shuts down its write side.

2

Are non-blocking sockets and receive timeouts affected?

Yes. MSG_DONTWAIT and an already expired SO_RCVTIMEO can wait on the pipe-held data instead of returning -EAGAIN.

3

Can a stuck recvmsg() be interrupted or killed?

In the affected wait path, pending signals are skipped, and the description states that SIGKILL cannot stop the spinning task until the pipe is drained. Draining the pipe releases the spliced data and ends that wait condition.

4

How does the fixed behavior differ for reads while spliced data remains in a pipe?

A zero-length read returns 0 without waiting. A non-blocking read returns -EAGAIN while the pipe holds the data, although poll() may still report the socket as readable because splice() can consume those bytes.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203