CVE-2021-47103

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 5 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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

inet: fully convert sk->sk_rx_dst to RCU rules

syzbot reported various issues around early demux, one being included in this changelog [1]

sk->sk_rx_dst is using RCU protection without clearly documenting it.

And following sequences in tcp_v4_do_rcv()/tcp_v6_do_rcv() are not following standard RCU rules.

[a] dst_release(dst); [b] sk->sk_rx_dst = NULL;

They look wrong because a delete operation of RCU protected pointer is supposed to clear the pointer before the call_rcu()/synchronize_rcu() guarding actual memory freeing.

In some cases indeed, dst could be freed before [b] is done.

We could cheat by clearing sk_rx_dst before calling dst_release(), but this seems the right time to stick to standard RCU annotations and debugging facilities.

[1] BUG: KASAN: use-after-free in dst_check include/net/dst.h:470 [inline] BUG: KASAN: use-after-free in tcp_v4_early_demux+0x95b/0x960 net/ipv4/tcp_ipv4.c:1792 Read of size 2 at addr ffff88807f1cb73a by task syz-executor.5/9204

CPU: 0 PID: 9204 Comm: syz-executor.5 Not tainted 5.16.0-rc5-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106 print_address_description.constprop.0.cold+0x8d/0x320 mm/kasan/report.c:247 __kasan_report mm/kasan/report.c:433 [inline] kasan_report.cold+0x83/0xdf mm/kasan/report.c:450 dst_check include/net/dst.h:470 [inline] tcp_v4_early_demux+0x95b/0x960 net/ipv4/tcp_ipv4.c:1792 ip_rcv_finish_core.constprop.0+0x15de/0x1e80 net/ipv4/ip_input.c:340 ip_list_rcv_finish.constprop.0+0x1b2/0x6e0 net/ipv4/ip_input.c:583 ip_sublist_rcv net/ipv4/ip_input.c:609 [inline] ip_list_rcv+0x34e/0x490 net/ipv4/ip_input.c:644 __netif_receive_skb_list_ptype net/core/dev.c:5508 [inline] __netif_receive_skb_list_core+0x549/0x8e0 net/core/dev.c:5556 __netif_receive_skb_list net/core/dev.c:5608 [inline] netif_receive_skb_list_internal+0x75e/0xd80 net/core/dev.c:5699 gro_normal_list net/core/dev.c:5853 [inline] gro_normal_list net/core/dev.c:5849 [inline] napi_complete_done+0x1f1/0x880 net/core/dev.c:6590 virtqueue_napi_complete drivers/net/virtio_net.c:339 [inline] virtnet_poll+0xca2/0x11b0 drivers/net/virtio_net.c:1557 __napi_poll+0xaf/0x440 net/core/dev.c:7023 napi_poll net/core/dev.c:7090 [inline] net_rx_action+0x801/0xb40 net/core/dev.c:7177 __do_softirq+0x29b/0x9c2 kernel/softirq.c:558 invoke_softirq kernel/softirq.c:432 [inline] __irq_exit_rcu+0x123/0x180 kernel/softirq.c:637 irq_exit_rcu+0x5/0x20 kernel/softirq.c:649 common_interrupt+0x52/0xc0 arch/x86/kernel/irq.c:240 asm_common_interrupt+0x1e/0x40 arch/x86/include/asm/idtentry.h:629 RIP: 0033:0x7f5e972bfd57 Code: 39 d1 73 14 0f 1f 80 00 00 00 00 48 8b 50 f8 48 83 e8 08 48 39 ca 77 f3 48 39 c3 73 3e 48 89 13 48 8b 50 f8 48 89 38 49 8b 0e <48> 8b 3e 48 83 c3 08 48 83 c6 08 eb bc 48 39 d1 72 9e 48 39 d0 73 RSP: 002b:00007fff8a413210 EFLAGS: 00000283 RAX: 00007f5e97108990 RBX: 00007f5e97108338 RCX: ffffffff81d3aa45 RDX: ffffffff81d3aa45 RSI: 00007f5e97108340 RDI: ffffffff81d3aa45 RBP: 00007f5e97107eb8 R08: 00007f5e97108d88 R09: 0000000093c2e8d9 R10: 0000000000000000 R11: 0000000000000000 R12: 00007f5e97107eb0 R13: 00007f5e97108338 R14: 00007f5e97107ea8 R15: 0000000000000019

