Bug 2492809 (CVE-2026-53233)

Summary: CVE-2026-53233 kernel: netdev: fix double-free in netdev_nl_bind_rx_doit()
Product: [Other] Security Response Reporter: OSIDB Bzimport <bzimport>
Component: vulnerabilityAssignee: Product Security <prodsec-ir-bot>
Status: NEW --- QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: rhel-process-autobot, watson-tool-maintainers
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
A flaw was found in the Linux kernel. A double-free vulnerability exists within the `netdev_nl_bind_rx_doit()` function, which is responsible for binding network device receive operations. This vulnerability arises when `genlmsg_reply()` consumes the socket buffer (`skb`), and the error handling path subsequently attempts to free the response (`rsp`) again, resulting in a double-free. This could allow a local attacker to cause a denial of service (DoS) or potentially execute arbitrary code.
 Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description OSIDB Bzimport 2026-06-25 10:06:57 UTC 
In the Linux kernel, the following vulnerability has been resolved:

netdev: fix double-free in netdev_nl_bind_rx_doit()

Sashiko flags that genlmsg_reply() always consumes the skb.
The error path calls nlmsg_free(rsp) so we can't jump directly
to it. Let's not unbind, just propagate the error to the user.
This is the typical way of handling genlmsg_reply() failures.
They shouldn't happen unless user does something silly like
calling the kernel with an already-full rcvbuf.
Comment 1 Keith Grant 2026-06-26 01:02:52 UTC 
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2026062509-CVE-2026-53233-508b@gregkh/T