CVE-2024-56633

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2024-12-27. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week
7.8EG
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.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

tcp_bpf: Fix the sk_mem_uncharge logic in tcp_bpf_sendmsg

The current sk memory accounting logic in __SK_REDIRECT is pre-uncharging tosend bytes, which is either msg->sg.size or a smaller value apply_bytes.

Potential problems with this strategy are as follows:

  • If the actual sent bytes are smaller than tosend, we need to charge some
bytes back, as in line 487, which is okay but seems not clean.
  • When tosend is set to apply_bytes, as in line 417, and (ret < 0), we may
miss uncharging (msg->sg.size - apply_bytes) bytes.

[...] 415 tosend = msg->sg.size; 416 if (psock->apply_bytes && psock->apply_bytes < tosend) 417 tosend = psock->apply_bytes; [...] 443 sk_msg_return(sk, msg, tosend); 444 release_sock(sk); 446 origsize = msg->sg.size; 447 ret = tcp_bpf_sendmsg_redir(sk_redir, redir_ingress, 448 msg, tosend, flags); 449 sent = origsize - msg->sg.size; [...] 454 lock_sock(sk); 455 if (unlikely(ret < 0)) { 456 int free = sk_msg_free_nocharge(sk, msg); 458 if (!cork) 459 *copied -= free; 460 } [...] 487 if (eval == __SK_REDIRECT) 488 sk_mem_charge(sk, tosend - sent); [...]

When running the selftest test_txmsg_redir_wait_sndmem with txmsg_apply, the following warning will be reported:

------------[ cut here ]------------ WARNING: CPU: 6 PID: 57 at net/ipv4/af_inet.c:156 inet_sock_destruct+0x190/0x1a0 Modules linked in: CPU: 6 UID: 0 PID: 57 Comm: kworker/6:0 Not tainted 6.12.0-rc1.bm.1-amd64+ #43 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014 Workqueue: events sk_psock_destroy RIP: 0010:inet_sock_destruct+0x190/0x1a0 RSP: 0018:ffffad0a8021fe08 EFLAGS: 00010206 RAX: 0000000000000011 RBX: ffff9aab4475b900 RCX: ffff9aab481a0800 RDX: 0000000000000303 RSI: 0000000000000011 RDI: ffff9aab4475b900 RBP: ffff9aab4475b990 R08: 0000000000000000 R09: ffff9aab40050ec0 R10: 0000000000000000 R11: ffff9aae6fdb1d01 R12: ffff9aab49c60400 R13: ffff9aab49c60598 R14: ffff9aab49c60598 R15: dead000000000100 FS: 0000000000000000(0000) GS:ffff9aae6fd80000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007ffec7e47bd8 CR3: 00000001a1a1c004 CR4: 0000000000770ef0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 PKRU: 55555554 Call Trace:

? __warn+0x89/0x130 ? inet_sock_destruct+0x190/0x1a0 ? report_bug+0xfc/0x1e0 ? handle_bug+0x5c/0xa0 ? exc_invalid_op+0x17/0x70 ? asm_exc_invalid_op+0x1a/0x20 ? inet_sock_destruct+0x190/0x1a0 __sk_destruct+0x25/0x220 sk_psock_destroy+0x2b2/0x310 process_scheduled_works+0xa3/0x3e0 worker_thread+0x117/0x240 ? __pfx_worker_thread+0x10/0x10 kthread+0xcf/0x100 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x31/0x40 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30

---[ end trace 0000000000000000 ]---

In __SK_REDIRECT, a more concise way is delaying the uncharging after sent bytes are finalized, and uncharge this value. When (ret < 0), we shall invoke sk_msg_free.

Same thing happens in case __SK_DROP, when tosend is set to apply_bytes, we may miss uncharging (msg->sg.size - apply_bytes) bytes. The same warning will be reported in selftest.

[...] 468 case __SK_DROP: 469 default: 470 sk_msg_free_partial(sk, msg, tosend); 471 sk_msg_apply_bytes(psock, tosend); 472 *copied -= (tosend + delta); 473 return -EACCES; [...]

So instead of sk_msg_free_partial we can do sk_msg_free here.

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

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 (value × EchelonGraph’s weight)
Severity78% × 45%
The EG Score, 7.8 of 10.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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
19th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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

December 27, 2024

Last Modified

November 3, 2025

Advisory Details (9)

Auto-updated Oct 12, 2026
Patch available.
Web pageMentions a patch (unverified)

[SECURITY] [DLA 4075-1] linux security update

https://lists.debian.org/debian-lts-announce/2025/03/msg00002.html
Web pageMentions a patch (unverified)

[SECURITY] [DLA 4076-1] linux-6.1 security update

https://lists.debian.org/debian-lts-announce/2025/03/msg00001.html
Web page

tcp_bpf: Fix the sk_mem_uncharge logic in tcp_bpf_sendmsg - kernel/git/stable/linux.git - Linux kernel stable tree

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

tcp_bpf: Fix the sk_mem_uncharge logic in tcp_bpf_sendmsg - kernel/git/stable/linux.git - Linux kernel stable tree

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

tcp_bpf: Fix the sk_mem_uncharge logic in tcp_bpf_sendmsg - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/905d82e6e77d16ec3e089c92b7b59a14899dfc1a
Web page

tcp_bpf: Fix the sk_mem_uncharge logic in tcp_bpf_sendmsg - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5c9e3bb43a354a2245caebbbbb4a5b8c034fdd56
Web page

tcp_bpf: Fix the sk_mem_uncharge logic in tcp_bpf_sendmsg - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/456f08d24afa51b5eb816c42e4ca1c44a247bd42
Web page

