CVE-2024-50128

HIGHNVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2024-11-05. NVD baseline CVSS 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.1Exploit: NoneExposed: 0

A fix is available — apply it.

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

net: wwan: fix global oob in wwan_rtnl_policy

The variable wwan_rtnl_link_ops assign a *bigger* maxtype which leads to a global out-of-bounds read when parsing the netlink attributes. Exactly same bug cause as the oob fixed in commit b33fb5b801c6 ("net: qualcomm: rmnet: fix global oob in rmnet_policy").

================================================================== BUG: KASAN: global-out-of-bounds in validate_nla lib/nlattr.c:388 [inline] BUG: KASAN: global-out-of-bounds in __nla_validate_parse+0x19d7/0x29a0 lib/nlattr.c:603 Read of size 1 at addr ffffffff8b09cb60 by task syz.1.66276/323862

CPU: 0 PID: 323862 Comm: syz.1.66276 Not tainted 6.1.70 #1 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/2014 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x177/0x231 lib/dump_stack.c:106 print_address_description mm/kasan/report.c:284 [inline] print_report+0x14f/0x750 mm/kasan/report.c:395 kasan_report+0x139/0x170 mm/kasan/report.c:495 validate_nla lib/nlattr.c:388 [inline] __nla_validate_parse+0x19d7/0x29a0 lib/nlattr.c:603 __nla_parse+0x3c/0x50 lib/nlattr.c:700 nla_parse_nested_deprecated include/net/netlink.h:1269 [inline] __rtnl_newlink net/core/rtnetlink.c:3514 [inline] rtnl_newlink+0x7bc/0x1fd0 net/core/rtnetlink.c:3623 rtnetlink_rcv_msg+0x794/0xef0 net/core/rtnetlink.c:6122 netlink_rcv_skb+0x1de/0x420 net/netlink/af_netlink.c:2508 netlink_unicast_kernel net/netlink/af_netlink.c:1326 [inline] netlink_unicast+0x74b/0x8c0 net/netlink/af_netlink.c:1352 netlink_sendmsg+0x882/0xb90 net/netlink/af_netlink.c:1874 sock_sendmsg_nosec net/socket.c:716 [inline] __sock_sendmsg net/socket.c:728 [inline] ____sys_sendmsg+0x5cc/0x8f0 net/socket.c:2499 ___sys_sendmsg+0x21c/0x290 net/socket.c:2553 __sys_sendmsg net/socket.c:2582 [inline] __do_sys_sendmsg net/socket.c:2591 [inline] __se_sys_sendmsg+0x19e/0x270 net/socket.c:2589 do_syscall_x64 arch/x86/entry/common.c:51 [inline] do_syscall_64+0x45/0x90 arch/x86/entry/common.c:81 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7f67b19a24ad RSP: 002b:00007f67b17febb8 EFLAGS: 00000246 ORIG_RAX: 000000000000002e RAX: ffffffffffffffda RBX: 00007f67b1b45f80 RCX: 00007f67b19a24ad RDX: 0000000000000000 RSI: 0000000020005e40 RDI: 0000000000000004 RBP: 00007f67b1a1e01d R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ffd2513764f R14: 00007ffd251376e0 R15: 00007f67b17fed40

The buggy address belongs to the variable: wwan_rtnl_policy+0x20/0x40

The buggy address belongs to the physical page: page:ffffea00002c2700 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0xb09c flags: 0xfff00000001000(reserved|node=0|zone=1|lastcpupid=0x7ff) raw: 00fff00000001000 ffffea00002c2708 ffffea00002c2708 0000000000000000 raw: 0000000000000000 0000000000000000 00000001ffffffff 0000000000000000 page dumped because: kasan: bad access detected page_owner info is not present (never set?)

Memory state around the buggy address: ffffffff8b09ca00: 05 f9 f9 f9 05 f9 f9 f9 00 01 f9 f9 00 01 f9 f9 ffffffff8b09ca80: 00 00 00 05 f9 f9 f9 f9 00 00 03 f9 f9 f9 f9 f9 >ffffffff8b09cb00: 00 00 00 00 05 f9 f9 f9 00 00 00 00 f9 f9 f9 f9 ^ ffffffff8b09cb80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ==================================================================

