CVE-2024-36933

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.5 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 79% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
5.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.5Exploit: NoneExposed: 0

A fix is available — apply it.

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

nsh: Restore skb->{protocol,data,mac_header} for outer header in nsh_gso_segment().

syzbot triggered various splats (see [0] and links) by a crafted GSO packet of VIRTIO_NET_HDR_GSO_UDP layering the following protocols:

ETH_P_8021AD + ETH_P_NSH + ETH_P_IPV6 + IPPROTO_UDP

NSH can encapsulate IPv4, IPv6, Ethernet, NSH, and MPLS. As the inner protocol can be Ethernet, NSH GSO handler, nsh_gso_segment(), calls skb_mac_gso_segment() to invoke inner protocol GSO handlers.

nsh_gso_segment() does the following for the original skb before calling skb_mac_gso_segment()

  • reset skb->network_header
  • save the original skb->{mac_heaeder,mac_len} in a local variable
  • pull the NSH header
  • resets skb->mac_header
  • set up skb->mac_len and skb->protocol for the inner protocol.

and does the following for the segmented skb

  • set ntohs(ETH_P_NSH) to skb->protocol
  • push the NSH header
  • restore skb->mac_header
  • set skb->mac_header + mac_len to skb->network_header
  • restore skb->mac_len

There are two problems in 6-7 and 8-9.

(a) After 6 & 7, skb->data points to the NSH header, so the outer header (ETH_P_8021AD in this case) is stripped when skb is sent out of netdev.

Also, if NSH is encapsulated by NSH + Ethernet (so NSH-Ethernet-NSH), skb_pull() in the first nsh_gso_segment() will make skb->data point to the middle of the outer NSH or Ethernet header because the Ethernet header is not pulled by the second nsh_gso_segment().

(b) While restoring skb->{mac_header,network_header} in 8 & 9, nsh_gso_segment() does not assume that the data in the linear buffer is shifted.

However, udp6_ufo_fragment() could shift the data and change skb->mac_header accordingly as demonstrated by syzbot.

If this happens, even the restored skb->mac_header points to the middle of the outer header.

It seems nsh_gso_segment() has never worked with outer headers so far.

At the end of nsh_gso_segment(), the outer header must be restored for the segmented skb, instead of the NSH header.

To do that, let's calculate the outer header position relatively from the inner header and set skb->{data,mac_header,protocol} properly.

[0]: BUG: KMSAN: uninit-value in ipvlan_process_outbound drivers/net/ipvlan/ipvlan_core.c:524 [inline] BUG: KMSAN: uninit-value in ipvlan_xmit_mode_l3 drivers/net/ipvlan/ipvlan_core.c:602 [inline] BUG: KMSAN: uninit-value in ipvlan_queue_xmit+0xf44/0x16b0 drivers/net/ipvlan/ipvlan_core.c:668 ipvlan_process_outbound drivers/net/ipvlan/ipvlan_core.c:524 [inline] ipvlan_xmit_mode_l3 drivers/net/ipvlan/ipvlan_core.c:602 [inline] ipvlan_queue_xmit+0xf44/0x16b0 drivers/net/ipvlan/ipvlan_core.c:668 ipvlan_start_xmit+0x5c/0x1a0 drivers/net/ipvlan/ipvlan_main.c:222 __netdev_start_xmit include/linux/netdevice.h:4989 [inline] netdev_start_xmit include/linux/netdevice.h:5003 [inline] xmit_one net/core/dev.c:3547 [inline] dev_hard_start_xmit+0x244/0xa10 net/core/dev.c:3563 __dev_queue_xmit+0x33ed/0x51c0 net/core/dev.c:4351 dev_queue_xmit include/linux/netdevice.h:3171 [inline] packet_xmit+0x9c/0x6b0 net/packet/af_packet.c:276 packet_snd net/packet/af_packet.c:3081 [inline] packet_sendmsg+0x8aef/0x9f10 net/packet/af_packet.c:3113 sock_sendmsg_nosec net/socket.c:730 [inline] __sock_sendmsg net/socket.c:745 [inline] __sys_sendto+0x735/0xa10 net/socket.c:2191 __do_sys_sendto net/socket.c:2203 [inline] __se_sys_sendto net/socket.c:2199 [inline] __x64_sys_sendto+0x125/0x1c0 net/socket.c:2199 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcf/0x1e0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x63/0x6b

