VulnerabilityPublished 30 Oct 2025

CVE-2025-40091: Linux kernel · ixgbe: fix too early devlink_free() in ixgbe_remove()

Source GCVE Database

Compare

Not known to be exploited.

Data as of 29 Oct 2026, 23:09 UTC

Severity

Medium

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

Exploitation evidence

Disclosed: evidence found.
CVE published 30 Oct 2025
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 29 Oct 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.

ghsa-gq9j-j338-8fvx

What to do

AI-suggested

A fix has been implemented by moving the devlink_free() call to the end of the ixgbe_remove() function. Users should update to a Linux kernel version that includes this fix once it is released.

Description

A use-after-free vulnerability was identified and fixed in the ixgbe driver of the Linux kernel. The issue involved calling devlink_free() too early in the ixgbe_remove() function, which could lead to use-after-free (UAF) conditions. The fix involved moving the devlink_free() call to the end of the removal path to prevent premature freeing of resources.

Impact

This vulnerability could lead to use-after-free conditions in the ixgbe driver, potentially causing kernel crashes or undefined behavior. However, there is no indication of known exploits in the wild or direct impact beyond the UAF condition reported by KASAN.

Summary

The Linux kernel's ixgbe driver contained a vulnerability where devlink_free() was called prematurely in the ixgbe_remove() function. Since the ixgbe_adapter is embedded in devlink, this premature call could cause a use-after-free (UAF) condition. The kernel's KASAN (Kernel Address Sanitizer) detected this issue during the ixgbe_reset_interrupt_capability function, showing a read of freed memory. The fix was to move the devlink_free() call to the end of the ixgbe_remove() function to ensure proper resource cleanup without premature freeing.

References

Community reviews

Loading reviews…