Skip to main content
VulnerabilityPublished

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

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-99606· High

Not known to be exploited · fixed in f97e7bce1cb1f2c7fc3c0afb1818c7e568624ef7 : patch Linux kernel soon.

Data as of 20 Nov 2026, 07:34 UTC

Severity
High

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in f97e7bce1cb1f2c7fc3c0afb1818c7e568624ef7, 8288ba942cfd20621c05e16978b7c3da91513ae1, 883b66d11ee3ed89cc22599280d3c319cf38903f +1

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade Linux kernel to f97e7bce1cb1f2c7fc3c0afb1818c7e568624ef7, 8288ba942cfd20621c05e16978b7c3da91513ae1, 883b66d11ee3ed89cc22599280d3c319cf38903f or 16bbd8c8381c01598ae91bc72e62f617353d9bd9.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 9014db202cb764b8e14c53e7bacc81f9a1a2ba7f, < f97e7bce1cb1f2c7fc3c0afb1818c7e568624ef7
Fixed in
  • f97e7bce1cb1f2c7fc3c0afb1818c7e568624ef7
LinuxLinuxAffected
  • ≥ 9014db202cb764b8e14c53e7bacc81f9a1a2ba7f, < 8288ba942cfd20621c05e16978b7c3da91513ae1
Fixed in
  • 8288ba942cfd20621c05e16978b7c3da91513ae1
LinuxLinuxAffected
  • ≥ 9014db202cb764b8e14c53e7bacc81f9a1a2ba7f, < 883b66d11ee3ed89cc22599280d3c319cf38903f
Fixed in
  • 883b66d11ee3ed89cc22599280d3c319cf38903f
LinuxLinuxAffected
  • ≥ 9014db202cb764b8e14c53e7bacc81f9a1a2ba7f, < 16bbd8c8381c01598ae91bc72e62f617353d9bd9
Fixed in
  • 16bbd8c8381c01598ae91bc72e62f617353d9bd9
LinuxLinuxAffected
  • =4.18
Fixed in–

Description

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.

References

Community reviews

Loading reviews…