CVE-2026-53233

netdev: fix double-free in netdev_nl_bind_rx_doit()

Published Jun 25, 2026 CVSS 3.1 · 7.8 High EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

A double-free occurs in the netdev_nl_bind_rx_doit routine when a netlink reply has already been consumed by genlmsg_reply and the error path subsequently frees the socket buffer using nlmsg_free. The redundant release can corrupt kernel memory, potentially leading to a kernel crash or other unintended kernel state changes.

Affected Systems

All Linux kernel builds that do not include the patch introduced by commit 9b019376cbee10c4f9184d1745fa37d156e36f30 are affected. This encompasses every kernel version released before that commit. Distribution kernels that package the upstream source without the fix remain vulnerable until a security update incorporating the commit is applied.

Risk and Exploitability

The vulnerability is local; it is triggered when a netlink message path enters the error handling code that frees the socket buffer twice. No network-exposed vector is described. Exploitability depends on the ability of an attacker to send netlink requests that exercise this error path, which typically requires local access, but could be achieved by a non-root user depending on the semantics of the affected netlink interface. The CVSS score of 7.8 indicates a high severity, and the EPSS score is <1%, indicating a low but nonzero likelihood of exploitation. The issue is not listed in CISA KEV. The risk is significant because kernel memory corruption can destabilize the system and compromise availability.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply a Linux kernel version that incorporates commit 9b019376cbee10c4f9184d1745fa37d156e36f30 or later, which removes the double-free logic.
  • Install distribution-specific security updates that include the patched kernel image as soon as they are released.
  • Review and test local applications that send netlink traffic to ensure they do not generate messages that would activate the error path; consider enforcing size limits on receive buffers to prevent overflow scenarios.

Generated by OpenCVE AI on August 13, 2026 at 13:16 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Ubuntu USN Ubuntu USN USN-8726-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8727-1 Linux kernel (OEM) vulnerabilities
Ubuntu USN Ubuntu USN USN-8728-1 Linux kernel (GCP) vulnerabilities
Ubuntu USN Ubuntu USN USN-8760-1 Linux kernel (NVIDIA) vulnerabilities
Ubuntu USN Ubuntu USN USN-8726-2 Linux kernel (Raspberry Pi) vulnerabilities
Ubuntu USN Ubuntu USN USN-8726-3 Linux kernel (IBM) vulnerabilities
Ubuntu USN Ubuntu USN USN-8800-1 Linux kernel (NVIDIA BaseOS) vulnerabilities
Ubuntu USN Ubuntu USN USN-8760-2 Linux kernel (NVIDIA) vulnerabilities
Ubuntu USN Ubuntu USN USN-8726-4 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8728-2 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-8728-3 Linux kernel (Oracle) vulnerabilities
History
Type Values Removed Values Added
Weaknesses CWE-416
Type Values Removed Values Added
Weaknesses CWE-763
References
Metrics threat_severity

None

cvssV3_1

{'score': 7.0, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H'}

threat_severity

Moderate

Type Values Removed Values Added
Weaknesses CWE-416
Type Values Removed Values Added
Description 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.
Title netdev: fix double-free in netdev_nl_bind_rx_doit()
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Jun 25, 2026, 8:39 AM
Reserved
Jun 9, 2026, 7:44 AM
Status
Analyzed
Published
Jun 25, 2026, 9:16 AM
Modified
Jul 7, 2026, 11:46 PM
Severity
Moderate
Public date
Jun 25, 2026, 12:00 AM