Skip to content
Noroxi
CVE-2024-35907· NVD / CVE Program· CNA Linux

mlxbf_gige: call request_irq() after NAPI initialized

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.22% (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 24444af5ddf729376b90db0f135fa19973cb5dab, 867a2f598af6a645c865d1101b58c5e070c6dd9e, 8feb1652afe9c5d019059a55c90f70690dce0f52.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 24444af5ddf729376b90db0f135fa19973cb5dab, 867a2f598af6a645c865d1101b58c5e070c6dd9e, 8feb1652afe9c5d019059a55c90f70690dce0f52 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: mlxbf_gige: call request_irq() after NAPI initialized The mlxbf_gige driver encounters a NULL pointer exception in mlxbf_gige_open() when kdump is enabled. The sequence to reproduce the exception is as follows: a) enable kdump b) trigger kdump via "echo c > /proc/sysrq-trigger" c) kdump kernel executes d) kdump kernel loads mlxbf_gige module e) the mlxbf_gige module runs its open() as the the "oob_net0" interface is brought up f) mlxbf_gige module will experience an exception during its open(), something like: Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000 Mem abort info: ESR = 0x0000000086000004 EC = 0x21: IABT (current EL), IL = 32 bits SET = 0, FnV = 0 EA = 0, S1PTW = 0 FSC = 0x04: level 0 translation fault user pgtable: 4k pages, 48-bit VAs, pgdp=00000000e29a4000 [0000000000000000] pgd=0000000000000000, p4d=0000000000000000 Internal error: Oops: 0000000086000004 [#1] SMP CPU: 0 PID: 812 Comm: NetworkManager Tainted: G OE 5.15.0-1035-bluefield #37-Ubuntu Hardware name: https://www.mellanox.com BlueField-3 SmartNIC Main Card/BlueField-3 SmartNIC Main Card, BIOS 4.6.0.13024 Jan 19 2024 pstate: 80400009 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : 0x0 lr : __napi_poll+0x40/0x230 sp : ffff800008003e00 x29: ffff800008003e00 x28: 0000000000000000 x27: 00000000ffffffff x26: ffff000066027238 x25: ffff00007cedec00 x24: ffff800008003ec8 x23: 000000000000012c x22: ffff800008003eb7 x21: 0000000000000000 x20: 0000000000000001 x19: ffff000066027238 x18: 0000000000000000 x17: ffff578fcb450000 x16: ffffa870b083c7c0 x15: 0000aaab010441d0 x14: 0000000000000001 x13: 00726f7272655f65 x12: 6769675f6662786c x11: 0000000000000000 x10: 0000000000000000 x9 : ffffa870b0842398 x8 : 0000000000000004 x7 : fe5a48b9069706ea x6 : 17fdb11fc84ae0d2 x5 : d94a82549d594f35 x4 : 0000000000000000 x3 : 0000000000400100 x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff000066027238 Call trace: 0x0 net_rx_action+0x178/0x360 __do_softirq+0x15c/0x428 __irq_exit_rcu+0xac/0xec irq_exit+0x18/0x2c handle_domain_irq+0x6c/0xa0 gic_handle_irq+0xec/0x1b0 call_on_irq_stack+0x20/0x2c do_interrupt_handler+0x5c/0x70 el1_interrupt+0x30/0x50 el1h_64_irq_handler+0x18/0x2c el1h_64_irq+0x7c/0x80 __setup_irq+0x4c0/0x950 request_threaded_irq+0xf4/0x1bc mlxbf_gige_request_irqs+0x68/0x110 [mlxbf_gige] mlxbf_gige_open+0x5c/0x170 [mlxbf_gige] __dev_open+0x100/0x220 __dev_change_flags+0x16c/0x1f0 dev_change_flags+0x2c/0x70 do_setlink+0x220/0xa40 __rtnl_newlink+0x56c/0x8a0 rtnl_newlink+0x58/0x84 rtnetlink_rcv_msg+0x138/0x3c4 netlink_rcv_skb+0x64/0x130 rtnetlink_rcv+0x20/0x30 netlink_unicast+0x2ec/0x360 netlink_sendmsg+0x278/0x490 __sock_sendmsg+0x5c/0x6c ____sys_sendmsg+0x290/0x2d4 ___sys_sendmsg+0x84/0xd0 __sys_sendmsg+0x70/0xd0 __arm64_sys_sendmsg+0x2c/0x40 invoke_syscall+0x78/0x100 el0_svc_common.constprop.0+0x54/0x184 do_el0_svc+0x30/0xac el0_svc+0x48/0x160 el0t_64_sync_handler+0xa4/0x12c el0t_64_sync+0x1a4/0x1a8 Code: bad PC value ---[ end trace 7d1c3f3bf9d81885 ]--- Kernel panic - not syncing: Oops: Fatal exception in interrupt Kernel Offset: 0x2870a7a00000 from 0xffff800008000000 PHYS_OFFSET: 0x80000000 CPU features: 0x0,000005c1,a3332a5a Memory Limit: none ---[ end Kernel panic - not syncing: Oops: Fatal exception in interrupt ]--- The exception happens because there is a pending RX interrupt before the call to request_irq(RX IRQ) executes. Then, the RX IRQ handler fires immediately after this request_irq() completes. The ---truncated---

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
May 19, 2024
Updated
Jun 17, 2026
EPSS
0.2% · 12th percentile

Report tools

JSON

Action score

22

Monitor

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.

Follow CVE-2024-35907

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi 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 help

Affected 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.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel5.14 and later · before 5.15.154
  • linux linux kernel5.16 and later · before 6.1.85
  • linux linux kernel6.2 and later · before 6.6.26
  • linux linux kernel6.7 and later · before 6.8.5
  • linux linux kernel6.9

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

    • 5.14affected
    • f92e1869d74e1acc6551256eb084a1c14a054e19 and later · before a583117668ddb86e98f2e11c7caa3db0e6df52a3affected · git
    • f92e1869d74e1acc6551256eb084a1c14a054e19 and later · before 24444af5ddf729376b90db0f135fa19973cb5dabaffected · git
    • f92e1869d74e1acc6551256eb084a1c14a054e19 and later · before 867a2f598af6a645c865d1101b58c5e070c6dd9eaffected · git
    • f92e1869d74e1acc6551256eb084a1c14a054e19 and later · before 8feb1652afe9c5d019059a55c90f70690dce0f52affected · git
    • f92e1869d74e1acc6551256eb084a1c14a054e19 and later · before f7442a634ac06b953fc1f7418f307b25acd4cfbcaffected · git
    • before 5.14not affected · semver
    • 5.15.154 and later · up to and including 5.15.*not affected · semver
    • 6.1.85 and later · up to and including 6.1.*not affected · semver
    • 6.6.26 and later · up to and including 6.6.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:9bpftoolbefore 7.3.0-427.28.1.el9_47.3.0-427.28.1.el9_4
AlmaLinux:9kernelbefore 5.14.0-427.28.1.el9_45.14.0-427.28.1.el9_4
AlmaLinux:9kernel-64kbefore 5.14.0-427.28.1.el9_45.14.0-427.28.1.el9_4
AlmaLinux:9kernel-64k-corebefore 5.14.0-427.28.1.el9_45.14.0-427.28.1.el9_4
AlmaLinux:9kernel-64k-debugbefore 5.14.0-427.28.1.el9_45.14.0-427.28.1.el9_4
AlmaLinux:9kernel-64k-debug-corebefore 5.14.0-427.28.1.el9_45.14.0-427.28.1.el9_4
AlmaLinux:9kernel-64k-debug-develbefore 5.14.0-427.28.1.el9_45.14.0-427.28.1.el9_4
AlmaLinux:9kernel-64k-debug-devel-matchedbefore 5.14.0-427.28.1.el9_45.14.0-427.28.1.el9_4
AlmaLinux:9kernel-64k-debug-modulesbefore 5.14.0-427.28.1.el9_45.14.0-427.28.1.el9_4
AlmaLinux:9kernel-64k-debug-modules-corebefore 5.14.0-427.28.1.el9_45.14.0-427.28.1.el9_4
AlmaLinux:9kernel-64k-debug-modules-extrabefore 5.14.0-427.28.1.el9_45.14.0-427.28.1.el9_4
AlmaLinux:9kernel-64k-develbefore 5.14.0-427.28.1.el9_45.14.0-427.28.1.el9_4
AlmaLinux:9kernel-64k-devel-matchedbefore 5.14.0-427.28.1.el9_45.14.0-427.28.1.el9_4
AlmaLinux:9kernel-64k-modulesbefore 5.14.0-427.28.1.el9_45.14.0-427.28.1.el9_4
AlmaLinux:9kernel-64k-modules-corebefore 5.14.0-427.28.1.el9_45.14.0-427.28.1.el9_4
AlmaLinux:9kernel-64k-modules-extrabefore 5.14.0-427.28.1.el9_45.14.0-427.28.1.el9_4
AlmaLinux:9kernel-abi-stablelistsbefore 5.14.0-427.28.1.el9_45.14.0-427.28.1.el9_4
AlmaLinux:9kernel-corebefore 5.14.0-427.28.1.el9_45.14.0-427.28.1.el9_4
AlmaLinux:9kernel-cross-headersbefore 5.14.0-427.28.1.el9_45.14.0-427.28.1.el9_4
AlmaLinux:9kernel-debugbefore 5.14.0-427.28.1.el9_45.14.0-427.28.1.el9_4
AlmaLinux:9kernel-debug-corebefore 5.14.0-427.28.1.el9_45.14.0-427.28.1.el9_4
AlmaLinux:9kernel-debug-develbefore 5.14.0-427.28.1.el9_45.14.0-427.28.1.el9_4
AlmaLinux:9kernel-debug-devel-matchedbefore 5.14.0-427.28.1.el9_45.14.0-427.28.1.el9_4
AlmaLinux:9kernel-debug-modulesbefore 5.14.0-427.28.1.el9_45.14.0-427.28.1.el9_4

+96

Other highest-scoring records for the same primary product.

  • 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 KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now
  • CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV
    83Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-35903May 19, 2024 · x86/bpf: Fix IP after emitting call depth accounting
    22Monitor
  • ← EarlierCVE-2024-35904May 19, 2024 · selinux: avoid dereference of garbage after mount failure
    22Monitor
  • Later →CVE-2024-35908May 19, 2024 · tls: get psock ref after taking rxlock to avoid leak
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux24444af5ddf729376b90db0f135fa19973cb5dabVendor (CNA)
Linux Linux867a2f598af6a645c865d1101b58c5e070c6dd9eVendor (CNA)
Linux Linux8feb1652afe9c5d019059a55c90f70690dce0f52Vendor (CNA)
Linux Linuxa583117668ddb86e98f2e11c7caa3db0e6df52a3Vendor (CNA)
Linux Linuxf7442a634ac06b953fc1f7418f307b25acd4cfbcVendor (CNA)
almalinux:bpftool7.3.0-427.28.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel5.14.0-427.28.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-427.28.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-427.28.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-427.28.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-427.28.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-427.28.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-427.28.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-427.28.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-427.28.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-427.28.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-427.28.1.el9_4 · AlmaLinux:9Package registry (OSV)
debian:linux6.1.85-1 · Debian:12Package registry (OSV)
red hat:bpftool-debuginfo0:7.3.0-427.28.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-427.28.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-427.28.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-427.28.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-427.28.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-427.28.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-427.28.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-427.28.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-427.28.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-427.28.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-427.28.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-aarch640:5.14.0-427.28.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage 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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

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

CVSS 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

All records