LiveActive security incident?Get immediate response
CVE Record

CVE-2024-42150: net: txgbe: remove separate irq request for MSI and INTx

In the Linux kernel, the following vulnerability has been resolved: net: txgbe: remove separate irq request for MSI and INTx When using MSI or INTx interrupts, request_irq() for pdev->irq will conflict with request_threaded_irq() for txgbe->misc.irq, to cause system crash. So remove txgbe_request_irq() for MSI/INTx case, and rename txgbe_request_msix_irqs() since it only request for queue irqs. Add wx->misc_irq_domain to determine whether the driver creates an IRQ domain and threaded request the IRQs.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2024-42150 is a Linux kernel flaw in the txgbe network driver. Under MSI or INTx interrupt modes, conflicting IRQ requests can cause a system crash. The public record does not provide CVSS, exploitability details, or evidence of active exploitation.

Executive priority

Treat as a reliability and availability issue for affected Linux network hosts. Prioritize internet-facing, production, and high-availability systems using txgbe hardware, but do not escalate as actively exploited based on the provided sources.

Technical view

The txgbe driver could call request_irq() for pdev->irq while also using request_threaded_irq() for txgbe->misc.irq, creating an IRQ conflict in MSI or INTx modes. The kernel fix removes the separate MSI/INTx IRQ request path and adds misc_irq_domain state tracking.

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions with the txgbe network driver and MSI or INTx interrupt use. The source bundle lists Linux 6.9 through 6.9.9 and 6.10 as affected, but gives incomplete operational detail.

Exploitation context

No source in the bundle states active exploitation, public exploit availability, or remote attack requirements. The described impact is a system crash from driver IRQ handling conflict, not data theft or privilege escalation.

Researcher notes

Evidence is sparse: no CVSS, CWE, exploit prerequisites, or attacker model are provided. The strongest technical signal is the upstream stable fix describing an IRQ request conflict that can crash the system under MSI or INTx interrupt handling.

Mitigation direction

  • Apply Linux stable fixes referenced by the kernel commits.
  • Prioritize systems using txgbe-supported network adapters.
  • Check distribution advisories for backported kernel packages.
  • Avoid direct wrangler-style assumptions; follow vendor kernel guidance.
  • Schedule reboot windows where kernel updates require restart.

Validation and detection

  • Inventory kernels against listed affected and fixed versions.
  • Identify hosts loading or depending on the txgbe driver.
  • Review crash logs for txgbe or IRQ conflict messages.
  • Confirm patched kernels include the referenced stable commits.
  • Track vendor advisories for distribution-specific status.
Prepared
Confidence
medium
Sources
4

Public sources used

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-42150 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

0CVSS vectors
3Timeline events
2ADP providers
3Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxaefd013624a10f39b0bfaee8432a235128705380, aefd013624a10f39b0bfaee8432a235128705380, ffe8a87463c8bb885c42ed54540d06ed041e76dc, 6.8.12unaffected
LinuxLinux6.9, 0, 6.9.9, 6.10affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.