tcp_bpf: Fix the sk_mem_uncharge logic in tcp_bpf_sendmsg - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/206d56f41a1509cadd06e2178c26cb830e45057d
Web page

tcp_bpf: Fix the sk_mem_uncharge logic in tcp_bpf_sendmsg - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0d6cd1151e26fc7c2d5daa85e8984aaa685a1a12

Vendor Advisories for CVE-2024-56633(1)

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

Patch Availability(31)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-virtual-hwe-24.04-edge (6.11.0-21.21) @ oracular2026-05-23ubuntu
ubuntulinux-tools-gcp-fips (5.15.0.1079.69) @ jammy2026-05-23ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.135.133) @ jammy2026-05-23ubuntu
ubuntulinux-tools-oracle-edge (5.4.0.1140.149~18.04.1) @ bionic2026-05-23ubuntu
ubuntulinux-xilinx-zynqmp-tools-host (5.15.0-1044.48) @ jammy2026-05-23ubuntu
ubuntulinux-virtual-hwe-18.04-edge (5.4.0.211.206) @ focal2026-05-23ubuntu
ubuntulinux-tools-lowlatency-64k (6.11.0-1011.12) @ oracular2026-05-23ubuntu
ubuntulinux-tools-lowlatency-hwe-24.04-edge (6.11.0-1011.12~24.04.1) @ noble2026-05-23ubuntu
ubuntulinux-tools-nvidia-tegra-rt (5.15.0.1033.33) @ jammy2026-05-23ubuntu
ubuntulinux-tools-realtime (5.15.0.1080.83) @ jammy2026-05-23ubuntu
ubuntulinux-tools-kvm (5.15.0.1076.72) @ jammy2026-05-23ubuntu
ubuntulinux-tools-fips (5.4.0.1116.113) @ focal2026-05-23ubuntu
ubuntulinux-tools-oem-24.04b (6.11.0-1017.17) @ noble2026-05-23ubuntu
ubuntulinux-tools-aws-edge (5.4.0.1142.152~18.04.1) @ bionic2026-05-23ubuntu
ubuntulinux-tools-aws-lts-20.04 (5.4.0.1142.139) @ focal2026-05-23ubuntu
ubuntulinux-tools-aws-fips (5.4.0.1142.89) @ focal2026-05-23ubuntu
ubuntulinux-tools-aws-edge (6.8.0-1027.29~22.04.1) @ jammy2026-05-23ubuntu
ubuntulinux-tools-gcp-fips (5.4.0.1145.87) @ focal2026-05-23ubuntu
ubuntulinux-tools-raspi (6.11.0-1010.10) @ oracular2026-05-23ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.136.147~20.04.1) @ focal2026-05-23ubuntu
ubuntulinux-tools-gcp-edge (6.8.0-1028.30~22.04.1) @ jammy2026-05-23ubuntu
ubuntulinux-tools-iot (5.4.0.1048.46) @ focal2026-05-23ubuntu
ubuntulinux-tools-ibm-edge (5.15.0.1074.77~20.04.1) @ focal2026-05-23ubuntu
ubuntulinux-tools-realtime-hwe-24.04 (6.8.1-1020.21) @ noble2026-05-23ubuntu
ubuntulinux-tools-azure-fde-edge (5.15.0.1086.95~20.04.1.61) @ focal2026-05-23ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1024.25~22.04.1) @ jammy2026-05-23ubuntu
ubuntulinux-tools-intel-iotg-edge (5.15.0.1077.83~20.04.1) @ focal2026-05-23ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-58.60~22.04.1) @ jammy2026-05-23ubuntu
ubuntulinux-tools-ibm-edge (5.4.0.1090.95~18.04.1) @ bionic2026-05-23ubuntu
redhatkernel-0:6.12.0-211.7.1.el10_22026-05-19redhat
linuxKernel @ 5.4.287 (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

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (44 versions)
  • every version up to 5.10.234-1: fixed in 5.10.234-1
—
linux-6.16.1.106-3~deb11u1, 6.1.106-3~deb11u2, 6.1.106-3~deb11u3, 6.1.112-1~deb11u1, 6.1.119-1~deb11u1
  • every version up to 6.1.128-1~deb11u1: fixed in 6.1.128-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (32 versions)
  • every version up to 6.1.123-1: fixed in 6.1.123-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.5-1: fixed in 6.12.5-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.5-1: fixed in 6.12.5-1
—

Additional Vendor Advisories

(24)

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 11× in last 7d / 30× 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 89 of 178 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. 11 repeat rows among the latest 100 are merged into the row they repeat. The 89 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2024-56633?
CVE-2024-56633 is a high-severity vulnerability; its CVE record was published on December 27, 2024. In the Linux kernel, the following vulnerability has been resolved: tcpbpf: Fix the skmemuncharge logic in tcpbpf_sendmsg The current sk memory accounting logic in SK_REDIRECT is pre-uncharging tosend bytes, which is either msg->sg.size or a smaller value apply_bytes. Potential problems with this…
When was the CVE record for CVE-2024-56633 published?
The CVE record for CVE-2024-56633 was published on December 27, 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 3, 2025; the record at its source may have been updated since.
Is CVE-2024-56633 actively exploited?
CVE-2024-56633 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (19th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-56633?
CVE-2024-56633 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2024-56633?
A fix for CVE-2024-56633 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-56633 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-56633

Explore →

Is Your Infrastructure Affected by CVE-2024-56633?

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

Book a Demo →Browse All CVEs