CVE-2024-26780

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-04-04. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2024-24042 (ENISA EUVD) · GHSA-95rc-29j2-q3vr (GitHub Security Advisories)Source: ENISA EUVD

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:

af_unix: Fix task hung while purging oob_skb in GC.

syzbot reported a task hung; at the same time, GC was looping infinitely in list_for_each_entry_safe() for OOB skb. [0]

syzbot demonstrated that the list_for_each_entry_safe() was not actually safe in this case.

A single skb could have references for multiple sockets. If we free such a skb in the list_for_each_entry_safe(), the current and next sockets could be unlinked in a single iteration.

unix_notinflight() uses list_del_init() to unlink the socket, so the prefetched next socket forms a loop itself and list_for_each_entry_safe() never stops.

Here, we must use while() and make sure we always fetch the first socket.

[0]: Sending NMI from CPU 0 to CPUs 1: NMI backtrace for cpu 1 CPU: 1 PID: 5065 Comm: syz-executor236 Not tainted 6.8.0-rc3-syzkaller-00136-g1f719a2f3fa6 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024 RIP: 0010:preempt_count arch/x86/include/asm/preempt.h:26 [inline] RIP: 0010:check_kcov_mode kernel/kcov.c:173 [inline] RIP: 0010:__sanitizer_cov_trace_pc+0xd/0x60 kernel/kcov.c:207 Code: cc cc cc cc 66 0f 1f 84 00 00 00 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3 0f 1e fa 65 48 8b 14 25 40 c2 03 00 <65> 8b 05 b4 7c 78 7e a9 00 01 ff 00 48 8b 34 24 74 0f f6 c4 01 74 RSP: 0018:ffffc900033efa58 EFLAGS: 00000283 RAX: ffff88807b077800 RBX: ffff88807b077800 RCX: 1ffffffff27b1189 RDX: ffff88802a5a3b80 RSI: ffffffff8968488d RDI: ffff88807b077f70 RBP: ffffc900033efbb0 R08: 0000000000000001 R09: fffffbfff27a900c R10: ffffffff93d48067 R11: ffffffff8ae000eb R12: ffff88807b077800 R13: dffffc0000000000 R14: ffff88807b077e40 R15: 0000000000000001 FS: 0000000000000000(0000) GS:ffff8880b9500000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000564f4fc1e3a8 CR3: 000000000d57a000 CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: unix_gc+0x563/0x13b0 net/unix/garbage.c:319 unix_release_sock+0xa93/0xf80 net/unix/af_unix.c:683 unix_release+0x91/0xf0 net/unix/af_unix.c:1064 __sock_release+0xb0/0x270 net/socket.c:659 sock_close+0x1c/0x30 net/socket.c:1421 __fput+0x270/0xb80 fs/file_table.c:376 task_work_run+0x14f/0x250 kernel/task_work.c:180 exit_task_work include/linux/task_work.h:38 [inline] do_exit+0xa8a/0x2ad0 kernel/exit.c:871 do_group_exit+0xd4/0x2a0 kernel/exit.c:1020 __do_sys_exit_group kernel/exit.c:1031 [inline] __se_sys_exit_group kernel/exit.c:1029 [inline] __x64_sys_exit_group+0x3e/0x50 kernel/exit.c:1029 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xd5/0x270 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x6f/0x77 RIP: 0033:0x7f9d6cbdac09 Code: Unable to access opcode bytes at 0x7f9d6cbdabdf. RSP: 002b:00007fff5952feb8 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7 RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f9d6cbdac09 RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000000 RBP: 00007f9d6cc552b0 R08: ffffffffffffffb8 R09: 0000000000000006 R10: 0000000000000006 R11: 0000000000000246 R12: 00007f9d6cc552b0 R13: 0000000000000000 R14: 00007f9d6cc55d00 R15: 00007f9d6cbabe70

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-25). 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

April 4, 2024

Last Modified

