CVE-2024-47747: net: seeq: Fix use after free vulnerability in ether3 Driver Due to Race Condition
In the Linux kernel, the following vulnerability has been resolved:
net: seeq: Fix use after free vulnerability in ether3 Driver Due to Race Condition
In the ether3_probe function, a timer is initialized with a callback
function ether3_ledoff, bound to &prev(dev)->timer. Once the timer is
started, there is a risk of a race condition if the module or device
is removed, triggering the ether3_remove function to perform cleanup.
The sequence of operations that may lead to a UAF bug is as follows:
CPU0 CPU1
| ether3_ledoff
ether3_remove |
free_netdev(dev); |
put_devic |
kfree(dev); |
| ether3_outw(priv(dev)->regs.config2 |= CFG2_CTRLO, REG_CONFIG2);
| // use dev
Fix it by ensuring that the timer is canceled before proceeding with
the cleanup in ether3_remove.
Security readout for executives and security teams
Plain-English summary
A race in Linux's ether3 network driver can let a timer use a network-device object after removal has freed it. This kernel memory-safety failure may cause crashes or corruption and carries high confidentiality, integrity, and availability impact. Exposure appears specialized because the affected driver must be present and involved in device or module removal.
Executive priority
Treat this as high priority for systems using ether3, especially multi-user or locally accessible appliances. For fleets without this driver or associated hardware, urgency is lower, but inventory evidence is required. There is no source-backed indication of active exploitation.
Technical view
In ether3_probe, a timer callback is bound to device-private state. ether3_remove can free the network device while ether3_ledoff is executing on another CPU, allowing the callback to dereference freed memory. The fix cancels the timer before cleanup. The supplied CVSS v3.1 score is 7.8: local access, low complexity, low privileges, and no user interaction.
Likely exposure
Likely exposure is concentrated in Linux systems whose kernels contain and use the ether3 driver. The vulnerable race occurs during device or module removal while the timer remains active. The supplied affected-version list contains ambiguous boundary-style entries, so kernel version strings alone are insufficient for determining exposure.
Exploitation context
The bundle marks this CVE as absent from KEV and provides no evidence of active exploitation or a public exploit. Exploitation is scored local with low privileges; reliable triggering and real-world prevalence are not established by the supplied sources.
Researcher notes
Focus on the teardown and timer race: ether3_remove frees the device while ether3_ledoff may dereference its private state. The correction cancels the timer before cleanup. The flattened affected-version entries do not establish exact vulnerable package ranges; use distribution backport records and stable-commit ancestry for confirmation.
Mitigation direction
Upgrade to a vendor-supported kernel release that incorporates the applicable upstream stable fix.
Follow Linux distribution or equipment-vendor advisories for package-specific remediation and reboot requirements.
Confirm the corrected kernel is running after completing the vendor-prescribed update process.
Validation and detection
Determine whether the running kernel contains the ether3 driver and whether associated hardware or modules are used.
Map distribution kernel packages to upstream stable fixes; do not rely solely on the supplied flattened version list.
Verify the installed kernel contains the applicable fix that cancels the timer before device cleanup.
Review relevant kernel logs for faults associated with ether3 device removal or module lifecycle events.
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.
cve · low confidence lookup
CVE-2024-47747 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.