CVE-2025-39922: ixgbe: fix incorrect map used in eee linkmode
In the Linux kernel, the following vulnerability has been resolved:
ixgbe: fix incorrect map used in eee linkmode
incorrectly used ixgbe_lp_map in loops intended to populate the
supported and advertised EEE linkmode bitmaps based on ixgbe_ls_map.
This results in incorrect bit setting and potential out-of-bounds
access, since ixgbe_lp_map and ixgbe_ls_map have different sizes
and purposes.
ixgbe_lp_map[i] -> ixgbe_ls_map[i]
Use ixgbe_ls_map for supported and advertised linkmodes, and keep
ixgbe_lp_map usage only for link partner (lp_advertised) mapping.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel driver flaw in ixgbe EEE linkmode handling. The code used the wrong mapping table, which can cause incorrect bit setting and possible out-of-bounds memory access. The published score is high because local, low-privileged access may affect confidentiality and availability.
Executive priority
Treat as a high-priority kernel maintenance item for Linux infrastructure using ixgbe. It is not described as remotely exploitable or actively exploited in the provided sources, but kernel memory safety issues with high confidentiality and availability impact should not wait for routine quarterly patching.
Technical view
In ixgbe, supported and advertised EEE linkmode bitmaps were populated using ixgbe_lp_map instead of ixgbe_ls_map. The maps have different sizes and purposes, creating potential CWE-125 out-of-bounds access. The fix changes those loops to use ixgbe_ls_map and keeps ixgbe_lp_map for link partner advertised mapping.
Likely exposure
Exposure is most relevant to Linux systems running affected kernel versions where the ixgbe driver and EEE linkmode code are present. The CVSS vector is local, low complexity, low privileges, no user interaction, with high confidentiality and availability impact.
Exploitation context
The provided bundle does not show KEV listing or active exploitation. Based on CVSS, exploitation is local and requires low privileges. Evidence is insufficient to claim remote exploitation, public weaponization, or broad exploitation in the wild.
Researcher notes
The key condition is the wrong map used for supported and advertised EEE linkmode bitmaps. Review affected kernel trees around the three stable commits and validate whether deployed kernels include the ixgbe_ls_map correction. The source evidence does not provide crash traces, proof of concept, or exploitability details.
Mitigation direction
Update to a vendor-supported kernel containing the referenced stable fixes.
Prioritize hosts using ixgbe-backed network interfaces.
Track distribution advisories mapping this CVE to fixed kernel packages.
Reboot into the fixed kernel after applying updates.
If updates are delayed, follow vendor guidance for temporary risk reduction.
Validation and detection
Inventory Linux kernel versions on potentially affected hosts.
Identify systems where the ixgbe driver is loaded or required.
Confirm the running kernel includes one of the referenced stable fixes.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-125: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-125 · source CWE mapping
Out-of-bounds Read
Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.