Answer in brief
CVE-2026-80982 records a Unknown severity vulnerability in net/smc: fix use-after-free in smc_rx_pipe_buf_release(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=9014db202cb764b8e14c53e7bacc81f9a1a2ba7f <6a644a7340df978785f3109d1e0726a982ce2c6f || >=9014db202cb764b8e14c53e7bacc81f9a1a2ba7f <0761e49aa78c2f1362511054c6e9670653858837 || >=9014db202cb764b8e14c53e7bacc81f9a1a2ba7f <0926f59ca0f94120895b92180c636a48d0ed3a6d || >=9014db202cb764b8e14c53e7bacc81f9a1a2ba7f <c924884743e948e25625b7fbf3ee2a9325a204a7 | 6a644a7340df978785f3109d1e0726a982ce2c6f, 0761e49aa78c2f1362511054c6e9670653858837, 0926f59ca0f94120895b92180c636a48d0ed3a6d, c924884743e948e25625b7fbf3ee2a9325a204a7 |
| Linux/Linuxgeneric | 4.18 | Not reported |
Published upstream
Sep 11, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 11, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 11, 2026
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.
Quoted source text, attributed separately from HOL analysis.