CVE-2026-74493
CVE CVE-2026-74493EUVD EUVD-2026-59686Published 2026-08-15T12:27:21.000ZLast changed 2026-08-19T16:37:50.000ZCVSS 9.8
What the advisory describes
In the Linux kernel, the following vulnerability has been resolved: net/smc: fix socket use-after-free during link group termination __smc_lgr_terminate() drops conns_lock after finding a connection in lgr->conns_all, but before taking a reference on its socket. The connection is embedded in the socket, and its registration reference protects it only while the connection remains in the tree. A concurrent close can unregister the connection and drop that reference, freeing the socket before the termination worker reaches sock_hold(). The race is reachable when close overlaps link group termination. Local stress testing reproduced the use-after-free and KASAN reported: BUG: KASAN: slab-use-after-free in __smc_lgr_terminate.part.0 [smc] Write of size 4 by task kworker/3:3 Workqueue: events smc_lgr_terminate_work [smc] __smc_lgr_terminate.part.0 [smc] The socket was allocated by smc_create(), freed through slab_free_after_rcu_debug(), and was followed by: refcount_t: addition on 0; use-after-free. __smc_lgr_terminate.part.0 [smc] Take the socket reference while conns_lock still protects the tree entry. The unregister path then cannot drop the last reference until termination has finished using the socket.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux patch: 6.18.44; 69318b5215f2dc32c345a3d65b98b4b1bf29c007 <ff44f2df57fb5560bdc75eb977867643e764a262; 69318b5215f2dc32c345a3d65b98b4b1bf29c007 <281c103a8eaed59001ce952f231df1b07674215a; patch: 5.15.216; 69318b5215f2dc32c345a3d65b98b4b1bf29c007 <f0541a775d04c88e90ba448e35ce0d743512822a; 69318b5215f2dc32c345a3d65b98b4b1bf29c007 <9fb17c95b8f0683570fca1fb2792264147af937a; 69318b5215f2dc32c345a3d65b98b4b1bf29c007 <f807a63d0d95680c34f677700da9148a07d7c78f; 5.5; patch: 7.2; 69318b5215f2dc32c345a3d65b98b4b1bf29c007 <bea8dc14de2d56aca749d368563e6888217710a5; patch: 7.1.8; patch: 5.10.265; patch: 6.1.183; 69318b5215f2dc32c345a3d65b98b4b1bf29c007 <f621d6ebeebb6374342571e4ddf45fdbc420f6cd; 69318b5215f2dc32c345a3d65b98b4b1bf29c007 <5a42f162b857019a4c10ff687dc3bcdf51831865; patch: 0; patch: 6.12.103; patch: 6.6.151
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.