CVE-2021-47419

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
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

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

net/sched: sch_taprio: properly cancel timer from taprio_destroy()

There is a comment in qdisc_create() about us not calling ops->reset() in some cases.

err_out4: /* * Any broken qdiscs that would require a ops->reset() here? * The qdisc was never in action so it shouldn't be necessary. */

As taprio sets a timer before actually receiving a packet, we need to cancel it from ops->destroy, just in case ops->reset has not been called.

syzbot reported:

ODEBUG: free active (active state 0) object type: hrtimer hint: advance_sched+0x0/0x9a0 arch/x86/include/asm/atomic64_64.h:22 WARNING: CPU: 0 PID: 8441 at lib/debugobjects.c:505 debug_print_object+0x16e/0x250 lib/debugobjects.c:505 Modules linked in: CPU: 0 PID: 8441 Comm: syz-executor813 Not tainted 5.14.0-rc6-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 RIP: 0010:debug_print_object+0x16e/0x250 lib/debugobjects.c:505 Code: ff df 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 af 00 00 00 48 8b 14 dd e0 d3 e3 89 4c 89 ee 48 c7 c7 e0 c7 e3 89 e8 5b 86 11 05 <0f> 0b 83 05 85 03 92 09 01 48 83 c4 18 5b 5d 41 5c 41 5d 41 5e c3 RSP: 0018:ffffc9000130f330 EFLAGS: 00010282 RAX: 0000000000000000 RBX: 0000000000000003 RCX: 0000000000000000 RDX: ffff88802baeb880 RSI: ffffffff815d87b5 RDI: fffff52000261e58 RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000000 R10: ffffffff815d25ee R11: 0000000000000000 R12: ffffffff898dd020 R13: ffffffff89e3ce20 R14: ffffffff81653630 R15: dffffc0000000000 FS: 0000000000f0d300(0000) GS:ffff8880b9d00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007ffb64b3e000 CR3: 0000000036557000 CR4: 00000000001506e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: __debug_check_no_obj_freed lib/debugobjects.c:987 [inline] debug_check_no_obj_freed+0x301/0x420 lib/debugobjects.c:1018 slab_free_hook mm/slub.c:1603 [inline] slab_free_freelist_hook+0x171/0x240 mm/slub.c:1653 slab_free mm/slub.c:3213 [inline] kfree+0xe4/0x540 mm/slub.c:4267 qdisc_create+0xbcf/0x1320 net/sched/sch_api.c:1299 tc_modify_qdisc+0x4c8/0x1a60 net/sched/sch_api.c:1663 rtnetlink_rcv_msg+0x413/0xb80 net/core/rtnetlink.c:5571 netlink_rcv_skb+0x153/0x420 net/netlink/af_netlink.c:2504 netlink_unicast_kernel net/netlink/af_netlink.c:1314 [inline] netlink_unicast+0x533/0x7d0 net/netlink/af_netlink.c:1340 netlink_sendmsg+0x86d/0xdb0 net/netlink/af_netlink.c:1929 sock_sendmsg_nosec net/socket.c:704 [inline] sock_sendmsg+0xcf/0x120 net/socket.c:724 ____sys_sendmsg+0x6e8/0x810 net/socket.c:2403 ___sys_sendmsg+0xf3/0x170 net/socket.c:2457 __sys_sendmsg+0xe5/0x1b0 net/socket.c:2486 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80

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
14%
KEV
Not listed

Published

May 21, 2024

Last Modified

August 5, 2026

References (4)

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2021-47419?
CVE-2021-47419 is a medium vulnerability published on May 21, 2024. In the Linux kernel, the following vulnerability has been resolved: net/sched: schtaprio: properly cancel timer from tapriodestroy() There is a comment in qdisc_create() about us not calling ops->reset() in some cases. err_out4: /* Any broken qdiscs that would require a ops->reset() here? The qdisc…
When was CVE-2021-47419 disclosed?
CVE-2021-47419 was first published in the National Vulnerability Database on May 21, 2024, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2021-47419 actively exploited?
CVE-2021-47419 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 86.0% of all scored CVEs.
What is the CVSS score of CVE-2021-47419?
CVE-2021-47419 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2021-47419?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2021-47419, 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-2021-47419

Explore →

Is Your Infrastructure Affected by CVE-2021-47419?

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

Start Free Scan →Browse All CVEs