Allocated by task 13: kasan_save_stack+0x1e/0x50 mm/kasan/common.c:38 kasan_set_track mm/kasan/common.c:46 [inline] set_alloc_info mm/kasan/common.c:434 [inline] __kasan_slab_alloc+0x90/0xc0 mm/kasan/common.c:467 kasan_slab_alloc include/linux/kasan.h:259 [inline] slab_post_alloc_hook mm/slab.h:519 [inline] slab_alloc_node mm/slub.c:3234 [inline] slab_alloc mm/slub.c:3242 [inline] kmem_cache_alloc+0x202/0x3a0 mm/slub.c:3247 dst_alloc+0x146/0x1f0 net/core/dst.c:92 rt_dst_alloc+0x73/0x430 net/ipv4/route.c:1613 ip_route_input_slow+0x1817/0x3a20 net/ipv4/route.c:234 ---truncated---

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
35(Track)
EG Risk 35/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
Severity78% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
58%
KEV
Not listed

Published

March 4, 2024

Last Modified

August 5, 2026

Advisory Details (7)

Auto-updated Aug 4, 2026
No patch confirmed yet.
generic

inet: fully convert sk->sk_rx_dst to RCU rules - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/75a578000ae5e511e5d0e8433c94a14d9c99c412
generic

inet: fully convert sk->sk_rx_dst to RCU rules - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/68c34ce11ef23328692aa35fa6aaafdd75913100
generic

inet: fully convert sk->sk_rx_dst to RCU rules - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0249a4b8a554f2eb6a27b62516fa50168584faa4
generic

inet: fully convert sk->sk_rx_dst to RCU rules - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f039b43cbaea5e0700980c2f0052da05a70782e0
generic

inet: fully convert sk->sk_rx_dst to RCU rules - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c3bb4a7e8cbc984e1cdac0fe6af60e880214ed6e
generic

inet: fully convert sk->sk_rx_dst to RCU rules - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/92e6e36ecd16808866ac6172b9491b5097cde449
generic

inet: fully convert sk->sk_rx_dst to RCU rules - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8f905c0e7354ef261360fb7535ea079b1082c105

Vendor Advisories for CVE-2021-47103(2)

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

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-lts-xenial (4.4.0.266.272) @ xenial2026-05-24ubuntu
ubuntulinux-tools-kvm (4.4.0.1142.139) @ xenial2026-05-24ubuntu
ubuntulinux-virtual-lts-xenial (4.4.0.266.300~14.04.1) @ trusty2026-05-24ubuntu
redhatkernel-0:5.14.0-162.6.1.el9_12022-11-15redhat
redhatkernel-0:4.18.0-425.3.1.el82022-11-08redhat

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.

Weakness Classification(1)

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

Additional Vendor Advisories

(3)

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

Frequently asked(5)

What is CVE-2021-47103?
CVE-2021-47103 is a high vulnerability published on March 4, 2024. In the Linux kernel, the following vulnerability has been resolved: inet: fully convert sk->skrxdst to RCU rules syzbot reported various issues around early demux, one being included in this changelog [1] sk->skrxdst is using RCU protection without clearly documenting it. And following sequences in…
When was CVE-2021-47103 disclosed?
CVE-2021-47103 was first published in the National Vulnerability Database on March 4, 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-47103 actively exploited?
CVE-2021-47103 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 42.0% of all scored CVEs.
What is the CVSS score of CVE-2021-47103?
CVE-2021-47103 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2021-47103?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2021-47103, 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-47103

Explore →

Is Your Infrastructure Affected by CVE-2021-47103?

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