CVE-2026-80982

net/smc: fix use-after-free in smc_rx_pipe_buf_release()

CVE-2026-80982 is fixed in 2 products on 1 platform, first by DEBIAN-CVE-2026-80982, released September 23, 2026. It is not reported as exploited. Patch Radar priority: High.

High
CVSS
7.8
Important
Exploitation
None reported
No vendor assessment
CISA KEV
Not listed
Not in the Known Exploited Vulnerabilities catalog
EPSS
0.0016
5th percentile

In the Linux kernel, the following vulnerability has been resolved: net/smc: fix use-after-free in smc_rx_pipe_buf_release() smc_rx_splice() hands RMB pages to a pipe and takes a socket reference per entry so the smc_sock stays alive until the reader finishes. The connection does not: a concurrent close runs smc_conn_free(), which releases the receive buffer back to the link group pool. smc_rx_pipe_buf_release() tests sk_state before taking the socket lock. The state can change between the test and the lock, and smc_rx_update_cons() then dereferences conn->rmb_desc and walks conn->lgr, which smc_conn_free() has already released. On the is_reg_err path smcr_buf_unuse() frees the descriptor outright, so this is a use-after-free. Take the socket lock first and test conn->freed instead. smc_conn_free() sets that flag before releasing anything, and every caller holds the socket lock. The two paths exclude each other: either the pipe release runs first with everything valid, or it sees the flag and skips the update.

Where it's fixed

ProductFixed inFixReleased
Linux
linux · Debian 12.15 (bookworm) 6.1.190-1 DEBIAN-CVE-2026-80982 Sep 23, 2026
linux · Debian 13.5 (trixie) 6.12.111-1 DEBIAN-CVE-2026-80982 Sep 23, 2026
linux · Debian 14 7.2.6-1 DEBIAN-CVE-2026-80982 Sep 23, 2026
linux-6.12 · Debian 12.15 (bookworm) 6.12.111-1~deb12u1 DEBIAN-CVE-2026-80982 Sep 23, 2026

Patch Radar data is free to use with attribution. Terms and how to credit it.

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.