CVE-2022-48909
net/smc: fix connection leak
- Published
- Updated
- Reserved
- Assigned by
- Linux
Description
In the Linux kernel, the following vulnerability has been resolved: net/smc: fix connection leak There's a potential leak issue under following execution sequence : smc_release smc_connect_work if (sk->sk_state == SMC_INIT) send_clc_confirim tcp_abort(); ... sk.sk_state = SMC_ACTIVE smc_close_active switch(sk->sk_state) { ... case SMC_ACTIVE: smc_close_final() // then wait peer closed Unfortunately, tcp_abort() may discard CLC CONFIRM messages that are still in the tcp send buffer, in which case our connection token cannot be delivered to the server side, which means that we cannot get a passive close message at all. Therefore, it is impossible for the to be disconnected at all. This patch tries a very simple way to avoid this issue, once the state has changed to SMC_ACTIVE after tcp_abort(), we can actively abort the smc connection, considering that the state is SMC_INIT before tcp_abort(), abandoning the complete disconnection process should not cause too much problem. In fact, this problem may exist as long as the CLC CONFIRM message is not received by the server. Whether a timer should be added after smc_close_final() needs to be discussed in the future. But even so, this patch provides a faster release for connection in above case, it should also be valuable.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.24% · top 85% of all CVEs (6 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Weakness
Affected products
- affected 39f41f367b08650e9aa314e3a13fb6dda1e9eec7 – < 2e8d465b83db307f04ad265848f8ab3f78f6918f
- affected 39f41f367b08650e9aa314e3a13fb6dda1e9eec7 – < 80895b6f9154fb22d36fab311ccbb75503a2c87b
- affected 39f41f367b08650e9aa314e3a13fb6dda1e9eec7 – < e98d46ccfa84b35a9e4b1ccdd83961b41a5d7ce5
- affected 39f41f367b08650e9aa314e3a13fb6dda1e9eec7 – < 9f1c50cf39167ff71dc5953a3234f3f6eeb8fcb5
- affected 5.3
- unaffected < 5.3
- unaffected 5.10.104 – ≤ 5.10.*
- unaffected 5.15.27 – ≤ 5.15.*
- unaffected 5.16.13 – ≤ 5.16.*
- unaffected 5.17 – ≤ *
References (4)
- https://git.kernel.org/stable/c/2e8d465b83db307f04ad265848f8ab3f78f6918f (opens in a new tab)
- https://git.kernel.org/stable/c/80895b6f9154fb22d36fab311ccbb75503a2c87b (opens in a new tab)
- https://git.kernel.org/stable/c/e98d46ccfa84b35a9e4b1ccdd83961b41a5d7ce5 (opens in a new tab)
- https://git.kernel.org/stable/c/9f1c50cf39167ff71dc5953a3234f3f6eeb8fcb5 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://trackcve.app/cve/CVE-2022-48909)Record last updated .