CVE-2025-39922
NoneCVSS
—
EPSS
0.2%
Published
Oct 1, 2025
CISA due date
—
Cloudanix analysis
A driver bug in certain Intel network cards could let attackers on the same machine interfere with how the network connection is set up, and updating the system software fixes it.
- Exploitation
- Local Privilege
- Attacker needs
- Low Privilege
- Complexity
- Theoretical
- Impact
- Other
- Component
- OS kernel
- Class
- Misconfiguration
- Remediation
- Patch
- Effort
- Medium
- Patch risk
- Low
What it actually does
The ixgbe driver applies an incorrect mapping table when configuring Energy Efficient Ethernet (EEE) link modes, causing the driver to select or advertise the wrong link parameters during negotiation.
Why it matters to the business
Systems using affected Intel network adapters may experience unexpected link behavior, reduced power efficiency, or intermittent connectivity on 10 GbE interfaces, increasing operational risk for containerized or cloud workloads until the kernel is updated.
How an attack unfolds
An attacker with local access on a system using the vulnerable ixgbe driver manipulates EEE settings or link negotiation to trigger incorrect map usage; combined with other kernel flaws, this can be chained by groups such as VMSCAPE for privilege escalation on container-optimized Linux environments.
How to fix it
Update the Linux kernel to the commit 682105ab63826fb7ca7c112b42b478d156fbb19f or later stable releases that contain the corrected EEE linkmode map for ixgbe.
How to confirm the fix worked
Verify the running kernel contains commit 682105ab63826fb7ca7c112b42b478d156fbb19f; confirm via git log or kernel build info that the ixgbe EEE map correction is present and test link negotiation on affected hardware.
Typical attack path
- Obtain local or container access on a host using ixgbe-based NICs
- Trigger or observe EEE link-mode configuration via ethtool or driver init
- Exploit incorrect map to influence link state or adjacent kernel structures
- Escalate privileges or disrupt networking to achieve persistence or impact
How to detect it
Review kernel logs and audit records for unexpected ixgbe link-mode changes or EEE configuration events around the time of suspected activity; correlate with process execution on container hosts.
What your security team should do
- Apply the referenced kernel fix immediately on all systems using ixgbe NICs
- Prioritize patching hosts in container or cloud environments given VMSCAPE activity
- Monitor for new kernel releases and rebuild custom images with the corrected driver
- Review network interface configurations post-update to ensure EEE settings behave as expected
The record
ixgbe: fix incorrect map used in eee linkmode
Affected packages
| Ecosystem | Package | Introduced | Fixed |
|---|---|---|---|
| Linux | Kernel | 6.9.0 | 6.12.46 |
| SUSE:Linux Enterprise Live Patching 15 SP7 | kernel-livepatch-SLE15-SP7-RT_Update_5 | 0 | 1-150700.1.3.1 |
| SUSE:Real Time Module 15 SP7 | kernel-rt | 0 | 6.4.0-150700.7.19.1 |
| SUSE:Real Time Module 15 SP7 | kernel-source-rt | 0 | 6.4.0-150700.7.19.1 |
| SUSE:Real Time Module 15 SP7 | kernel-syms-rt | 0 | 6.4.0-150700.7.19.1 |
| openSUSE:Leap 16.0 | dtb-aarch64 | 0 | 6.12.0-160000.6.1 |
| openSUSE:Leap 16.0 | kernel-64kb | 0 | 6.12.0-160000.6.1 |
| openSUSE:Leap 16.0 | kernel-default | 0 | 6.12.0-160000.6.1 |
| openSUSE:Leap 16.0 | kernel-default-base | 0 | 6.12.0-160000.6.1.160000.2.4 |
| openSUSE:Leap 16.0 | kernel-docs | 0 | 6.12.0-160000.6.1 |
| openSUSE:Leap 16.0 | kernel-kvmsmall | 0 | 6.12.0-160000.6.1 |
| openSUSE:Leap 16.0 | kernel-obs-build | 0 | 6.12.0-160000.6.1 |
| openSUSE:Leap 16.0 | kernel-obs-qa | 0 | 6.12.0-160000.6.1 |
| openSUSE:Leap 16.0 | kernel-rt | 0 | 6.12.0-160000.6.1 |
| openSUSE:Leap 16.0 | kernel-source | 0 | 6.12.0-160000.6.1 |
| openSUSE:Leap 16.0 | kernel-syms | 0 | 6.12.0-160000.6.1 |
| openSUSE:Leap 16.0 | kernel-zfcpdump | 0 | 6.12.0-160000.6.1 |
Related vulnerabilities
- CVE-2026-23226 In the Linux kernel, the following vulnerability has been resolved: ksmbd: add chann_lock… Also affects Kernel
- CVE-2026-23225 In the Linux kernel, the following vulnerability has been resolved: sched/mmcid: Don't… Also affects Kernel
- CVE-2026-23230 In the Linux kernel, the following vulnerability has been resolved: smb: client: split… Also affects Kernel
- CVE-2026-23224 In the Linux kernel, the following vulnerability has been resolved: erofs: fix UAF issue… Also affects Kernel
- CVE-2026-23227 In the Linux kernel, the following vulnerability has been resolved: drm/exynos: vidi: use… Also affects Kernel
- CVE-2026-23223 In the Linux kernel, the following vulnerability has been resolved: xfs: fix UAF in… Also affects Kernel
- CVE-2026-23228 In the Linux kernel, the following vulnerability has been resolved: smb: server: fix leak… Also affects Kernel
- CVE-2026-23229 In the Linux kernel, the following vulnerability has been resolved: crypto: virtio - Add… Also affects Kernel