CVE-2024-50146

Kernel crash via NULL profile cleanup

Published Nov 7, 2024 · Updated May 11, 2026

NULL pointer dereference in the mlx5e driver in Linux 5.12 through 6.11.5 and 6.12-rc1 through 6.12-rc3 allows local users to crash the kernel. After mlx5e_netdev_change_profile fails to initialize a new profile and restore the original, it leaves the profile pointer NULL; _mlx5e_remove later dereferences profile->cleanup during driver unloading. Reachability requires local access able to interrupt workqueue rescuer creation during a profile change and later unload the mlx5e driver; the bounded consequence is a kernel crash.

CVSS severity5.5
Medium
EPSS probability0.23%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

NULL pointer dereference in the mlx5e driver in Linux 5.12 through 6.11.5 and 6.12-rc1 through 6.12-rc3 allows local users to crash the kernel. After mlx5e_netdev_change_profile fails to initialize a new profile and restore the original, it leaves the profile pointer NULL; _mlx5e_remove later dereferences profile->cleanup during driver unloading. Reachability requires local access able to interrupt workqueue rescuer creation during a profile change and later unload the mlx5e driver; the bounded consequence is a kernel crash.

The record

CVE
CVE-2024-50146
Published
Nov 7, 2024
Updated
May 11, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
T1499
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Nov 7, 2024CVE publishedPublication date reported by the CVE source.
  2. May 11, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=3ef14e463f6ed0218710f56b97e1a7d0448784d2 <3955b77494c3c7d14873b1db67e7e00c46a714db
  2. Affected versionversion=3ef14e463f6ed0218710f56b97e1a7d0448784d2 <4dbc1d1a9f39c3711ad2a40addca04d07d9ab5d0
  3. Affected versionversion=3ef14e463f6ed0218710f56b97e1a7d0448784d2 <d6fe973c8873c998734a050f366b28facc03d32a
  4. Affected versionversion=3ef14e463f6ed0218710f56b97e1a7d0448784d2 <db84cb4c8c565e6d4de84b23c2818b63991adfdd
  5. Affected versionversion=5.12

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linuxversion=3ef14e463f6ed0218710f56b97e1a7d0448784d2 <3955b77494c3c7d14873b1db67e7e00c46a714db; version=3ef14e463f6ed0218710f56b97e1a7d0448784d2 <4dbc1d1a9f39c3711ad2a40addca04d07d9ab5d0; version=3ef14e463f6ed0218710f56b97e1a7d0448784d2 <d6fe973c8873c998734a050f366b28facc03d32a; version=3ef14e463f6ed0218710f56b97e1a7d0448784d2 <db84cb4c8c565e6d4de84b23c2818b63991adfdd; version=5.12

Published CVSS scores

5.5Amazon LinuxCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

T1499Endpoint Denial of Service

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo