CVE-2024-36938

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 5.5 under NVD CVSS v3. EPSS exploit probability: 0.2% (15th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3

Also known asEUVD-2024-36288 (ENISA EUVD)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:

bpf, skmsg: Fix NULL pointer dereference in sk_psock_skb_ingress_enqueue

Fix NULL pointer data-races in sk_psock_skb_ingress_enqueue() which syzbot reported [1].

[1] BUG: KCSAN: data-race in sk_psock_drop / sk_psock_skb_ingress_enqueue

write to 0xffff88814b3278b8 of 8 bytes by task 10724 on cpu 1: sk_psock_stop_verdict net/core/skmsg.c:1257 [inline] sk_psock_drop+0x13e/0x1f0 net/core/skmsg.c:843 sk_psock_put include/linux/skmsg.h:459 [inline] sock_map_close+0x1a7/0x260 net/core/sock_map.c:1648 unix_release+0x4b/0x80 net/unix/af_unix.c:1048 __sock_release net/socket.c:659 [inline] sock_close+0x68/0x150 net/socket.c:1421 __fput+0x2c1/0x660 fs/file_table.c:422 __fput_sync+0x44/0x60 fs/file_table.c:507 __do_sys_close fs/open.c:1556 [inline] __se_sys_close+0x101/0x1b0 fs/open.c:1541 __x64_sys_close+0x1f/0x30 fs/open.c:1541 do_syscall_64+0xd3/0x1d0 entry_SYSCALL_64_after_hwframe+0x6d/0x75

read to 0xffff88814b3278b8 of 8 bytes by task 10713 on cpu 0: sk_psock_data_ready include/linux/skmsg.h:464 [inline] sk_psock_skb_ingress_enqueue+0x32d/0x390 net/core/skmsg.c:555 sk_psock_skb_ingress_self+0x185/0x1e0 net/core/skmsg.c:606 sk_psock_verdict_apply net/core/skmsg.c:1008 [inline] sk_psock_verdict_recv+0x3e4/0x4a0 net/core/skmsg.c:1202 unix_read_skb net/unix/af_unix.c:2546 [inline] unix_stream_read_skb+0x9e/0xf0 net/unix/af_unix.c:2682 sk_psock_verdict_data_ready+0x77/0x220 net/core/skmsg.c:1223 unix_stream_sendmsg+0x527/0x860 net/unix/af_unix.c:2339 sock_sendmsg_nosec net/socket.c:730 [inline] __sock_sendmsg+0x140/0x180 net/socket.c:745 ____sys_sendmsg+0x312/0x410 net/socket.c:2584 ___sys_sendmsg net/socket.c:2638 [inline] __sys_sendmsg+0x1e9/0x280 net/socket.c:2667 __do_sys_sendmsg net/socket.c:2676 [inline] __se_sys_sendmsg net/socket.c:2674 [inline] __x64_sys_sendmsg+0x46/0x50 net/socket.c:2674 do_syscall_64+0xd3/0x1d0 entry_SYSCALL_64_after_hwframe+0x6d/0x75

value changed: 0xffffffff83d7feb0 -> 0x0000000000000000

Reported by Kernel Concurrency Sanitizer on: CPU: 0 PID: 10713 Comm: syz-executor.4 Tainted: G W 6.8.0-syzkaller-08951-gfe46a7dd189e #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/29/2024

Prior to this, commit 4cd12c6065df ("bpf, sockmap: Fix NULL pointer dereference in sk_psock_verdict_data_ready()") fixed one NULL pointer similarly due to no protection of saved_data_ready. Here is another different caller causing the same issue because of the same reason. So we should protect it with sk_callback_lock read lock because the writer side in the sk_psock_drop() uses "write_lock_bh(&sk->sk_callback_lock);".

To avoid errors that could happen in future, I move those two pairs of lock into the sk_psock_data_ready(), which is suggested by John Fastabend.

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
15th
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.NVD CVSS v3 · CVSS v3.0 or v3.1
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

May 30, 2024

Last Modified

November 21, 2024

References (6)

Vendor Advisories for CVE-2024-36938(1)

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

Patch Availability(20)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-oracle-64k (6.8.0-1010.10) @ noble2026-10-24ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1060.58) @ jammy2026-10-24ubuntu
ubuntulinux-tools-oem-24.04a (6.8.0-1010.10) @ noble2026-10-24ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1065.71~20.04.1) @ focal2026-10-24ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1070.68) @ jammy2026-10-24ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1065.61) @ jammy2026-10-24ubuntu
ubuntulinux-tools-raspi (6.8.0-1009.10) @ noble2026-10-24ubuntu
ubuntulinux-xilinx-zynqmp-tools-host (5.15.0-1035.39) @ jammy2026-10-24ubuntu
ubuntulinux-tools-aws-lts-20.04 (5.4.0.1136.133) @ focal2026-10-24ubuntu
ubuntulinux-tools-oracle-lts-20.04 (5.4.0.1135.128) @ focal2026-10-24ubuntu
ubuntulinux-tools-azure-lts-20.04 (5.4.0.1142.136) @ focal2026-10-24ubuntu
ubuntulinux-tools-iot (5.4.0.1045.43) @ focal2026-10-24ubuntu
ubuntulinux-tools-raspi-hwe-18.04-edge (5.4.0.1120.132~18.04.1) @ bionic2026-10-24ubuntu
ubuntulinux-tools-azure-edge (5.4.0.1142.149~18.04.1) @ bionic2026-10-24ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.8.0-40.40) @ noble2026-10-24ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (5.15.0.118.128~20.04.1) @ focal2026-10-24ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.118.128~20.04.1) @ focal2026-10-24ubuntu
ubuntulinux-virtual-hwe-18.04-edge (5.4.0.202.222~18.04.1) @ bionic2026-10-24ubuntu
ubuntulinux-tools-azure (6.8.0-1012.14) @ noble2026-10-24ubuntu
linuxKernel @ 5.10.223 (fixes >=4.20.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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (42 versions)
  • every version up to 5.10.223-1: fixed in 5.10.223-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.27-1 ... 6.1.94-1~bpo11+1 (23 versions)
  • every version up to 6.1.94-1: fixed in 6.1.94-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.8.11-1: fixed in 6.8.11-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.8.11-1: fixed in 6.8.11-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(19)

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 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 96 of 216 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. 4 repeat rows among the latest 100 are merged into the row they repeat. The 120 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-36938?
CVE-2024-36938 is a medium-severity vulnerability; its CVE record was published on May 30, 2024. In the Linux kernel, the following vulnerability has been resolved: bpf, skmsg: Fix NULL pointer dereference in sk_psock_skb_ingress_enqueue Fix NULL pointer data-races in sk_psock_skb_ingress_enqueue() which syzbot reported [1]. [1] BUG: KCSAN: data-race in sk_psock_drop /…
When was the CVE record for CVE-2024-36938 published?
The CVE record for CVE-2024-36938 was published on May 30, 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 November 21, 2024; the record at its source may have been updated since.
Is CVE-2024-36938 actively exploited?
CVE-2024-36938 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (15th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-36938?
CVE-2024-36938 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2024-36938?
A fix for CVE-2024-36938 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-36938 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2024-36938?

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

Book a Demo →Browse All CVEs