Linux hwe edge: 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… (CVE-2025-38154)
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 ... '''
AI Analysis
Technical Summary
The advisory covers a set of security fixes and bug enhancements for the Linux kernel in Red Hat Enterprise Linux 10.0 Extended Update Support. Key security fixes include a use-after-free in BPF sockmap (CVE-2025-38154) enabling denial of service and privilege escalation, multiple use of Read-Copy-Update (RCU) fixes in IPv6 networking code (CVE-2025-40135, CVE-2025-40158), denial of service in libceph OSD client (CVE-2026-23136), use-after-free in CAN isotp_sendmsg (CVE-2026-31474), and several other kernel subsystem vulnerabilities. The advisory references multiple CVEs and bugzilla fixes. The update is rated as Important by Red Hat Product Security and requires a system reboot. No CVSS scores are provided in the advisory. The affected products include various architectures of Red Hat Enterprise Linux 10.0 EUS and CodeReady Linux Builder 10.0 EUS.
Potential Impact
The vulnerabilities fixed in this advisory can lead to denial of service and privilege escalation on affected systems running vulnerable kernel versions. The use-after-free bugs in critical kernel components such as BPF sockmap and CAN protocol can be exploited to crash the system or escalate privileges. Networking stack fixes address potential stability and security issues in IPv6 and SCTP. The denial of service in libceph OSD client can affect storage reliability. Overall, the impact is significant for systems running affected kernel versions without the update.
Mitigation Recommendations
Red Hat has released an updated kernel package addressing these vulnerabilities. Systems running Red Hat Enterprise Linux 10.0 Extended Update Support and related products should apply the update as described in the Red Hat advisory RHSA-2026:27731. A system reboot is required for the update to take effect. No alternative mitigations are indicated; applying the official update is the recommended remediation.
Linux hwe edge: 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… (CVE-2025-38154)
Description
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 ... '''
CVSS v3.1
Score 7.8high
Affected software
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The advisory covers a set of security fixes and bug enhancements for the Linux kernel in Red Hat Enterprise Linux 10.0 Extended Update Support. Key security fixes include a use-after-free in BPF sockmap (CVE-2025-38154) enabling denial of service and privilege escalation, multiple use of Read-Copy-Update (RCU) fixes in IPv6 networking code (CVE-2025-40135, CVE-2025-40158), denial of service in libceph OSD client (CVE-2026-23136), use-after-free in CAN isotp_sendmsg (CVE-2026-31474), and several other kernel subsystem vulnerabilities. The advisory references multiple CVEs and bugzilla fixes. The update is rated as Important by Red Hat Product Security and requires a system reboot. No CVSS scores are provided in the advisory. The affected products include various architectures of Red Hat Enterprise Linux 10.0 EUS and CodeReady Linux Builder 10.0 EUS.
Potential Impact
The vulnerabilities fixed in this advisory can lead to denial of service and privilege escalation on affected systems running vulnerable kernel versions. The use-after-free bugs in critical kernel components such as BPF sockmap and CAN protocol can be exploited to crash the system or escalate privileges. Networking stack fixes address potential stability and security issues in IPv6 and SCTP. The denial of service in libceph OSD client can affect storage reliability. Overall, the impact is significant for systems running affected kernel versions without the update.
Mitigation Recommendations
Red Hat has released an updated kernel package addressing these vulnerabilities. Systems running Red Hat Enterprise Linux 10.0 Extended Update Support and related products should apply the update as described in the Red Hat advisory RHSA-2026:27731. A system reboot is required for the update to take effect. No alternative mitigations are indicated; applying the official update is the recommended remediation.
Technical Details
- Gcve Source
- db.gcve.eu
- Csaf Category
- csaf_security_advisory
- Csaf Version
- 2.0
- Publisher
- Red Hat Product Security
- Advisory Id
- RHSA-2026:7100
- Cve Count
- 5
- Additional Cves
- ["CVE-2025-38180","CVE-2025-38206","CVE-2025-38248","CVE-2026-23209"]
- Cvss Version
- null
Threat ID: 6a27e9928dd33fbd85169e54
Added to database: 06/09/2026, 10:23:14 UTC
Last enriched: 07/30/2026, 15:07:36 UTC
Last updated: 08/01/2026, 07:17:56 UTC
Views: 101
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.