Answer in brief
CVE-2025-38154 records a Unknown severity vulnerability in bpf, sockmap: Avoid using sk_socket after free when sending. 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.
Answer in brief
CVE-2025-38154 records a Unknown severity vulnerability in bpf, sockmap: Avoid using sk_socket after free when sending. 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 | >=4959ffc65a0e94f8acaac20deac49f89e6ded52d <4edb40b05cb6a261775abfd8046804ca139a5546 || >=5eabdf17fed2ad41b836bb4055ec36d95e512c50 <b19cbf0b9a91f5a0d93fbcd761ff71c48ab40ed9 || >=e946428439a0d2079959f5603256ac51b6047017 <4c6fa65ab2aec7df94809478c8d28ef38676a1b7 || >=4b4647add7d3c8530493f7247d11e257ee425bf0 <15c0250dae3b48a398447d2b364603821ed4ed90 || >=4b4647add7d3c8530493f7247d11e257ee425bf0 <7c0a16f6ea2b1c82a03bccd5d1bdb4a7bbd4d987 || >=4b4647add7d3c8530493f7247d11e257ee425bf0 <8259eb0e06d8f64c700f5fbdb28a5c18e10de291 || 3627605de498639a3c586c8684d12c89cba11073 || >=5.15.162 <5.15.186 || >=6.1.95 <6.1.142 || >=6.6.35 <6.6.94 || >=6.9.6 <6.10 | 4edb40b05cb6a261775abfd8046804ca139a5546, b19cbf0b9a91f5a0d93fbcd761ff71c48ab40ed9, 4c6fa65ab2aec7df94809478c8d28ef38676a1b7, 15c0250dae3b48a398447d2b364603821ed4ed90, 7c0a16f6ea2b1c82a03bccd5d1bdb4a7bbd4d987, 8259eb0e06d8f64c700f5fbdb28a5c18e10de291, 5.15.186, 6.1.142, 6.6.94, 6.10 |
| Linux/Linuxgeneric | 6.10 | Not reported |
Published upstream
Jul 3, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: bpf, sockmap: Avoid using sk_socket after free when sending The sk->sk_socket is not locked or referenced in backlog thread, and during the call to skb_send_sock(), there is a race condition with the release of sk_socket. All types of sockets(tcp/udp/unix/vsock) will be affected. Race conditions: ''' CPU0 CPU1 backlog::skb_send_sock sendmsg_unlocked sock_sendmsg sock_sendmsg_nosec close(fd): ... ops->release() -> sock_map_close() sk_socket->ops = NULL free(socket) sock->ops->sendmsg ^ panic here ''' The ref of psock become 0 after sock_map_close() executed. ''' void sock_map_close() { ... if (likely(psock)) { ... // !! here we remove psock and the ref of psock become 0 sock_map_remove_links(sk, psock) psock = sk_psock_get(sk); if (unlikely(!psock)) goto no_psock; <=== Control jumps here via goto ... cancel_delayed_work_sync(&psock->work); <=== not executed sk_psock_put(sk, psock); ... } ''' Based on the fact that we already wait for the workqueue to finish in sock_map_close() if psock is held, we simply increase the psock reference count to avoid race conditions. With this patch, if the backlog thread is running, sock_map_close() will wait for the backlog thread to complete and cancel all pending work. If no backlog running, any pending work that hasn't started by then will fail when invoked by sk_psock_get(), as the psock reference count have been zeroed, and sk_psock_drop() will cancel all jobs via cancel_delayed_work_sync(). In summary, we require synchronization to coordinate the backlog thread and close() thread. The panic I catched: ''' Workqueue: events sk_psock_backlog RIP: 0010:sock_sendmsg+0x21d/0x440 RAX: 0000000000000000 RBX: ffffc9000521fad8 RCX: 0000000000000001 ... Call Trace: <TASK> ? die_addr+0x40/0xa0 ? exc_general_protection+0x14c/0x230 ? asm_exc_general_protection+0x26/0x30 ? sock_sendmsg+0x21d/0x440 ? sock_sendmsg+0x3e0/0x440 ? __pfx_sock_sendmsg+0x10/0x10 __skb_send_sock+0x543/0xb70 sk_psock_backlog+0x247/0xb80 ... '''
Quoted source text, attributed separately from HOL analysis.
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 | >=4959ffc65a0e94f8acaac20deac49f89e6ded52d <4edb40b05cb6a261775abfd8046804ca139a5546 || >=5eabdf17fed2ad41b836bb4055ec36d95e512c50 <b19cbf0b9a91f5a0d93fbcd761ff71c48ab40ed9 || >=e946428439a0d2079959f5603256ac51b6047017 <4c6fa65ab2aec7df94809478c8d28ef38676a1b7 || >=4b4647add7d3c8530493f7247d11e257ee425bf0 <15c0250dae3b48a398447d2b364603821ed4ed90 || >=4b4647add7d3c8530493f7247d11e257ee425bf0 <7c0a16f6ea2b1c82a03bccd5d1bdb4a7bbd4d987 || >=4b4647add7d3c8530493f7247d11e257ee425bf0 <8259eb0e06d8f64c700f5fbdb28a5c18e10de291 || 3627605de498639a3c586c8684d12c89cba11073 || >=5.15.162 <5.15.186 || >=6.1.95 <6.1.142 || >=6.6.35 <6.6.94 || >=6.9.6 <6.10 | 4edb40b05cb6a261775abfd8046804ca139a5546, b19cbf0b9a91f5a0d93fbcd761ff71c48ab40ed9, 4c6fa65ab2aec7df94809478c8d28ef38676a1b7, 15c0250dae3b48a398447d2b364603821ed4ed90, 7c0a16f6ea2b1c82a03bccd5d1bdb4a7bbd4d987, 8259eb0e06d8f64c700f5fbdb28a5c18e10de291, 5.15.186, 6.1.142, 6.6.94, 6.10 |
| Linux/Linuxgeneric | 6.10 | Not reported |
Published upstream
Jul 3, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: bpf, sockmap: Avoid using sk_socket after free when sending The sk->sk_socket is not locked or referenced in backlog thread, and during the call to skb_send_sock(), there is a race condition with the release of sk_socket. All types of sockets(tcp/udp/unix/vsock) will be affected. Race conditions: ''' CPU0 CPU1 backlog::skb_send_sock sendmsg_unlocked sock_sendmsg sock_sendmsg_nosec close(fd): ... ops->release() -> sock_map_close() sk_socket->ops = NULL free(socket) sock->ops->sendmsg ^ panic here ''' The ref of psock become 0 after sock_map_close() executed. ''' void sock_map_close() { ... if (likely(psock)) { ... // !! here we remove psock and the ref of psock become 0 sock_map_remove_links(sk, psock) psock = sk_psock_get(sk); if (unlikely(!psock)) goto no_psock; <=== Control jumps here via goto ... cancel_delayed_work_sync(&psock->work); <=== not executed sk_psock_put(sk, psock); ... } ''' Based on the fact that we already wait for the workqueue to finish in sock_map_close() if psock is held, we simply increase the psock reference count to avoid race conditions. With this patch, if the backlog thread is running, sock_map_close() will wait for the backlog thread to complete and cancel all pending work. If no backlog running, any pending work that hasn't started by then will fail when invoked by sk_psock_get(), as the psock reference count have been zeroed, and sk_psock_drop() will cancel all jobs via cancel_delayed_work_sync(). In summary, we require synchronization to coordinate the backlog thread and close() thread. The panic I catched: ''' Workqueue: events sk_psock_backlog RIP: 0010:sock_sendmsg+0x21d/0x440 RAX: 0000000000000000 RBX: ffffc9000521fad8 RCX: 0000000000000001 ... Call Trace: <TASK> ? die_addr+0x40/0xa0 ? exc_general_protection+0x14c/0x230 ? asm_exc_general_protection+0x26/0x30 ? sock_sendmsg+0x21d/0x440 ? sock_sendmsg+0x3e0/0x440 ? __pfx_sock_sendmsg+0x10/0x10 __skb_send_sock+0x543/0xb70 sk_psock_backlog+0x247/0xb80 ... '''
Quoted source text, attributed separately from HOL analysis.