According to the comment of nla_parse_nested_deprecated, use correct size IFLA_WWAN_MAX here to fix this issue.

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
32(Track)
EG Risk 32/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity71% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
13.6%
KEV
Not listed

Published

November 5, 2024

Last Modified

November 3, 2025

References (6)

Vendor Advisories for CVE-2024-50128(1)

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

Patch Availability(28)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-24.04-edge (6.11.0-18.18) @ oracular2026-05-23ubuntu
ubuntulinux-tools-nvidia-tegra-rt (5.15.0.1033.33) @ jammy2026-05-23ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1072.70) @ jammy2026-05-23ubuntu
ubuntulinux-xilinx-zynqmp-tools-host (5.15.0-1044.48) @ jammy2026-05-23ubuntu
ubuntulinux-tools-aws-lts-22.04 (5.15.0.1078.80) @ jammy2026-05-23ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (5.15.0.133.143~20.04.1) @ focal2026-05-23ubuntu
ubuntulinux-tools-gke-5.15 (5.15.0.1075.74) @ jammy2026-05-23ubuntu
ubuntulinux-tools-ibm (5.15.0.1070.66) @ jammy2026-05-23ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1075.81~20.04.1) @ focal2026-05-23ubuntu
ubuntulinux-tools-intel-iotg (5.15.0.1073.73) @ jammy2026-05-23ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.134.145~20.04.1) @ focal2026-05-23ubuntu
ubuntulinux-tools-kvm (5.15.0.1076.72) @ jammy2026-05-23ubuntu
ubuntulinux-virtual (6.8.0-58.60) @ noble2026-05-23ubuntu
ubuntulinux-tools-oem-24.04b (6.11.0-1015.15) @ noble2026-05-23ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.133.132) @ jammy2026-05-23ubuntu
ubuntulinux-tools-gkeop-6.8 (6.8.0-1010.12) @ noble2026-05-23ubuntu
ubuntulinux-tools-raspi-realtime (6.8.0-2023.24) @ noble2026-05-23ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-58.60~22.04.1) @ jammy2026-05-23ubuntu
ubuntulinux-tools-gcp-edge (6.8.0-1028.30~22.04.1) @ jammy2026-05-23ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1075.71) @ jammy2026-05-23ubuntu
ubuntulinux-tools-azure-nvidia (6.8.0-1014.15) @ noble2026-05-23ubuntu
ubuntulinux-tools-aws-edge (6.8.0-1027.29~22.04.1) @ jammy2026-05-23ubuntu
ubuntulinux-tools-ibm-edge (5.15.0.1074.77~20.04.1) @ focal2026-05-23ubuntu
ubuntulinux-tools-realtime-hwe-24.04 (6.8.1-1020.21) @ noble2026-05-23ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.11.0-1005.5) @ oracular2026-05-23ubuntu
ubuntulinux-tools-raspi (6.8.0-1028.32) @ noble2026-05-23ubuntu
redhatkernel-0:5.14.0-570.12.1.el9_62025-05-13redhat
linuxKernel @ 5.15.170—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.

Weakness Classification(1)

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

Additional Vendor Advisories

(24)

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 13× in last 7d / 43× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 101 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-50128?
CVE-2024-50128 is a high vulnerability published on November 5, 2024. In the Linux kernel, the following vulnerability has been resolved: net: wwan: fix global oob in wwanrtnlpolicy The variable wwanrtnllink_ops assign a bigger maxtype which leads to a global out-of-bounds read when parsing the netlink attributes. Exactly same bug cause as the oob fixed in commit…
When was CVE-2024-50128 disclosed?
CVE-2024-50128 was first published in the National Vulnerability Database on November 5, 2024, with the most recent update on November 3, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-50128 actively exploited?
CVE-2024-50128 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 13.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2024-50128?
CVE-2024-50128 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2024-50128?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-50128, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2024-50128

Explore →

Is Your Infrastructure Affected by CVE-2024-50128?

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

Start Free Scan →Browse All CVEs