March 18, 2025

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
linuxKernel @ 6.1.81 (fixes >=6.1.78)—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.76-1~bpo11+1 (18 versions)
  • every version up to 6.1.82-1: fixed in 6.1.82-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.7.9-1: fixed in 6.7.9-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.7.9-1: fixed in 6.7.9-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 38× 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 97 of 210 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. 3 repeat rows among the latest 100 are merged into the row they repeat. The 113 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.2% · 12th percentile
  2. 2026-11-01 16:31 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  3. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  4. 2026-10-30 16:31 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  5. 2026-10-29 16:30 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  6. 2026-10-28 16:29 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  7. 2026-10-27 16:29 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  8. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  9. 2026-10-25 17:15 UTCEG score recompute
  10. 2026-10-25 16:30 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  11. 2026-10-24 16:30 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  12. 2026-10-24 08:24 UTCEG score recompute
  13. 2026-10-24 08:24 UTCGHSA enrichmentGHSA-95rc-29j2-q3vr · GitHub CVSS 5.5
  14. 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  15. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  16. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  17. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  18. 2026-10-19 16:29 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  19. 2026-10-18 16:29 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  20. 2026-10-18 07:22 UTCEG score recompute
  21. 2026-10-17 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  22. 2026-10-16 16:36 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  23. 2026-10-15 16:29 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  24. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  25. 2026-10-13 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
Show 72 more
  1. 2026-10-12 17:59 UTCEG score recompute
  2. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  3. 2026-10-11 21:23 UTCEG score recompute
  4. 2026-10-11 16:24 UTCOSV refresh
  5. 2026-10-11 16:17 UTCEG score recompute
  6. 2026-10-11 13:45 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  7. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  8. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  9. 2026-10-08 17:07 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  10. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  11. 2026-10-06 15:15 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  12. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  13. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  14. 2026-10-03 14:23 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  15. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  16. 2026-09-30 16:59 UTCEG score recompute
  17. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  18. 2026-09-29 15:17 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  19. 2026-09-28 13:49 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  20. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  21. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  22. 2026-09-22 04:15 UTCOSV refresh
  23. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  24. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  25. 2026-09-16 05:11 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  26. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  27. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  28. 2026-09-12 14:59 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  29. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  30. 2026-09-11 09:34 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  31. 2026-09-08 21:58 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  32. 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  33. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  34. 2026-09-05 15:26 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  35. 2026-09-04 13:58 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  36. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  37. 2026-09-03 01:30 UTCOSV refresh
  38. 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  39. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  40. 2026-08-30 19:15 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  41. 2026-08-30 01:20 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  42. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  43. 2026-08-27 14:23 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  44. 2026-08-26 14:44 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  45. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  46. 2026-08-23 00:17 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  47. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  48. 2026-08-20 22:53 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  49. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  50. 2026-08-18 13:46 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  51. 2026-08-17 13:45 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  52. 2026-08-16 14:54 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  53. 2026-08-16 14:30 UTCOSV refresh
  54. 2026-08-16 02:12 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  55. 2026-08-15 01:28 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  56. 2026-08-13 21:58 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  57. 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  58. 2026-08-11 13:40 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  59. 2026-08-09 13:45 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  60. 2026-08-08 16:35 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  61. 2026-08-06 13:45 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  62. 2026-08-05 19:15 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  63. 2026-08-04 15:08 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  64. 2026-08-04 10:36 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  65. 2026-08-03 10:34 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  66. 2026-08-02 02:25 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  67. 2026-08-01 08:06 UTCOSV refresh
  68. 2026-08-01 04:14 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  69. 2026-07-30 16:26 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  70. 2026-07-30 01:29 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  71. 2026-07-28 15:34 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  72. 2026-07-27 14:11 UTCEPSS rescoreEPSS 0.2% · 12th percentile

Frequently asked(5)

What is CVE-2024-26780?
CVE-2024-26780 is a medium-severity vulnerability; its CVE record was published on April 4, 2024. In the Linux kernel, the following vulnerability has been resolved: af_unix: Fix task hung while purging oob_skb in GC. syzbot reported a task hung; at the same time, GC was looping infinitely in list_for_each_entry_safe() for OOB skb. [0] syzbot demonstrated that the list_for_each_entry_safe() was…
When was the CVE record for CVE-2024-26780 published?
The CVE record for CVE-2024-26780 was published on April 4, 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 March 18, 2025; the record at its source may have been updated since.
Is CVE-2024-26780 actively exploited?
CVE-2024-26780 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-26780?
CVE-2024-26780 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2024-26780?
A fix for CVE-2024-26780 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-26780

Explore →

Is Your Infrastructure Affected by CVE-2024-26780?

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