CVE-2024-38608: net/mlx5e: Fix netif state handling
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.26% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 3d5918477f94e4c2f064567875c475468e264644, 70eca80d98a44f47cd1633d0c20bda8ae546b4d1, 96e3eeccea9b55ca9c6a18a5a59ee3d6f12e0fb3.
Low priority for now. Upgrade to Linux Linux 3d5918477f94e4c2f064567875c475468e264644, 70eca80d98a44f47cd1633d0c20bda8ae546b4d1, 96e3eeccea9b55ca9c6a18a5a59ee3d6f12e0fb3 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Fix netif state handling mlx5e_suspend cleans resources only if netif_device_present() returns true. However, mlx5e_resume changes the state of netif, via mlx5e_nic_enable, only if reg_state == NETREG_REGISTERED. In the below case, the above leads to NULL-ptr Oops[1] and memory leaks: mlx5e_probe _mlx5e_resume mlx5e_attach_netdev mlx5e_nic_enable <-- netdev not reg, not calling netif_device_attach() register_netdev <-- failed for some reason. ERROR_FLOW: _mlx5e_suspend <-- netif_device_present return false, resources aren't freed :( Hence, clean resources in this case as well. [1] BUG: kernel NULL pointer dereference, address: 0000000000000000 PGD 0 P4D 0 Oops: 0010 [#1] SMP CPU: 2 PID: 9345 Comm: test-ovs-ct-gen Not tainted 6.5.0_for_upstream_min_debug_2023_09_05_16_01 #1 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 RIP: 0010:0x0 Code: Unable to access opcode bytes at0xffffffffffffffd6. RSP: 0018:ffff888178aaf758 EFLAGS: 00010246 Call Trace: <TASK> ? __die+0x20/0x60 ? page_fault_oops+0x14c/0x3c0 ? exc_page_fault+0x75/0x140 ? asm_exc_page_fault+0x22/0x30 notifier_call_chain+0x35/0xb0 blocking_notifier_call_chain+0x3d/0x60 mlx5_blocking_notifier_call_chain+0x22/0x30 [mlx5_core] mlx5_core_uplink_netdev_event_replay+0x3e/0x60 [mlx5_core] mlx5_mdev_netdev_track+0x53/0x60 [mlx5_ib] mlx5_ib_roce_init+0xc3/0x340 [mlx5_ib] __mlx5_ib_add+0x34/0xd0 [mlx5_ib] mlx5r_probe+0xe1/0x210 [mlx5_ib] ? auxiliary_match_id+0x6a/0x90 auxiliary_bus_probe+0x38/0x80 ? driver_sysfs_add+0x51/0x80 really_probe+0xc9/0x3e0 ? driver_probe_device+0x90/0x90 __driver_probe_device+0x80/0x160 driver_probe_device+0x1e/0x90 __device_attach_driver+0x7d/0x100 bus_for_each_drv+0x80/0xd0 __device_attach+0xbc/0x1f0 bus_probe_device+0x86/0xa0 device_add+0x637/0x840 __auxiliary_device_add+0x3b/0xa0 add_adev+0xc9/0x140 [mlx5_core] mlx5_rescan_drivers_locked+0x22a/0x310 [mlx5_core] mlx5_register_device+0x53/0xa0 [mlx5_core] mlx5_init_one_devl_locked+0x5c4/0x9c0 [mlx5_core] mlx5_init_one+0x3b/0x60 [mlx5_core] probe_one+0x44c/0x730 [mlx5_core] local_pci_probe+0x3e/0x90 pci_device_probe+0xbf/0x210 ? kernfs_create_link+0x5d/0xa0 ? sysfs_do_create_link_sd+0x60/0xc0 really_probe+0xc9/0x3e0 ? driver_probe_device+0x90/0x90 __driver_probe_device+0x80/0x160 driver_probe_device+0x1e/0x90 __device_attach_driver+0x7d/0x100 bus_for_each_drv+0x80/0xd0 __device_attach+0xbc/0x1f0 pci_bus_add_device+0x54/0x80 pci_iov_add_virtfn+0x2e6/0x320 sriov_enable+0x208/0x420 mlx5_core_sriov_configure+0x9e/0x200 [mlx5_core] sriov_numvfs_store+0xae/0x1a0 kernfs_fop_write_iter+0x10c/0x1a0 vfs_write+0x291/0x3c0 ksys_write+0x5f/0xe0 do_syscall_64+0x3d/0x90 entry_SYSCALL_64_after_hwframe+0x46/0xb0 CR2: 0000000000000000 ---[ end trace 0000000000000000 ]---
- Published
- Jun 19, 2024
- Updated
- Oct 30, 2026
- EPSS
- 0.2% · 17th percentile
- CWE
- CWE-476
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.12affected
- 2c3b5beec46ab0d77c94828eb15170b333ae769a and later · before 96e3eeccea9b55ca9c6a18a5a59ee3d6f12e0fb3affected · git
- 2c3b5beec46ab0d77c94828eb15170b333ae769a and later · before 70eca80d98a44f47cd1633d0c20bda8ae546b4d1affected · git
- 2c3b5beec46ab0d77c94828eb15170b333ae769a and later · before f7e6cfb864a53af71c5cc904f1cc22215d68f5c6affected · git
- 2c3b5beec46ab0d77c94828eb15170b333ae769a and later · before 3d5918477f94e4c2f064567875c475468e264644affected · git
- before 4.12not affected · semver
- 6.1.191 and later · up to and including 6.1.*not affected · semver
- 6.6.160 and later · up to and including 6.6.*not affected · semver
- 6.9.3 and later · up to and including 6.9.*not affected · semver
- 6.10 and laternot affected · original_commit_for_fix
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel4.12 and later · before 6.9.3
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | bpftool | before 4.18.0-553.27.1.el8_10 | 4.18.0-553.27.1.el8_10 |
| AlmaLinux:8 | kernel | before 4.18.0-553.27.1.el8_10 | 4.18.0-553.27.1.el8_10 |
| AlmaLinux:8 | kernel-abi-stablelists | before 4.18.0-553.27.1.el8_10 | 4.18.0-553.27.1.el8_10 |
| AlmaLinux:8 | kernel-core | before 4.18.0-553.27.1.el8_10 | 4.18.0-553.27.1.el8_10 |
| AlmaLinux:8 | kernel-cross-headers | before 4.18.0-553.27.1.el8_10 | 4.18.0-553.27.1.el8_10 |
| AlmaLinux:8 | kernel-debug | before 4.18.0-553.27.1.el8_10 | 4.18.0-553.27.1.el8_10 |
| AlmaLinux:8 | kernel-debug-core | before 4.18.0-553.27.1.el8_10 | 4.18.0-553.27.1.el8_10 |
| AlmaLinux:8 | kernel-debug-devel | before 4.18.0-553.27.1.el8_10 | 4.18.0-553.27.1.el8_10 |
| AlmaLinux:8 | kernel-debug-modules | before 4.18.0-553.27.1.el8_10 | 4.18.0-553.27.1.el8_10 |
| AlmaLinux:8 | kernel-debug-modules-extra | before 4.18.0-553.27.1.el8_10 | 4.18.0-553.27.1.el8_10 |
| AlmaLinux:8 | kernel-devel | before 4.18.0-553.27.1.el8_10 | 4.18.0-553.27.1.el8_10 |
| AlmaLinux:8 | kernel-doc | before 4.18.0-553.27.1.el8_10 | 4.18.0-553.27.1.el8_10 |
| AlmaLinux:8 | kernel-headers | before 4.18.0-553.27.1.el8_10 | 4.18.0-553.27.1.el8_10 |
| AlmaLinux:8 | kernel-modules | before 4.18.0-553.27.1.el8_10 | 4.18.0-553.27.1.el8_10 |
| AlmaLinux:8 | kernel-modules-extra | before 4.18.0-553.27.1.el8_10 | 4.18.0-553.27.1.el8_10 |
| AlmaLinux:8 | kernel-rt | before 4.18.0-553.27.1.rt7.368.el8_10 | 4.18.0-553.27.1.rt7.368.el8_10 |
| AlmaLinux:8 | kernel-rt-core | before 4.18.0-553.27.1.rt7.368.el8_10 | 4.18.0-553.27.1.rt7.368.el8_10 |
| AlmaLinux:8 | kernel-rt-debug | before 4.18.0-553.27.1.rt7.368.el8_10 | 4.18.0-553.27.1.rt7.368.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-core | before 4.18.0-553.27.1.rt7.368.el8_10 | 4.18.0-553.27.1.rt7.368.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-devel | before 4.18.0-553.27.1.rt7.368.el8_10 | 4.18.0-553.27.1.rt7.368.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-modules | before 4.18.0-553.27.1.rt7.368.el8_10 | 4.18.0-553.27.1.rt7.368.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-modules-extra | before 4.18.0-553.27.1.rt7.368.el8_10 | 4.18.0-553.27.1.rt7.368.el8_10 |
| AlmaLinux:8 | kernel-rt-devel | before 4.18.0-553.27.1.rt7.368.el8_10 | 4.18.0-553.27.1.rt7.368.el8_10 |
| AlmaLinux:8 | kernel-rt-modules | before 4.18.0-553.27.1.rt7.368.el8_10 | 4.18.0-553.27.1.rt7.368.el8_10 |
+96
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2024-38598Jun 19, 2024 · md: fix resync softlockup when bitmap size is less than array size22Monitor
- ← EarlierCVE-2024-38599Jun 19, 2024 · jffs2: prevent xattr node from overflowing the eraseblock28Monitor
- Later →CVE-2024-38612Jun 19, 2024 · ipv6: sr: fix invalid unregister error path28Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 3d5918477f94e4c2f064567875c475468e264644 | Vendor (CNA) |
| Linux Linux | 70eca80d98a44f47cd1633d0c20bda8ae546b4d1 | Vendor (CNA) |
| Linux Linux | 96e3eeccea9b55ca9c6a18a5a59ee3d6f12e0fb3 | Vendor (CNA) |
| Linux Linux | f7e6cfb864a53af71c5cc904f1cc22215d68f5c6 | Vendor (CNA) |
| almalinux:bpftool | 4.18.0-553.27.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel | 4.18.0-553.27.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-abi-stablelists | 4.18.0-553.27.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-core | 4.18.0-553.27.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-cross-headers | 4.18.0-553.27.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug | 4.18.0-553.27.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-core | 4.18.0-553.27.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-devel | 4.18.0-553.27.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-modules | 4.18.0-553.27.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-modules-extra | 4.18.0-553.27.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-devel | 4.18.0-553.27.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-doc | 4.18.0-553.27.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| debian:linux | 6.9.7-1 · Debian:13 | Package registry (OSV) |
| red hat:bpftool-debuginfo | 0:7.0.0-284.80.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:5.14.0-284.80.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:5.14.0-284.80.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:5.14.0-284.80.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:5.14.0-284.80.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:5.14.0-284.80.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:5.14.0-284.80.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:5.14.0-284.80.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:5.14.0-284.80.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:5.14.0-284.80.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:5.14.0-284.80.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-aarch64 | 0:5.14.0-284.80.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| rocky linux:kernel | 0:4.18.0-553.27.1.el8_10 · Rocky Linux:8 | Package registry (OSV) |
+1
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-476 · NULL Pointer DereferenceCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.