Uninit was created at: slab_post_alloc_hook mm/slub.c:3819 [inline] slab_alloc_node mm/slub.c:3860 [inline] __do_kmalloc_node mm/slub.c:3980 [inline] __kmalloc_node_track_caller+0x705/0x1000 mm/slub.c:4001 kmalloc_reserve+0x249/0x4a0 net/core/skbuff.c:582 __ ---truncated---

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
25(Track)
EG Risk 25/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
Severity55% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
20.7%
KEV
Not listed

Published

May 30, 2024

Last Modified

January 22, 2026

References (19)

Patch Availability(22)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-raspi (6.8.0-1009.10) @ noble2026-05-24ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1065.61) @ jammy2026-05-24ubuntu
ubuntulinux-tools-oracle-lts-20.04 (5.4.0.1129.122) @ focal2026-05-24ubuntu
ubuntulinux-tools-oem-24.04a (6.8.0-1010.10) @ noble2026-05-24ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.4.0-1049 (5.4.0-1049.53) @ focal2026-05-24ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.118.128~20.04.1) @ focal2026-05-24ubuntu
ubuntulinux-tools-azure-edge (5.4.0.1135.142~18.04.1) @ bionic2026-05-24ubuntu
ubuntulinux-tools-azure-lts-20.04 (5.4.0.1135.129) @ focal2026-05-24ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1060.58) @ jammy2026-05-24ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1065.71~20.04.1) @ focal2026-05-24ubuntu
ubuntulinux-tools-bluefield (5.4.0.1090.86) @ focal2026-05-24ubuntu
ubuntulinux-tools-raspi-hwe-18.04-edge (5.4.0.1114.126~18.04.1) @ bionic2026-05-24ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.118.118) @ jammy2026-05-24ubuntu
ubuntulinux-xilinx-zynqmp-tools-host (5.15.0-1035.39) @ jammy2026-05-24ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.8.0-40.40) @ noble2026-05-24ubuntu
ubuntulinux-tools-oracle-64k (6.8.0-1010.10) @ noble2026-05-24ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1070.68) @ jammy2026-05-24ubuntu
redhatkernel-0:5.14.0-427.72.1.el9_42025-06-11redhat
redhatkernel-0:5.14.0-503.11.1.el9_52024-11-12redhat
redhatkernel-rt-0:4.18.0-553.16.1.rt7.357.el8_102024-08-08redhat
redhatkernel-0:4.18.0-553.16.1.el8_102024-08-08redhat
linuxKernel @ 4.19.314osv

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

(17)

Data Freshness Timeline

(refreshed 12× in last 7d / 46× 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.

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

Frequently asked(5)

What is CVE-2024-36933?
CVE-2024-36933 is a medium vulnerability published on May 30, 2024. In the Linux kernel, the following vulnerability has been resolved: nsh: Restore skb->{protocol,data,macheader} for outer header in nshgso_segment(). syzbot triggered various splats (see [0] and links) by a crafted GSO packet of VIRTIONETHDRGSOUDP layering the following protocols: ETHP8021AD +…
When was CVE-2024-36933 disclosed?
CVE-2024-36933 was first published in the National Vulnerability Database on May 30, 2024, with the most recent update on January 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-36933 actively exploited?
CVE-2024-36933 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 20.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2024-36933?
CVE-2024-36933 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2024-36933?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-36933, 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-36933

Explore →

Is Your Infrastructure Affected by CVE-2024-36933?

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