CVE-2024-50157: RDMA/bnxt_re: Avoid CPU lockups due fifo occupancy check loop

Published Nov 7, 2024
·
Updated

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

RDMA/bnxtre: Avoid CPU lockups due fifo occupancy check loop

Driver waits indefinitely for the fifo occupancy to go below a threshold as soon as the pacing interrupt is received. This can cause soft lockup on one of the processors, if the rate of DB is very high.

Add a loop count for FPGA and exit the waitforfifooccupancybelowth if the loop is taking more time. Pacing will be continuing until the occupancy is below the threshold. This is ensured by the checks in bnxtrepacingtimerexp and further scheduling the work for pacing based on the fifo occupancy.

Affected Software

7 affected componentsFixes available
Linux Linux kernel>=6.6<6.11.6
Linux Linux kernel=6.12-rc1
Linux Linux kernel=6.12-rc2
Linux Linux kernel=6.12-rc3
debian/linux
5.10.223-15.10.234-16.1.129-16.1.135-16.12.22-16.12.25-1
Microsoft azl3 kernel 6.6.76.1-1<6.6.76.1-1
6.6.76.1-1
Microsoft azl3 kernel 6.6.92.2-1<6.6.76.1-1
6.6.76.1-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

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

    Fixed in 5.10.223-1Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.22-1Fixed in 6.12.25-1
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.6.76.1-1
  3. Compensating control

    In bnxt_re_pacing_timer_exp (RDMA/bnxt_re), add a loop count to the fifo-occupancy polling and exit __wait_for_fifo_occupancy_below_th if the loop takes more time, since the driver otherwise waits indefinitely for fifo occupancy to drop below the threshold after the pacing interrupt.

Event History

Nov 7, 2024
CVE Published
via MITRE·09:31 AM
Data Sourced
via MITRE·09:31 AM
Description
Apr 29, 2025
Data Sourced
via Ubuntu·01:03 AM
RemedyDescriptionSeverityAffected Software
Sep 4, 2025
Data Sourced
via Microsoft·04:26 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·04:26 AM
Affected Software
Updated
via Microsoft·04:26 AM
SeverityAffected Software
Updated
via Microsoft·04:26 AM
DescriptionSeverity

Frequently Asked Questions

1

What is the severity of CVE-2024-50157?

CVE-2024-50157 is considered a medium severity vulnerability due to the risk of causing soft lockups in systems using affected kernel versions.

2

How do I fix CVE-2024-50157?

To mitigate CVE-2024-50157, users should update their Linux kernel to version 6.12-rc4 or later, where the vulnerability has been patched.

3

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

CVE-2024-50157 affects Linux kernel versions from 6.6 to 6.11.6 and includes specific 6.12 release candidates up to rc3.

4

What are the potential impacts of CVE-2024-50157?

The potential impact of CVE-2024-50157 includes system instability and performance issues, specifically soft lockups during FIFO occupancy checks.

5

Is CVE-2024-50157 specific to any Linux distributions?

CVE-2024-50157 is related to the Linux kernel itself and could potentially affect any Linux distribution utilizing the vulnerable kernel versions.

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