CVE-2024-42112: net: txgbe: free isb resources at the right time
In the Linux kernel, the following vulnerability has been resolved:
net: txgbe: free isb resources at the right time
When using MSI/INTx interrupt, the shared interrupts are still being
handled in the device remove routine, before free IRQs. So isb memory
is still read after it is freed. Thus move wx_free_isb_resources()
from txgbe_close() to txgbe_remove(). And fix the improper isb free
action in txgbe_open() error handling path.
Security readout for executives and security teams
Plain-English summary
A Linux network driver can access memory after freeing it while a txgbe device is being removed under MSI or legacy INTx interrupts. This may crash the host or corrupt kernel memory. The supplied CVSS rates potential confidentiality, integrity, and availability impacts as high, but the sources do not demonstrate practical privilege escalation or data theft.
Executive priority
Treat as a high-priority kernel maintenance issue for affected txgbe hosts, especially infrastructure where a crash would disrupt critical services. It is not supported as an internet-wide emergency: exploitation requires local access, affected driver conditions, and device lifecycle activity. Patch during the next expedited maintenance window after confirming vendor applicability.
Technical view
CVE-2024-42112 is a use-after-free condition in the Linux txgbe network driver. Shared interrupts can continue reading ISB memory during device removal before IRQs are released. The correction delays ISB resource cleanup until txgbe_remove() and repairs cleanup in the txgbe_open() error path. The supplied CVSS 3.1 score is 7.8 with local, low-privilege access required.
Likely exposure
Exposure is limited to systems running an affected Linux kernel with the txgbe driver and relevant network hardware, particularly where MSI or INTx interrupts and device removal occur. The bundle identifies 6.9, 6.9.9, and 6.10 as affected, but its version data includes an unexplained โ0โ; confirm exact distribution status with the kernel vendor.
Exploitation context
The supplied vector requires local access and low privileges, with no user interaction. No CISA KEV listing or cited evidence of active exploitation is provided. The sources establish a kernel memory-lifetime flaw, but do not establish a reliable exploitation method, observed attacks, or whether exploitation beyond denial of service is practical.
Researcher notes
The vulnerable lifetime ordering is specific: ISB storage was released while shared interrupt handlers could still reference it before IRQ teardown. The fixes relocate cleanup from close to remove and correct open-error cleanup. No CWE is supplied. Exact affected-release boundaries are not fully clear from the flattened version list, so commit-level or distribution-advisory verification is preferable.
Mitigation direction
Upgrade to a vendor-supported kernel containing the referenced stable fix.
Confirm the distribution's advisory maps its kernel build to the fix commits.
Prioritize systems actively using the txgbe driver and affected network hardware.
Where upgrades are delayed, consult vendor guidance for supported risk-reduction options.
Validation and detection
Record the running kernel version and distribution build on potentially affected hosts.
Check whether the txgbe driver is present and actively bound to network hardware.
Verify the installed kernel includes either applicable referenced stable fix commit.
Review kernel logs for crashes or memory faults associated with txgbe device removal.
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-42112 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.