CVE-2024-26597

HIGHNVD 7.17.1
EchelonGraph scoreMEDIUM confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2024-23859 (ENISA EUVD) · GHSA-m32w-wmcr-wvxf (GitHub Security Advisories)Source: ENISA EUVD

7.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

net: qualcomm: rmnet: fix global oob in rmnet_policy

The variable rmnet_link_ops assign a *bigger* maxtype which leads to a global out-of-bounds read when parsing the netlink attributes. See bug trace below:

================================================================== BUG: KASAN: global-out-of-bounds in validate_nla lib/nlattr.c:386 [inline] BUG: KASAN: global-out-of-bounds in __nla_validate_parse+0x24af/0x2750 lib/nlattr.c:600 Read of size 1 at addr ffffffff92c438d0 by task syz-executor.6/84207

CPU: 0 PID: 84207 Comm: syz-executor.6 Tainted: G N 6.1.0 #3 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+0x8b/0xb3 lib/dump_stack.c:106 print_address_description mm/kasan/report.c:284 [inline] print_report+0x172/0x475 mm/kasan/report.c:395 kasan_report+0xbb/0x1c0 mm/kasan/report.c:495 validate_nla lib/nlattr.c:386 [inline] __nla_validate_parse+0x24af/0x2750 lib/nlattr.c:600 __nla_parse+0x3e/0x50 lib/nlattr.c:697 nla_parse_nested_deprecated include/net/netlink.h:1248 [inline] __rtnl_newlink+0x50a/0x1880 net/core/rtnetlink.c:3485 rtnl_newlink+0x64/0xa0 net/core/rtnetlink.c:3594 rtnetlink_rcv_msg+0x43c/0xd70 net/core/rtnetlink.c:6091 netlink_rcv_skb+0x14f/0x410 net/netlink/af_netlink.c:2540 netlink_unicast_kernel net/netlink/af_netlink.c:1319 [inline] netlink_unicast+0x54e/0x800 net/netlink/af_netlink.c:1345 netlink_sendmsg+0x930/0xe50 net/netlink/af_netlink.c:1921 sock_sendmsg_nosec net/socket.c:714 [inline] sock_sendmsg+0x154/0x190 net/socket.c:734 ____sys_sendmsg+0x6df/0x840 net/socket.c:2482 ___sys_sendmsg+0x110/0x1b0 net/socket.c:2536 __sys_sendmsg+0xf3/0x1c0 net/socket.c:2565 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3b/0x90 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7fdcf2072359 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fdcf13e3168 EFLAGS: 00000246 ORIG_RAX: 000000000000002e RAX: ffffffffffffffda RBX: 00007fdcf219ff80 RCX: 00007fdcf2072359 RDX: 0000000000000000 RSI: 0000000020000200 RDI: 0000000000000003 RBP: 00007fdcf20bd493 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007fffbb8d7bdf R14: 00007fdcf13e3300 R15: 0000000000022000

The buggy address belongs to the variable: rmnet_policy+0x30/0xe0

The buggy address belongs to the physical page: page:0000000065bdeb3c refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x155243 flags: 0x200000000001000(reserved|node=0|zone=2) raw: 0200000000001000 ffffea00055490c8 ffffea00055490c8 0000000000000000 raw: 0000000000000000 0000000000000000 00000001ffffffff 0000000000000000 page dumped because: kasan: bad access detected

Memory state around the buggy address: ffffffff92c43780: f9 f9 f9 f9 00 00 00 02 f9 f9 f9 f9 00 00 00 07 ffffffff92c43800: f9 f9 f9 f9 00 00 00 05 f9 f9 f9 f9 06 f9 f9 f9 >ffffffff92c43880: f9 f9 f9 f9 00 00 00 00 00 00 f9 f9 f9 f9 f9 f9 ^ ffffffff92c43900: 00 00 00 00 00 00 00 00 07 f9 f9 f9 f9 f9 f9 f9 ffffffff92c43980: 00 00 00 07 f9 f9 f9 f9 00 00 00 05 f9 f9 f9 f9

According to the comment of nla_parse_nested_deprecated, the maxtype should be len(destination array) - 1. Hence use IFLA_RMNET_MAX here.

CVSS v3
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
32
EG Risk 32/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)
Severity71% × 45%
Impact severity (EG Severity): CVSS 7.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 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.3%
EPSS %ILE
17th
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 (7.1): severity, escalated by confirmed exploitation. This CVE's 7.1 is its impact severity (EG Severity), not escalated.

