CVE-2022-50073

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2025-06-18. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
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

A fix is available — apply it.

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

net: tap: NULL pointer derefence in dev_parse_header_protocol when skb->dev is null

Fixes a NULL pointer derefence bug triggered from tap driver. When tap_get_user calls virtio_net_hdr_to_skb the skb->dev is null (in tap.c skb->dev is set after the call to virtio_net_hdr_to_skb) virtio_net_hdr_to_skb calls dev_parse_header_protocol which needs skb->dev field to be valid.

The line that trigers the bug is in dev_parse_header_protocol (dev is at offset 0x10 from skb and is stored in RAX register) if (!dev->header_ops || !dev->header_ops->parse_protocol) 22e1: mov 0x10(%rbx),%rax 22e5: mov 0x230(%rax),%rax

Setting skb->dev before the call in tap.c fixes the issue.

BUG: kernel NULL pointer dereference, address: 0000000000000230 RIP: 0010:virtio_net_hdr_to_skb.constprop.0+0x335/0x410 [tap] Code: c0 0f 85 b7 fd ff ff eb d4 41 39 c6 77 cf 29 c6 48 89 df 44 01 f6 e8 7a 79 83 c1 48 85 c0 0f 85 d9 fd ff ff eb b7 48 8b 43 10 <48> 8b 80 30 02 00 00 48 85 c0 74 55 48 8b 40 28 48 85 c0 74 4c 48 RSP: 0018:ffffc90005c27c38 EFLAGS: 00010246 RAX: 0000000000000000 RBX: ffff888298f25300 RCX: 0000000000000010 RDX: 0000000000000005 RSI: ffffc90005c27cb6 RDI: ffff888298f25300 RBP: ffffc90005c27c80 R08: 00000000ffffffea R09: 00000000000007e8 R10: ffff88858ec77458 R11: 0000000000000000 R12: 0000000000000001 R13: 0000000000000014 R14: ffffc90005c27e08 R15: ffffc90005c27cb6 FS: 0000000000000000(0000) GS:ffff88858ec40000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000230 CR3: 0000000281408006 CR4: 00000000003706e0 Call Trace: tap_get_user+0x3f1/0x540 [tap] tap_sendmsg+0x56/0x362 [tap] ? get_tx_bufs+0xc2/0x1e0 [vhost_net] handle_tx_copy+0x114/0x670 [vhost_net] handle_tx+0xb0/0xe0 [vhost_net] handle_tx_kick+0x15/0x20 [vhost_net] vhost_worker+0x7b/0xc0 [vhost] ? vhost_vring_call_reset+0x40/0x40 [vhost] kthread+0xfa/0x120 ? kthread_complete_and_exit+0x20/0x20 ret_from_fork+0x1f/0x30

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/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%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
9%
KEV
Not listed

Published

June 18, 2025

Last Modified

August 12, 2026

Advisory Details (4)

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

net: tap: NULL pointer derefence in dev_parse_header_protocol when skb->dev is null - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4f61f133f354853bc394ec7d6028adb9b02dd701
generic

net: tap: NULL pointer derefence in dev_parse_header_protocol when skb->dev is null - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: tap: NULL pointer derefence in dev_parse_header_protocol when skb->dev is null - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/447ba770cfe798925f4923548b367fd49f0ee5f0
generic

net: tap: NULL pointer derefence in dev_parse_header_protocol when skb->dev is null - kernel/git/stable/linux.git - Linux kernel stable tree

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

Vendor Advisories for CVE-2022-50073(3)

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

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:5.14.0-503.11.1.el9_52024-11-12redhat
redhatkernel-0:4.18.0-348.el82021-11-09redhat
linuxKernel @ 5.10.258—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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (54 versions)5.10.259-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux—5.19.6-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux—5.19.6-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux—5.19.6-1—

Weakness Classification(1)

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

Additional Vendor Advisories

(11)

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 5× in last 7d / 25× 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 155 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2022-50073?
CVE-2022-50073 is a medium vulnerability published on June 18, 2025. In the Linux kernel, the following vulnerability has been resolved: net: tap: NULL pointer derefence in devparseheader_protocol when skb->dev is null Fixes a NULL pointer derefence bug triggered from tap driver. When tapgetuser calls virtionethdrtoskb the skb->dev is null (in tap.c skb->dev is set…
When was CVE-2022-50073 disclosed?
CVE-2022-50073 was first published in the National Vulnerability Database on June 18, 2025, with the most recent update on August 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-50073 actively exploited?
CVE-2022-50073 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 91.4% of all scored CVEs.
What is the CVSS score of CVE-2022-50073?
CVE-2022-50073 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2022-50073?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-50073, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-50073

Explore →

Is Your Infrastructure Affected by CVE-2022-50073?

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

Start Free Scan →Browse All CVEs