Memory Leak Affecting kernel-rt-modules-extra package, versions *
Threat Intelligence
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk ID SNYK-CENTOS8-KERNELRTMODULESEXTRA-7823781
- published 23 Aug 2024
- disclosed 22 Aug 2024
Introduced: 22 Aug 2024
CVE-2022-48909 Open this link in a new tabHow to fix?
There is no fixed version for Centos:8
kernel-rt-modules-extra
.
NVD Description
Note: Versions mentioned in the description apply only to the upstream kernel-rt-modules-extra
package and not the kernel-rt-modules-extra
package as distributed by Centos
.
See How to fix?
for Centos:8
relevant fixed versions and status.
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.
References
- https://access.redhat.com/security/cve/CVE-2022-48909
- https://git.kernel.org/stable/c/2e8d465b83db307f04ad265848f8ab3f78f6918f
- https://git.kernel.org/stable/c/80895b6f9154fb22d36fab311ccbb75503a2c87b
- https://git.kernel.org/stable/c/9f1c50cf39167ff71dc5953a3234f3f6eeb8fcb5
- https://git.kernel.org/stable/c/e98d46ccfa84b35a9e4b1ccdd83961b41a5d7ce5