Skip to main content

Boteraser | Website and Server Security Solutions

🛡️ CVE-2024-50146 — kernel

🟡 CVSS 5.5 — Medium ✅ No Known Exploit NVD
5.5
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

net/mlx5e: Don't call cleanup on profile rollback failure

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

net/mlx5e: Don't call cleanup on profile rollback failure

When profile rollback fails in mlx5e_netdev_change_profile, the netdev

profile var is left set to NULL. Avoid a crash when unloading the driver

by not calling profile->cleanup in such a case.

This was encountered while testing, with the original trigger that

the wq rescuer thread creation got interrupted (presumably due to

Ctrl+C-ing modprobe), which gets converted to ENOMEM (-12) by

mlx5e_priv_init, the profile rollback also fails for the same reason

(signal still active) so the profile is left as NULL, leading to a crash

later in _mlx5e_remove.

[ 732.473932] mlx5_core 0000:08:00.1: E-Switch: Unload vfs: mode(OFFLOADS), nvfs(2), necvfs(0), active vports(2)

[ 734.525513] workqueue: Failed to create a rescuer kthread for wq "mlx5e": -EINTR

[ 734.557372] mlx5_core 0000:08:00.1: mlx5e_netdev_init_profile:6235:(pid 6086): mlx5e_priv_init failed, err=-12

[ 734.559187] mlx5_core 0000:08:00.1 eth3: mlx5e_netdev_change_profile: new profile init failed, -12

[ 734.560153] workqueue: Failed to create a rescuer kthread for wq "mlx5e": -EINTR

[ 734.589378] mlx5_core 0000:08:00.1: mlx5e_netdev_init_profile:6235:(pid 6086): mlx5e_priv_init failed, err=-12

[ 734.591136] mlx5_core 0000:08:00.1 eth3: mlx5e_netdev_change_profile: failed to rollback to orig profile, -12

[ 745.537492] BUG: kernel NULL pointer dereference, address: 0000000000000008

[ 745.538222] #PF: supervisor read access in kernel mode

<snipped>

[ 745.551290] Call Trace:

[ 745.551590] <TASK>

[ 745.551866] ? __die+0x20/0x60

[ 745.552218] ? page_fault_oops+0x150/0x400

[ 745.555307] ? exc_page_fault+0x79/0x240

[ 745.555729] ? asm_exc_page_fault+0x22/0x30

[ 745.556166] ? mlx5e_remove+0x6b/0xb0 [mlx5_core]

[ 745.556698] auxiliary_bus_remove+0x18/0x30

[ 745.557134] device_release_driver_internal+0x1df/0x240

[ 745.557654] bus_remove_device+0xd7/0x140

[ 745.558075] device_del+0x15b/0x3c0

[ 745.558456] mlx5_rescan_drivers_locked.part.0+0xb1/0x2f0 [mlx5_core]

[ 745.559112] mlx5_unregister_device+0x34/0x50 [mlx5_core]

[ 745.559686] mlx5_uninit_one+0x46/0xf0 [mlx5_core]

[ 745.560203] remove_one+0x4e/0xd0 [mlx5_core]

[ 745.560694] pci_device_remove+0x39/0xa0

[ 745.561112] device_release_driver_internal+0x1df/0x240

[ 745.561631] driver_detach+0x47/0x90

[ 745.562022] bus_remove_driver+0x84/0x100

[ 745.562444] pci_unregister_driver+0x3b/0x90

[ 745.562890] mlx5_cleanup+0xc/0x1b [mlx5_core]

[ 745.563415] __x64_sys_delete_module+0x14d/0x2f0

[ 745.563886] ? kmem_cache_free+0x1b0/0x460

[ 745.564313] ? lockdep_hardirqs_on_prepare+0xe2/0x190

[ 745.564825] do_syscall_64+0x6d/0x140

[ 745.565223] entry_SYSCALL_64_after_hwframe+0x4b/0x53

[ 745.565725] RIP: 0033:0x7f1579b1288b

How this vulnerability can be exploited

This issue can be reached with local access to the system, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity none, availability high.

CVSS metrics in full

The score comes from this vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

  • Attack vector: Local — a local account, shell or session on the host is needed.
  • Attack complexity: Low — the attack works reliably, with no preparation.
  • Privileges required: Low — an ordinary user account is enough.
  • User interaction: None — nobody has to be tricked into anything.
  • Scope: Unchanged — the damage stays inside the vulnerable component.
  • Confidentiality impact: None.
  • Integrity impact: None.
  • Availability impact: High — total loss, or loss the attacker controls.

Affected software

CVE-2024-50146 is recorded against 2 packages.

  • kernel (from 6.7.0 up to 6.11.6)
  • linux-kernel

Timeline and source

Published on 7 November 2024 and last revised on 12 August 2026. No public exploit is currently recorded for this entry. A vendor advisory or fix has been published. Record sourced from NVD.

References

git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
lists.debian.org (Web)
github.com (Advisory)
nvd.nist.gov (Advisory)
git.kernel.org (Package)

Other advisories for this package

kernel has other advisories on record. If you are patching this one, these are worth checking on the same host:

CVE-2024-50146 on other distributions

Each distribution ships its own build and its own fixed version. Pick the one you run:

Details

Severity Medium
CVSS Score 5.5
CVSS Vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CWE N/A
Public Exploit ✅ No
Source NVD
Published 2024-11-07
Updated 2026-08-20
Modified 2026-08-12

Affected Packages

Software From version Fixed in
kernel 6.7.0 6.11.6
linux-kernel — —

Similar Threats

Vulnerability Monitoring

Track new vulnerabilities in kernel

CVE-2024-50146 is rated CVSS 5.5 Medium. BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.

Set Up Free Alerts →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesCVECVE 2024
✓