CVE-2024-42110: net: ntb_netdev: Move ntb_netdev_rx_handler() to call netif_rx() from __netif_rx()

Published Jul 30, 2024
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

net: ntbnetdev: Move ntbnetdevrxhandler() to call netifrx() from netifrx()

The following is emitted when using idxd (DSA) dmanegine as the data mover for ntbtransport that ntbnetdev uses.

[74412.546922] BUG: using smpprocessorid() in preemptible [00000000] code: irq/52-idxd-por/14526 [74412.556784] caller is netifrxinternal+0x42/0x130 [74412.562282] CPU: 6 PID: 14526 Comm: irq/52-idxd-por Not tainted 6.9.5 #5 [74412.569870] Hardware name: Intel Corporation ArcherCity/ArcherCity, BIOS EGSDCRB1.E9I.1752.P05.2402080856 02/08/2024 [74412.581699] Call Trace: [74412.584514] <TASK> [74412.586933] dumpstacklvl+0x55/0x70 [74412.591129] checkpreemptiondisabled+0xc8/0xf0 [74412.596374] netifrxinternal+0x42/0x130 [74412.600957] netifrx+0x20/0xd0 [74412.604743] ntbnetdevrxhandler+0x66/0x150 [ntbnetdev] [74412.610985] ntbcompleterxc+0xed/0x140 [ntbtransport] [74412.617010] ntbrxcopycallback+0x53/0x80 [ntbtransport] [74412.623332] idxddmacompletetxd+0xe3/0x160 [idxd] [74412.628963] idxdwqthread+0x1a6/0x2b0 [idxd] [74412.634046] irqthreadfn+0x21/0x60 [74412.638134] ? irqthread+0xa8/0x290 [74412.642218] irqthread+0x1a0/0x290 [74412.646212] ? pfxirqthreadfn+0x10/0x10 [74412.651071] ? pfxirqthreaddtor+0x10/0x10 [74412.656117] ? pfxirqthread+0x10/0x10 [74412.660686] kthread+0x100/0x130 [74412.664384] ? pfxkthread+0x10/0x10 [74412.668639] retfromfork+0x31/0x50 [74412.672716] ? pfxkthread+0x10/0x10 [74412.676978] retfromforkasm+0x1a/0x30 [74412.681457] </TASK>

The cause is due to the idxd driver interrupt completion handler uses threaded interrupt and the threaded handler is not hard or soft interrupt context. However netifrx() can only be called from interrupt context. Change the call to netifrx() in order to allow completion via normal context for dmaengine drivers that utilize threaded irq handling.

While the following commit changed from netifrx() to netifrx(), baebdf48c360 ("net: dev: Makes sure netifrx() can be invoked in any context."), the change should've been a noop instead. However, the code precedes this fix should've been using netifrxni() or netifrxanycontext().

Affected Software

15 affected componentsFixes available
redhat/kernel<6.1.98
6.1.98
redhat/kernel<6.6.39
6.6.39
redhat/kernel<6.9.9
6.9.9
redhat/kernel<6.10
6.10
debian/linux<=5.10.223-1, <=5.10.234-1
6.1.129-16.1.135-16.12.25-16.12.27-1
debian/linux-6.1
6.1.129-1~deb11u1
Linux Linux kernel>=3.9<6.1.98
Linux Linux kernel>=6.2<6.6.39
Linux Linux kernel>=6.7<6.9.9
Linux Linux kernel=6.10-rc1
Linux Linux kernel=6.10-rc2
Linux Linux kernel=6.10-rc3
Linux Linux kernel=6.10-rc4
Linux Linux kernel=6.10-rc5
Linux Linux kernel=6.10-rc6

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade redhat/kernel to a version that resolves this vulnerability.

    Fixed in 6.1.98
  2. Upgrade

    Upgrade redhat/kernel to a version that resolves this vulnerability.

    Fixed in 6.6.39
  3. Upgrade

    Upgrade redhat/kernel to a version that resolves this vulnerability.

    Fixed in 6.9.9
  4. Upgrade

    Upgrade redhat/kernel to a version that resolves this vulnerability.

    Fixed in 6.10
  5. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.25-1Fixed in 6.12.27-1
  6. Upgrade

    Upgrade debian/linux-6.1 to a version that resolves this vulnerability.

    Fixed in 6.1.129-1~deb11u1
  7. Compensating control

    For dmaengine drivers that use threaded IRQ handling, ensure receive completion uses the netif_rx() variant intended for any/threaded context (e.g., netif_rx_ni() or netif_rx_any_context()), rather than __netif_rx(), since __netif_rx() can only be called from interrupt context.

Event History

Jul 30, 2024
CVE Published
via MITRE·07:46 AM
Data Sourced
via MITRE·07:46 AM
DescriptionSeverity
Data Sourced
via NVD·08:15 AM
Description
Data Sourced
via NVD·08:15 AM
RemedySeverityAffected Software
Apr 27, 2025
Data Sourced
via Ubuntu·12:33 AM
RemedyDescriptionSeverityAffected Software
Oct 10, 2025
Data Sourced
via Microsoft·02:35 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

What is the severity of CVE-2024-42110?

The severity of CVE-2024-42110 has not been publicly rated yet, but it affects core functionalities in the Linux kernel.

2

How do I fix CVE-2024-42110?

To resolve CVE-2024-42110, update your Linux kernel to the recommended versions specified by your distribution.

3

Which versions of the Linux kernel are affected by CVE-2024-42110?

CVE-2024-42110 affects multiple versions of the Linux kernel, specifically those prior to 6.1.98, 6.6.39, 6.9.9, and 6.10.

4

What components are primarily impacted by CVE-2024-42110?

CVE-2024-42110 primarily impacts the ntb_netdev subsystem within the Linux kernel.

5

Is there a specific patch for CVE-2024-42110?

Yes, the fix for CVE-2024-42110 is included in the latest kernel updates from both Red Hat and Debian.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203