EG Severity
7.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). 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, and whom BOD 26-04 binds: 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.

The score's inputs: 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

February 23, 2024

Last Modified

August 5, 2026

Advisory Details (8)

Auto-updated Aug 5, 2026
Patch available.
Web page

net: qualcomm: rmnet: fix global oob in rmnet_policy - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b33fb5b801c6db408b774a68e7c8722796b59ecc
Web page

net: qualcomm: rmnet: fix global oob in rmnet_policy - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/17d06a5c44d8fd2e8e61bac295b09153496f87e1
Web page

net: qualcomm: rmnet: fix global oob in rmnet_policy - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c4734535034672f59f2652e1e0058c490da62a5c
Web page

net: qualcomm: rmnet: fix global oob in rmnet_policy - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ee1dc3bf86f2df777038506b139371a9add02534
Web page

net: qualcomm: rmnet: fix global oob in rmnet_policy - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3b5254862258b595662a0ccca6e9eeb88d6e7468
Web page

net: qualcomm: rmnet: fix global oob in rmnet_policy - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2295c22348faf795e1ccdf618f6eb7afdb2f7447
Web page

net: qualcomm: rmnet: fix global oob in rmnet_policy - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/02467ab8b404d80429107588e0f3425cf5fcd2e5
Web page

net: qualcomm: rmnet: fix global oob in rmnet_policy - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/093dab655808207f7a9f54cf156240aeafc70590

Patch Availability(13)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-oem-22.04c (6.1.0.1035.36) @ jammy2026-10-28ubuntu
ubuntulinux-tools-laptop-23.10 (6.5.0.1012.15) @ mantic2026-10-28ubuntu
ubuntulinux-tools-azure-edge (6.5.0.1017.17~22.04.1) @ jammy2026-10-28ubuntu
ubuntulinux-tools-aws-edge (5.15.0.1057.63~20.04.1) @ focal2026-10-28ubuntu
ubuntulinux-tools-iot (5.4.0.1034.32) @ focal2026-10-28ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.4.0-1041 (5.4.0-1041.45) @ focal2026-10-28ubuntu
ubuntuibm-5.15 (5.15.0-1000) @ focal2026-10-28ubuntu
ubuntulinux-virtual-hwe-18.04-edge (5.4.0.176.174) @ focal2026-10-28ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.5.0.26.26~22.04.13) @ jammy2026-10-28ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.102.99) @ jammy2026-10-28ubuntu
ubuntulinux-tools-aws (6.5.0.1016.16) @ mantic2026-10-28ubuntu
ubuntuibm (6.8.0-1005) @ noble2026-10-28ubuntu
linuxKernel @ 4.19.306 (fixes >=4.17.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

(6 across 5 ecosystems)
Debian:10(2)
PackageVulnerable rangeFix by version rangeDependents
linux4.19.118-1 ... 4.19.98-1~bpo9+1 (46 versions)
  • every version up to 4.19.316-1: fixed in 4.19.316-1
—
linux-5.105.10.136-1~deb10u1 ... 5.10.205-2~deb10u1 (12 versions)
  • every version up to 5.10.209-2~deb10u1: fixed in 5.10.209-2~deb10u1
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (37 versions)
  • every version up to 5.10.209-1: fixed in 5.10.209-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.27-1 ... 6.1.76-1~bpo11+1 (17 versions)
  • every version up to 6.1.76-1: fixed in 6.1.76-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.6.15-1: fixed in 6.6.15-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.6.15-1: fixed in 6.6.15-1
—

Weakness Classification(1)

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

All Vendor Advisories

(12)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 10× in last 7d / 41× 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 98 of 215 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. 2 repeat rows among the latest 100 are merged into the row they repeat. The 117 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-26597?
CVE-2024-26597 is a high-severity vulnerability; its CVE record was published on February 23, 2024. In the Linux kernel, the following vulnerability has been resolved: net: qualcomm: rmnet: fix global oob in rmnet_policy The variable rmnet_link_ops assign a bigger maxtype which leads to a global out-of-bounds read when parsing the netlink attributes. See bug trace below:…
When was the CVE record for CVE-2024-26597 published?
The CVE record for CVE-2024-26597 was published on February 23, 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 August 5, 2026; the record at its source may have been updated since.
Is CVE-2024-26597 actively exploited?
CVE-2024-26597 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (17th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-26597?
CVE-2024-26597 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2024-26597?
A fix for CVE-2024-26597 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2024-26597?

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

Book a Demo →Browse All CVEs