CVE-2021-47078

MEDIUMNVD 5.35.3
EchelonGraph scoreMEDIUM confidence

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

Score 5.3 from GitHub Security Advisory published 2024-03-02. NVD baseline CVSS 5.3; sources differ by 0.0.

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

Also known asEUVD-2021-33726 (ENISA EUVD) · GHSA-c56c-8vvg-gr68 (GitHub Security Advisories)Source: ENISA EUVD

5.3EG
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.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

RDMA/rxe: Clear all QP fields if creation failed

rxe_qp_do_cleanup() relies on valid pointer values in QP for the properly created ones, but in case rxe_qp_from_init() failed it was filled with garbage and caused tot the following error.

refcount_t: underflow; use-after-free. WARNING: CPU: 1 PID: 12560 at lib/refcount.c:28 refcount_warn_saturate+0x1d1/0x1e0 lib/refcount.c:28 Modules linked in: CPU: 1 PID: 12560 Comm: syz-executor.4 Not tainted 5.12.0-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 RIP: 0010:refcount_warn_saturate+0x1d1/0x1e0 lib/refcount.c:28 Code: e9 db fe ff ff 48 89 df e8 2c c2 ea fd e9 8a fe ff ff e8 72 6a a7 fd 48 c7 c7 e0 b2 c1 89 c6 05 dc 3a e6 09 01 e8 ee 74 fb 04 <0f> 0b e9 af fe ff ff 0f 1f 84 00 00 00 00 00 41 56 41 55 41 54 55 RSP: 0018:ffffc900097ceba8 EFLAGS: 00010286 RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000 RDX: 0000000000040000 RSI: ffffffff815bb075 RDI: fffff520012f9d67 RBP: 0000000000000003 R08: 0000000000000000 R09: 0000000000000000 R10: ffffffff815b4eae R11: 0000000000000000 R12: ffff8880322a4800 R13: ffff8880322a4940 R14: ffff888033044e00 R15: 0000000000000000 FS: 00007f6eb2be3700(0000) GS:ffff8880b9d00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fdbe5d41000 CR3: 000000001d181000 CR4: 00000000001506e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: __refcount_sub_and_test include/linux/refcount.h:283 [inline] __refcount_dec_and_test include/linux/refcount.h:315 [inline] refcount_dec_and_test include/linux/refcount.h:333 [inline] kref_put include/linux/kref.h:64 [inline] rxe_qp_do_cleanup+0x96f/0xaf0 drivers/infiniband/sw/rxe/rxe_qp.c:805 execute_in_process_context+0x37/0x150 kernel/workqueue.c:3327 rxe_elem_release+0x9f/0x180 drivers/infiniband/sw/rxe/rxe_pool.c:391 kref_put include/linux/kref.h:65 [inline] rxe_create_qp+0x2cd/0x310 drivers/infiniband/sw/rxe/rxe_verbs.c:425 _ib_create_qp drivers/infiniband/core/core_priv.h:331 [inline] ib_create_named_qp+0x2ad/0x1370 drivers/infiniband/core/verbs.c:1231 ib_create_qp include/rdma/ib_verbs.h:3644 [inline] create_mad_qp+0x177/0x2d0 drivers/infiniband/core/mad.c:2920 ib_mad_port_open drivers/infiniband/core/mad.c:3001 [inline] ib_mad_init_device+0xd6f/0x1400 drivers/infiniband/core/mad.c:3092 add_client_context+0x405/0x5e0 drivers/infiniband/core/device.c:717 enable_device_and_get+0x1cd/0x3b0 drivers/infiniband/core/device.c:1331 ib_register_device drivers/infiniband/core/device.c:1413 [inline] ib_register_device+0x7c7/0xa50 drivers/infiniband/core/device.c:1365 rxe_register_device+0x3d5/0x4a0 drivers/infiniband/sw/rxe/rxe_verbs.c:1147 rxe_add+0x12fe/0x16d0 drivers/infiniband/sw/rxe/rxe.c:247 rxe_net_add+0x8c/0xe0 drivers/infiniband/sw/rxe/rxe_net.c:503 rxe_newlink drivers/infiniband/sw/rxe/rxe.c:269 [inline] rxe_newlink+0xb7/0xe0 drivers/infiniband/sw/rxe/rxe.c:250 nldev_newlink+0x30e/0x550 drivers/infiniband/core/nldev.c:1555 rdma_nl_rcv_msg+0x36d/0x690 drivers/infiniband/core/netlink.c:195 rdma_nl_rcv_skb drivers/infiniband/core/netlink.c:239 [inline] rdma_nl_rcv+0x2ee/0x430 drivers/infiniband/core/netlink.c:259 netlink_unicast_kernel net/netlink/af_netlink.c:1312 [inline] netlink_unicast+0x533/0x7d0 net/netlink/af_netlink.c:1338 netlink_sendmsg+0x856/0xd90 net/netlink/af_netlink.c:1927 sock_sendmsg_nosec net/socket.c:654 [inline] sock_sendmsg+0xcf/0x120 net/socket.c:674 ____sys_sendmsg+0x6e8/0x810 net/socket.c:2350 ___sys_sendmsg+0xf3/0x170 net/socket.c:2404 __sys_sendmsg+0xe5/0x1b0 net/socket.c:2433 do_syscall_64+0x3a/0xb0 arch/x86/entry/common.c:47 entry_SYSCALL_64_after_hwframe+0 ---truncated---

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
24
EG Risk 24/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)
Severity53% × 45%
Impact severity (EG Severity): CVSS 5.3 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 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.3%
EPSS %ILE
20th
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.3): severity, escalated by confirmed exploitation. This CVE's 5.3 is its impact severity (EG Severity), not escalated.

EG Severity
5.3 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 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

March 1, 2024

Last Modified

August 5, 2026

References (7)

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.10.40-1: fixed in 5.10.40-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.10.40-1: fixed in 5.10.40-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.10.40-1: fixed in 5.10.40-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.10.40-1: fixed in 5.10.40-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 36× 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 211 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 114 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2021-47078?
CVE-2021-47078 is a medium-severity vulnerability; its CVE record was published on March 1, 2024. In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Clear all QP fields if creation failed rxe_qp_do_cleanup() relies on valid pointer values in QP for the properly created ones, but in case rxe_qp_from_init() failed it was filled with garbage and caused tot the following…
When was the CVE record for CVE-2021-47078 published?
The CVE record for CVE-2021-47078 was published on March 1, 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 August 5, 2026; the record at its source may have been updated since.
Is CVE-2021-47078 actively exploited?
CVE-2021-47078 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (20th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2021-47078?
CVE-2021-47078 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2021-47078?
A fix for CVE-2021-47078 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-2021-47078

Explore →

Is Your Infrastructure Affected by CVE-2021-47078?

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

Book a Demo →Browse All CVEs