Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-98710 Overview
CVE-2026-98710 is a memory leak vulnerability in the Linux kernel's iwlegacy 3945 wireless driver. The driver's PCI probe routine il3945_pci_probe() calls il_eeprom_init() to allocate memory for EEPROM data. While the probe failure paths correctly release this allocation using il_eeprom_free(), the remove path il3945_pci_remove() fails to free it after a successful probe. The EEPROM buffer therefore leaks each time the PCI device is removed. The issue was identified through manual code inspection and resolved by freeing the EEPROM data in the remove handler before releasing the mac80211 hardware structure.
Critical Impact
Repeated bind/unbind cycles of the Intel 3945 wireless adapter leak kernel memory, degrading long-running system stability.
Affected Products
- Linux kernel versions containing the iwlegacy 3945 wireless driver
- Systems using Intel PRO/Wireless 3945ABG network adapters
- Distributions shipping unpatched upstream iwl3945 driver code
Discovery Timeline
- 2026-10-18 - CVE-2026-98710 published to NVD
- 2026-10-21 - Last updated in NVD database
Technical Details for CVE-2026-98710
Vulnerability Analysis
The defect resides in the iwlegacy driver that supports the Intel PRO/Wireless 3945ABG chipset. During device initialization, il3945_pci_probe() invokes il_eeprom_init(), which allocates a kernel heap buffer to hold the EEPROM contents read from the hardware. This buffer persists for the lifetime of the device binding and is used by the driver to query hardware capabilities and MAC configuration.
The probe function correctly cleans up allocations when initialization fails, calling il_eeprom_free() on each error path. The remove counterpart il3945_pci_remove() was not updated with the matching free call. Consequently, when the PCI device is unbound through rmmod, hotplug removal, or administrative unbind, the EEPROM buffer is never released.
Each unbind operation leaks a small, fixed-size allocation. On most workloads the impact is negligible, but environments that repeatedly bind and unbind the adapter such as power-management test harnesses, suspend/resume cycles, or driver reload scripts accumulate leaked memory over time.
Root Cause
The root cause is a missing deallocation in the device teardown path, classified as a Memory Leak [CWE-401]. The probe and remove paths were asymmetric: il_eeprom_init() had no corresponding il_eeprom_free() call in il3945_pci_remove(). The upstream fix adds the missing il_eeprom_free() invocation before ieee80211_free_hw() is called, restoring symmetric resource ownership between probe and remove.
Attack Vector
Triggering the leak requires local privilege to load, unload, bind, or unbind the iwl3945 driver, operations normally restricted to root. There is no remote attack surface and no path to code execution, privilege escalation, or information disclosure. The practical consequence is gradual kernel memory consumption that can contribute to resource exhaustion on long-running systems that repeatedly cycle the device.
The vulnerability manifests only in the driver teardown flow. See the upstream commits referenced below for the exact code change.
Detection Methods for CVE-2026-98710
Indicators of Compromise
- Growth in kernel slab allocations attributable to iwl3945 or EEPROM-related objects following repeated driver unload cycles
- kmemleak reports flagging unreferenced allocations originating from il_eeprom_init() in the iwlegacy driver
- Gradual increase in unreclaimable kernel memory on hosts that frequently rebind the 3945 wireless adapter
Detection Strategies
- Enable CONFIG_DEBUG_KMEMLEAK on test kernels and exercise rmmod iwl3945 && modprobe iwl3945 cycles to surface the leaked buffer
- Compare /proc/meminfoSlab and SUnreclaim values across repeated driver bind and unbind operations
- Audit installed kernel versions against the fixed commits published on git.kernel.org to identify unpatched hosts
Monitoring Recommendations
- Track kernel memory growth on long-running laptops and embedded systems that use the Intel 3945 chipset
- Alert on anomalous rates of iwl3945 module load or unload events in system journals
- Include kernel package version inventory in endpoint telemetry to prioritize patching of affected hosts
How to Mitigate CVE-2026-98710
Immediate Actions Required
- Apply the upstream Linux kernel patch that adds il_eeprom_free() to il3945_pci_remove() before releasing the mac80211 hardware structure
- Update to a distribution kernel package that incorporates the stable-tree backport referenced in the kernel.org commits
- Avoid unnecessary bind/unbind or modprobe cycles of the iwl3945 driver on systems that cannot yet be patched
Patch Information
The fix is distributed across the stable kernel trees. Relevant commits include kernel commit 3ebc529726c0, kernel commit 89f9d6186dc7, kernel commit ab7bee2cd55f, kernel commit cd8f8f45d81a, and kernel commit f8ebe286394c. Rebuild and reboot after applying.
Workarounds
- Blacklist the iwl3945 module on systems that do not require the legacy Intel 3945 wireless adapter
- Reboot hosts periodically to reclaim leaked kernel memory until the patched kernel is deployed
- Restrict root-level module loading permissions to limit who can trigger repeated driver teardown cycles
# Verify kernel version and blacklist the vulnerable module if unused
uname -r
echo "blacklist iwl3945" | sudo tee /etc/modprobe.d/blacklist-iwl3945.conf
sudo update-initramfs -u
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

