CVE-2024-57996

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 2025-02-27. 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-2025-5254 (ENISA EUVD) · GHSA-25pp-pjqx-3f66 (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.3%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

net_sched: sch_sfq: don't allow 1 packet limit

The current implementation does not work correctly with a limit of

  • iproute2 actually checks for this and this patch adds the check in
kernel as well.

This fixes the following syzkaller reported crash:

UBSAN: array-index-out-of-bounds in net/sched/sch_sfq.c:210:6 index 65535 is out of range for type 'struct sfq_head[128]' CPU: 0 PID: 2569 Comm: syz-executor101 Not tainted 5.10.0-smp-DEV #1 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024 Call Trace: __dump_stack lib/dump_stack.c:79 [inline] dump_stack+0x125/0x19f lib/dump_stack.c:120 ubsan_epilogue lib/ubsan.c:148 [inline] __ubsan_handle_out_of_bounds+0xed/0x120 lib/ubsan.c:347 sfq_link net/sched/sch_sfq.c:210 [inline] sfq_dec+0x528/0x600 net/sched/sch_sfq.c:238 sfq_dequeue+0x39b/0x9d0 net/sched/sch_sfq.c:500 sfq_reset+0x13/0x50 net/sched/sch_sfq.c:525 qdisc_reset+0xfe/0x510 net/sched/sch_generic.c:1026 tbf_reset+0x3d/0x100 net/sched/sch_tbf.c:319 qdisc_reset+0xfe/0x510 net/sched/sch_generic.c:1026 dev_reset_queue+0x8c/0x140 net/sched/sch_generic.c:1296 netdev_for_each_tx_queue include/linux/netdevice.h:2350 [inline] dev_deactivate_many+0x6dc/0xc20 net/sched/sch_generic.c:1362 __dev_close_many+0x214/0x350 net/core/dev.c:1468 dev_close_many+0x207/0x510 net/core/dev.c:1506 unregister_netdevice_many+0x40f/0x16b0 net/core/dev.c:10738 unregister_netdevice_queue+0x2be/0x310 net/core/dev.c:10695 unregister_netdevice include/linux/netdevice.h:2893 [inline] __tun_detach+0x6b6/0x1600 drivers/net/tun.c:689 tun_detach drivers/net/tun.c:705 [inline] tun_chr_close+0x104/0x1b0 drivers/net/tun.c:3640 __fput+0x203/0x840 fs/file_table.c:280 task_work_run+0x129/0x1b0 kernel/task_work.c:185 exit_task_work include/linux/task_work.h:33 [inline] do_exit+0x5ce/0x2200 kernel/exit.c:931 do_group_exit+0x144/0x310 kernel/exit.c:1046 __do_sys_exit_group kernel/exit.c:1057 [inline] __se_sys_exit_group kernel/exit.c:1055 [inline] __x64_sys_exit_group+0x3b/0x40 kernel/exit.c:1055 do_syscall_64+0x6c/0xd0 entry_SYSCALL_64_after_hwframe+0x61/0xcb RIP: 0033:0x7fe5e7b52479 Code: Unable to access opcode bytes at RIP 0x7fe5e7b5244f. RSP: 002b:00007ffd3c800398 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7 RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fe5e7b52479 RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000000 RBP: 00007fe5e7bcd2d0 R08: ffffffffffffffb8 R09: 0000000000000014 R10: 0000000000000000 R11: 0000000000000246 R12: 00007fe5e7bcd2d0 R13: 0000000000000000 R14: 00007fe5e7bcdd20 R15: 00007fe5e7b24270

The crash can be also be reproduced with the following (with a tc recompiled to allow for sfq limits of 1):

tc qdisc add dev dummy0 handle 1: root tbf rate 1Kbit burst 100b lat 1s ../iproute2-6.9.0/tc/tc qdisc add dev dummy0 handle 2: parent 1:10 sfq limit 1 ifconfig dummy0 up ping -I dummy0 -f -c2 -W0.1 8.8.8.8 sleep 1

Scenario that triggers the crash:

* the first packet is sent and queued in TBF and SFQ; qdisc qlen is 1

* TBF dequeues: it peeks from SFQ which moves the packet to the gso_skb list and keeps qdisc qlen set to 1. TBF is out of tokens so it schedules itself for later.

* the second packet is sent and TBF tries to queues it to SFQ. qdisc qlen is now 2 and because the SFQ limit is 1 the packet is dropped by SFQ. At this point qlen is 1, and all of the SFQ slots are empty, however q->tail is not NULL.

At this point, assuming no more packets are queued, when sch_dequeue runs again it will decrement the qlen for the current empty slot causing an underflow and the subsequent out of bounds access.

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

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.3% 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 low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 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 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.

The score's inputs: 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

February 27, 2025

Last Modified

October 15, 2026

Advisory Details (8)

Auto-updated Aug 5, 2026
Patch available.
Web page

net_sched: sch_sfq: don't allow 1 packet limit - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/10685681bafce6febb39770f3387621bf5d67d0b
Web page

net_sched: sch_sfq: don't allow 1 packet limit - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7fefc294204f10a3405f175f4ac2be16d63f135e
Web page

net_sched: sch_sfq: don't allow 1 packet limit - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7d8947f2153ee9c5ab4cb17861a11cc45f30e8c4
Web page

net_sched: sch_sfq: don't allow 1 packet limit - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/833e9a1c27b82024db7ff5038a51651f48f05e5e
Web page

net_sched: sch_sfq: don't allow 1 packet limit - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/35d0137305ae2f97260a9047f445bd4434bd6cc7
Web page

net_sched: sch_sfq: don't allow 1 packet limit - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1b562b7f9231432da40d12e19786c1bd7df653a7
Web page

net_sched: sch_sfq: don't allow 1 packet limit - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1e6d9d87626cf89eeffb4d943db12cb5b10bf961
Web page

net_sched: sch_sfq: don't allow 1 packet limit - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e12f6013d0a69660e8b99bfe381b9546ae667328

Vendor Advisories for CVE-2024-57996(2)

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-tools-realtime-6.8.1 (6.8.1-1031.32) @ noble2026-10-15ubuntu
ubuntulinux-tools-gcp-fips-5.4 (5.4.0.1153.95) @ focal2026-10-15ubuntu
ubuntulinux-tools-oracle-lts-20.04 (5.4.0.1149.143) @ focal2026-10-15ubuntu
ubuntulinux-tools-azure-fips-5.4 (5.4.0.1155.92) @ focal2026-10-15ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.11.0-26.26) @ oracular2026-10-15ubuntu
ubuntulinux-tools-oracle-64k (6.11.0-1016.17) @ oracular2026-10-15ubuntu
ubuntulinux-tools-aws (6.11.0-1014.15) @ oracular2026-10-15ubuntu
ubuntulinux-tools-gcp-fips-5.15 (5.15.0.1091.81) @ jammy2026-10-15ubuntu
ubuntulinux-virtual-6.8 (6.8.0-64.67) @ noble2026-10-15ubuntu
ubuntulinux-tools-gcp-lts-24.04 (6.8.0-1033.35) @ noble2026-10-15ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1025.26) @ noble2026-10-15ubuntu
ubuntulinux-tools-realtime-5.15 (5.15.0.1091.95) @ jammy2026-10-15ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1033.34~22.04.1) @ jammy2026-10-15ubuntu
ubuntulinux-virtual-lts-xenial (4.4.0.272.278) @ xenial2026-10-15ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-64.67~22.04.1) @ jammy2026-10-15ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-64.67.1) @ noble2026-10-15ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2026.27) @ noble2026-10-15ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1029.30) @ noble2026-10-15ubuntu
ubuntulinux-tools-raspi-6.8 (6.8.0-1031.35) @ noble2026-10-15ubuntu
ubuntulinux-tools-fips (4.4.0.1117.118) @ xenial2026-10-15ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1055 (5.15.0-1055.59) @ jammy2026-10-15ubuntu
ubuntulinux-tools-aws (4.4.0.1185.189) @ xenial2026-10-15ubuntu
ubuntulinux-tools-kvm-5.15 (5.15.0.1087.83) @ jammy2026-10-15ubuntu
ubuntulinux-tools-raspi-6.8 (6.8.0-1036.40) @ noble2026-10-15ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.4.0-1068 (5.4.0-1068.72) @ focal2026-10-15ubuntu
ubuntulinux-tools-azure (4.15.0.1192.207~14.04.1) @ trusty2026-10-15ubuntu
ubuntulinux-tools-gcp-fips-4.15 (4.15.0.2085.83) @ bionic2026-10-15ubuntu
ubuntulinux-tools-azure-edge (5.15.0.1095.104~20.04.1) @ focal2026-10-15ubuntu
ubuntulinux-tools-aws-fips-4.15 (4.15.0.2122.116) @ bionic2026-10-15ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1090.96~20.04.1) @ focal2026-10-15ubuntu
linuxKernel @ 5.4.297 (fixes >=2.6.12)—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 (46 versions)
  • every version up to 5.10.244-1: fixed in 5.10.244-1
—
linux-6.16.1.106-3~deb11u1 ... 6.1.128-1~deb11u1 (6 versions)
  • every version up to 6.1.129-1~deb11u1: fixed in 6.1.129-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (35 versions)
  • every version up to 6.1.129-1: fixed in 6.1.129-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.13-1: fixed in 6.12.13-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.13-1: fixed in 6.12.13-1
—

Weakness Classification(1)

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

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-57996?
CVE-2024-57996 is a medium-severity vulnerability; its CVE record was published on February 27, 2025. In the Linux kernel, the following vulnerability has been resolved: net_sched: sch_sfq: don't allow 1 packet limit The current implementation does not work correctly with a limit of 1. iproute2 actually checks for this and this patch adds the check in kernel as well. This fixes the following…
When was the CVE record for CVE-2024-57996 published?
The CVE record for CVE-2024-57996 was published on February 27, 2025. 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 October 15, 2026; the record at its source may have been updated since.
Is CVE-2024-57996 actively exploited?
CVE-2024-57996 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-57996?
CVE-2024-57996 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2024-57996?
A fix for CVE-2024-57996 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-57996 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-57996

Explore →

Is Your Infrastructure Affected by CVE-2024-57996?

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

Book a Demo →Browse All CVEs