VulnerabilityPublished 24 Jul 2026

CVE-2026-64242: Linux kernel · usb: gadget: net2280: Fix double free in probe error path

Affects Linux kernelSource GCVE Database

Compare

Not known to be exploited.

Data as of 8 Nov 2026, 16:36 UTC

Severity

High

Rated High by Threat Radar's AI analysis · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

Exploitation evidence

Disclosed: evidence found.
CVE published 24 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 8 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

The vulnerability has been fixed by removing the redundant kfree() call in the probe error path and relying on the gadget device's release callback for memory release. Users should apply the official Linux kernel update that includes this fix once available. Since this is a code-level fix in the kernel, upgrading to the patched kernel version is the recommended mitigation.

Description

A double free vulnerability was identified and fixed in the Linux kernel's usb gadget driver for net2280. The issue occurred in the probe error path where the device structure could be freed twice due to an explicit kfree call after the gadget device's release callback was already scheduled to free it. This flaw was detected by a static analysis tool and corrected by removing the redundant kfree call, ensuring proper memory management.

Impact

Double free vulnerabilities can lead to undefined behavior including potential memory corruption, system crashes, or escalation of privileges if exploited. However, there is no indication of known exploitation in the wild for this issue. The impact is limited to the Linux kernel's usb gadget net2280 driver and affects system stability and security if triggered.

Summary

The Linux kernel's usb gadget driver for net2280 had a double free vulnerability in its probe error path. Specifically, usb_initialize_gadget() sets gadget_release() as the release callback for the embedded gadget device, which frees the net2280 instance when the last reference is dropped. However, in the probe error path, net2280_remove() calls usb_put_gadget() to drop the gadget reference, and then an explicit kfree(dev) call could free the same object again, causing a double free. The fix involved removing the explicit kfree() call and relying on the gadget device's release callback to handle the final free operation.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 8 Nov 2026, 16:36 UTC

Technical details

References

Community reviews

Related threats