CVE-2024-26636

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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

llc: make llc_ui_sendmsg() more robust against bonding changes

syzbot was able to trick llc_ui_sendmsg(), allocating an skb with no headroom, but subsequently trying to push 14 bytes of Ethernet header [1]

Like some others, llc_ui_sendmsg() releases the socket lock before calling sock_alloc_send_skb(). Then it acquires it again, but does not redo all the sanity checks that were performed.

This fix:

  • Uses LL_RESERVED_SPACE() to reserve space.
  • Check all conditions again after socket lock is held again.
  • Do not account Ethernet header for mtu limitation.

[1]

skbuff: skb_under_panic: text:ffff800088baa334 len:1514 put:14 head:ffff0000c9c37000 data:ffff0000c9c36ff2 tail:0x5dc end:0x6c0 dev:bond0

kernel BUG at net/core/skbuff.c:193 ! Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP Modules linked in: CPU: 0 PID: 6875 Comm: syz-executor.0 Not tainted 6.7.0-rc8-syzkaller-00101-g0802e17d9aca-dirty #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023 pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : skb_panic net/core/skbuff.c:189 [inline] pc : skb_under_panic+0x13c/0x140 net/core/skbuff.c:203 lr : skb_panic net/core/skbuff.c:189 [inline] lr : skb_under_panic+0x13c/0x140 net/core/skbuff.c:203 sp : ffff800096f97000 x29: ffff800096f97010 x28: ffff80008cc8d668 x27: dfff800000000000 x26: ffff0000cb970c90 x25: 00000000000005dc x24: ffff0000c9c36ff2 x23: ffff0000c9c37000 x22: 00000000000005ea x21: 00000000000006c0 x20: 000000000000000e x19: ffff800088baa334 x18: 1fffe000368261ce x17: ffff80008e4ed000 x16: ffff80008a8310f8 x15: 0000000000000001 x14: 1ffff00012df2d58 x13: 0000000000000000 x12: 0000000000000000 x11: 0000000000000001 x10: 0000000000ff0100 x9 : e28a51f1087e8400 x8 : e28a51f1087e8400 x7 : ffff80008028f8d0 x6 : 0000000000000000 x5 : 0000000000000001 x4 : 0000000000000001 x3 : ffff800082b78714 x2 : 0000000000000001 x1 : 0000000100000000 x0 : 0000000000000089 Call trace: skb_panic net/core/skbuff.c:189 [inline] skb_under_panic+0x13c/0x140 net/core/skbuff.c:203 skb_push+0xf0/0x108 net/core/skbuff.c:2451 eth_header+0x44/0x1f8 net/ethernet/eth.c:83 dev_hard_header include/linux/netdevice.h:3188 [inline] llc_mac_hdr_init+0x110/0x17c net/llc/llc_output.c:33 llc_sap_action_send_xid_c+0x170/0x344 net/llc/llc_s_ac.c:85 llc_exec_sap_trans_actions net/llc/llc_sap.c:153 [inline] llc_sap_next_state net/llc/llc_sap.c:182 [inline] llc_sap_state_process+0x1ec/0x774 net/llc/llc_sap.c:209 llc_build_and_send_xid_pkt+0x12c/0x1c0 net/llc/llc_sap.c:270 llc_ui_sendmsg+0x7bc/0xb1c net/llc/af_llc.c:997 sock_sendmsg_nosec net/socket.c:730 [inline] __sock_sendmsg net/socket.c:745 [inline] sock_sendmsg+0x194/0x274 net/socket.c:767 splice_to_socket+0x7cc/0xd58 fs/splice.c:881 do_splice_from fs/splice.c:933 [inline] direct_splice_actor+0xe4/0x1c0 fs/splice.c:1142 splice_direct_to_actor+0x2a0/0x7e4 fs/splice.c:1088 do_splice_direct+0x20c/0x348 fs/splice.c:1194 do_sendfile+0x4bc/0xc70 fs/read_write.c:1254 __do_sys_sendfile64 fs/read_write.c:1322 [inline] __se_sys_sendfile64 fs/read_write.c:1308 [inline] __arm64_sys_sendfile64+0x160/0x3b4 fs/read_write.c:1308 __invoke_syscall arch/arm64/kernel/syscall.c:37 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:51 el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:136 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:155 el0_svc+0x54/0x158 arch/arm64/kernel/entry-common.c:678 el0t_64_sync_handler+0x84/0xfc arch/arm64/kernel/entry-common.c:696 el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:595 Code: aa1803e6 aa1903e7 a90023f5 94792f6a (d4210000)

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 PROB
0%
EPSS %ILE
15%
KEV
Not listed

Published

March 18, 2024

Last Modified

March 10, 2025

References (18)

Patch Availability(20)

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.

All Vendor Advisories

(19)

Data Freshness Timeline

(refreshed 7× in last 7d / 39× 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 125 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2024-26636?
CVE-2024-26636 is a medium vulnerability published on March 18, 2024. In the Linux kernel, the following vulnerability has been resolved: llc: make llcuisendmsg() more robust against bonding changes syzbot was able to trick llcuisendmsg(), allocating an skb with no headroom, but subsequently trying to push 14 bytes of Ethernet header [1] Like some others,…
When was CVE-2024-26636 disclosed?
CVE-2024-26636 was first published in the National Vulnerability Database on March 18, 2024, with the most recent update on March 10, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-26636 actively exploited?
CVE-2024-26636 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 84.9% of all scored CVEs.
What is the CVSS score of CVE-2024-26636?
CVE-2024-26636 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2024-26636?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-26636, 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-26636

Explore →

Is Your Infrastructure Affected by CVE-2024-26636?

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