CVE-2024-35907

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 5.5 from GitHub Security Advisory published 2024-05-19. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
12th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 19, 2024

Last Modified

December 30, 2024

References (5)

Vendor Advisories for CVE-2024-35907(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(16)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-aws-lts-22.04 (5.15.0.1065.65) @ jammy2026-05-24ubuntu
ubuntulinux-tools-nvidia-64k (6.8.0-1009.9) @ noble2026-05-24ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.116.116) @ jammy2026-05-24ubuntu
ubuntulinux-tools-aws (6.8.0-1011.12) @ noble2026-05-24ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1065.73~20.04.1) @ focal2026-05-24ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1068.66) @ jammy2026-05-24ubuntu
ubuntulinux-tools-oracle-64k (6.8.0-1008.8) @ noble2026-05-24ubuntu
ubuntulinux-xilinx-zynqmp-tools-host (5.15.0-1035.39) @ jammy2026-05-24ubuntu
ubuntulinux-tools-aws-edge (5.15.0.1065.71~20.04.1) @ focal2026-05-24ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1058.56) @ jammy2026-05-24ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.8.0-38.38) @ noble2026-05-24ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (5.15.0.116.106) @ jammy2026-05-24ubuntu
redhatkernel-rt-0:5.14.0-284.79.1.rt14.364.el9_22024-08-14redhat
redhatkernel-0:5.14.0-284.79.1.el9_22024-08-14redhat
redhatkernel-0:5.14.0-427.28.1.el9_42024-07-31redhat
linuxKernel @ 5.15.154 (fixes >=5.14.0)—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.27-1 ... 6.1.82-1 (19 versions)
  • every version up to 6.1.85-1: fixed in 6.1.85-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.8.9-1: fixed in 6.8.9-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.8.9-1: fixed in 6.8.9-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(12)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 8× in last 7d / 35× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 93 of 198 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 7 repeat rows among the latest 100 are merged into the row they repeat. The 105 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  2. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  3. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  4. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  5. 2026-10-19 16:29 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  6. 2026-10-18 16:30 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  7. 2026-10-18 07:13 UTCEG score recompute
  8. 2026-10-17 16:31 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  9. 2026-10-16 16:36 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  10. 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  11. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  12. 2026-10-13 16:30 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  13. 2026-10-12 17:52 UTCEG score recompute
  14. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  15. 2026-10-11 21:17 UTCEG score recompute
  16. 2026-10-11 16:10 UTCEG score recompute
  17. 2026-10-11 13:46 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  18. 2026-10-11 00:52 UTCOSV refresh
  19. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  20. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  21. 2026-10-08 17:07 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  22. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  23. 2026-10-06 15:15 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  24. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  25. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.2% · 12th percentile
Show 68 more
  1. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  2. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  3. 2026-09-30 19:46 UTCEG score recompute
  4. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  5. 2026-09-29 15:17 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  6. 2026-09-28 13:49 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  7. 2026-09-27 13:44 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  8. 2026-09-26 15:57 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  9. 2026-09-26 00:23 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  10. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  11. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  12. 2026-09-22 14:46 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  13. 2026-09-21 20:32 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  14. 2026-09-21 12:49 UTCOSV refresh
  15. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  16. 2026-09-19 15:40 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  17. 2026-09-18 19:26 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  18. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  19. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  20. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  21. 2026-09-12 14:59 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  22. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  23. 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  24. 2026-09-08 21:58 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  25. 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  26. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  27. 2026-09-05 15:26 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  28. 2026-09-04 13:59 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  29. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  30. 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  31. 2026-09-02 10:14 UTCOSV refresh
  32. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  33. 2026-09-01 04:37 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  34. 2026-08-30 19:15 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  35. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  36. 2026-08-27 14:23 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  37. 2026-08-26 14:44 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  38. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  39. 2026-08-24 14:15 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  40. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  41. 2026-08-20 22:53 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  42. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  43. 2026-08-18 13:46 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  44. 2026-08-17 13:45 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  45. 2026-08-16 14:54 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  46. 2026-08-16 08:47 UTCOSV refresh
  47. 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  48. 2026-08-15 01:28 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  49. 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  50. 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  51. 2026-08-11 13:40 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  52. 2026-08-10 23:58 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  53. 2026-08-09 13:45 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  54. 2026-08-08 16:35 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  55. 2026-08-07 16:25 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  56. 2026-08-06 13:45 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  57. 2026-08-05 19:16 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  58. 2026-08-04 15:08 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  59. 2026-08-04 10:36 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  60. 2026-08-03 10:34 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  61. 2026-08-02 02:25 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  62. 2026-08-01 04:14 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  63. 2026-08-01 02:42 UTCOSV refresh
  64. 2026-07-30 16:26 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  65. 2026-07-30 01:29 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  66. 2026-07-28 15:34 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  67. 2026-07-27 14:11 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  68. 2026-07-26 14:53 UTCEPSS rescoreEPSS 0.2% · 13th percentile

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-35907?
CVE-2024-35907 is a medium-severity vulnerability; its CVE record was published on May 19, 2024. In the Linux kernel, the following vulnerability has been resolved: mlxbfgige: call requestirq() after NAPI initialized The mlxbf_gige driver encounters a NULL pointer exception in mlxbfgigeopen() when kdump is enabled. The sequence to reproduce the exception is as follows: a) enable kdump b)…
When was the CVE record for CVE-2024-35907 published?
The CVE record for CVE-2024-35907 was published on May 19, 2024. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of December 30, 2024; the record at its source may have been updated since.
Is CVE-2024-35907 actively exploited?
CVE-2024-35907 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (12th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-35907?
CVE-2024-35907 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2024-35907?
A fix for CVE-2024-35907 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-35907 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-35907

Explore →

Is Your Infrastructure Affected by CVE-2024-35907?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs