CVE-2022-48862

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.5Exploit: NoneExposed: 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:

vhost: fix hung thread due to erroneous iotlb entries

In vhost_iotlb_add_range_ctx(), range size can overflow to 0 when start is 0 and last is ULONG_MAX. One instance where it can happen is when userspace sends an IOTLB message with iova=size=uaddr=0 (vhost_process_iotlb_msg). So, an entry with size = 0, start = 0, last = ULONG_MAX ends up in the iotlb. Next time a packet is sent, iotlb_access_ok() loops indefinitely due to that erroneous entry.

Call Trace: iotlb_access_ok+0x21b/0x3e0 drivers/vhost/vhost.c:1340 vq_meta_prefetch+0xbc/0x280 drivers/vhost/vhost.c:1366 vhost_transport_do_send_pkt+0xe0/0xfd0 drivers/vhost/vsock.c:104 vhost_worker+0x23d/0x3d0 drivers/vhost/vhost.c:372 kthread+0x2e9/0x3a0 kernel/kthread.c:377 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295

Reported by syzbot at: https://syzkaller.appspot.com/bug?extid=0abd373e2e50d704db87

To fix this, do two things:

  • Return -EINVAL in vhost_chr_write_iter() when userspace asks to map
a range with size 0.
  • Fix vhost_iotlb_add_range_ctx() to handle the range [0, ULONG_MAX]
by splitting it into two entries.

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

Published

July 16, 2024

Last Modified

November 21, 2024

References (6)

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 5.15.29—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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 47× 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 106 total refreshes for this CVE.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2022-48862?
CVE-2022-48862 is a medium vulnerability published on July 16, 2024. In the Linux kernel, the following vulnerability has been resolved: vhost: fix hung thread due to erroneous iotlb entries In vhostiotlbaddrangectx(), range size can overflow to 0 when start is 0 and last is ULONG_MAX. One instance where it can happen is when userspace sends an IOTLB message with…
When was CVE-2022-48862 disclosed?
CVE-2022-48862 was first published in the National Vulnerability Database on July 16, 2024, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-48862 actively exploited?
CVE-2022-48862 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 11.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2022-48862?
CVE-2022-48862 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2022-48862?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-48862, 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-2022-48862

Explore →

Is Your Infrastructure Affected by CVE-2022-48862?

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

Start Free Scan →Browse All CVEs