Security readout for executives and security teams
Plain-English summary
A Linux NTB networking driver can invoke packet receive handling from the wrong execution context when idxd/DSA DMA uses threaded interrupts. This can trigger a kernel BUG and disrupt availability. Exposure appears concentrated in specialized servers using NTB networking and this DMA path, rather than typical Linux systems.
Executive priority
Treat as high priority on systems using NTB networking with idxd/DSA DMA because the recorded impact is loss of availability. For other Linux systems, first confirm that the specialized modules, hardware, and data path are present before assigning emergency remediation resources.
Technical view
ntb_netdev_rx_handler() called __netif_rx(), which requires interrupt context. When ntb_transport completion arrives through an idxd DMA threaded interrupt, execution is in preemptible normal context, causing invalid smp_processor_id() use and an availability-impacting BUG. Stable fixes replace __netif_rx() with netif_rx(), which supports normal context.
Likely exposure
Likely limited to Linux hosts using ntb_netdev over ntb_transport where receive completion is delivered by a DMA engine with threaded IRQ handling, specifically demonstrated with Intel idxd/DSA. The bundle does not establish exposure for ordinary Ethernet hosts. Kernel versions and distributor backports must be checked individually.
Exploitation context
The supplied record has KEV=false and provides no evidence of exploitation in the wild. Its CVSS vector rates network reachability, low complexity, and no required privileges or interaction. However, the described failure depends on a specialized NTB/idxd path, and the sources do not establish practical remote attackability.
Researcher notes
The source describes an execution-context violation, not memory corruption: __netif_rx() was reached from preemptible threaded-interrupt context, producing smp_processor_id() diagnostics. The fix restores netif_rx(). No CWE is assigned, and the bundle does not prove a reliable remote crash primitive or specify every triggering traffic condition.
Mitigation direction
- Update to a vendor-supported kernel containing the applicable upstream stable fix, then reboot if required.
- Verify the vendor package contains the fix; distribution backports may not match upstream version numbers.
- Follow distribution or hardware-vendor guidance for temporary controls when patching cannot be immediate.
Validation and detection
- Inventory hosts for loaded or configured ntb_netdev, ntb_transport, and idxd components.
- Check the running kernel package for the applicable stable commit or documented vendor backport.
- Review kernel logs for the reported preemptible smp_processor_id() BUG signature.
- After remediation, exercise the authorized NTB receive path and confirm the warning does not recur.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-2024-42110 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6LinuxVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/4b3b6c7efee69f077b86ef7f088fb96768e46e1fCVE reference, Linux
- https://git.kernel.org/stable/c/e3af5b14e7632bf12058533d69055393e2d126c9CVE reference, Linux
- https://git.kernel.org/stable/c/858ae09f03677a4ab907a15516893bc2cc79d4c3CVE reference, Linux
- https://git.kernel.org/stable/c/e15a5d821e5192a3769d846079bc9aa380139bafCVE reference, Linux
- https://lists.debian.org/debian-lts-announce/2025/01/msg00001.htmlCVE reference, CVE
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.