CVE-2022-48785

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
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:

ipv6: mcast: use rcu-safe version of ipv6_get_lladdr()

Some time ago 8965779d2c0e ("ipv6,mcast: always hold idev->lock before mca_lock") switched ipv6_get_lladdr() to __ipv6_get_lladdr(), which is rcu-unsafe version. That was OK, because idev->lock was held for these codepaths.

In 88e2ca308094 ("mld: convert ifmcaddr6 to RCU") these external locks were removed, so we probably need to restore the original rcu-safe call.

Otherwise, we occasionally get a machine crashed/stalled with the following in dmesg:

[ 3405.966610][T230589] general protection fault, probably for non-canonical address 0xdead00000000008c: 0000 [#1] SMP NOPTI [ 3405.982083][T230589] CPU: 44 PID: 230589 Comm: kworker/44:3 Tainted: G O 5.15.19-cloudflare-2022.2.1 #1 [ 3405.998061][T230589] Hardware name: SUPA-COOL-SERV [ 3406.009552][T230589] Workqueue: mld mld_ifc_work [ 3406.017224][T230589] RIP: 0010:__ipv6_get_lladdr+0x34/0x60 [ 3406.025780][T230589] Code: 57 10 48 83 c7 08 48 89 e5 48 39 d7 74 3e 48 8d 82 38 ff ff ff eb 13 48 8b 90 d0 00 00 00 48 8d 82 38 ff ff ff 48 39 d7 74 22 <66> 83 78 32 20 77 1b 75 e4 89 ca 23 50 2c 75 dd 48 8b 50 08 48 8b [ 3406.055748][T230589] RSP: 0018:ffff94e4b3fc3d10 EFLAGS: 00010202 [ 3406.065617][T230589] RAX: dead00000000005a RBX: ffff94e4b3fc3d30 RCX: 0000000000000040 [ 3406.077477][T230589] RDX: dead000000000122 RSI: ffff94e4b3fc3d30 RDI: ffff8c3a31431008 [ 3406.089389][T230589] RBP: ffff94e4b3fc3d10 R08: 0000000000000000 R09: 0000000000000000 [ 3406.101445][T230589] R10: ffff8c3a31430000 R11: 000000000000000b R12: ffff8c2c37887100 [ 3406.113553][T230589] R13: ffff8c3a39537000 R14: 00000000000005dc R15: ffff8c3a31431000 [ 3406.125730][T230589] FS: 0000000000000000(0000) GS:ffff8c3b9fc80000(0000) knlGS:0000000000000000 [ 3406.138992][T230589] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 3406.149895][T230589] CR2: 00007f0dfea1db60 CR3: 000000387b5f2000 CR4: 0000000000350ee0 [ 3406.162421][T230589] Call Trace: [ 3406.170235][T230589] [ 3406.177736][T230589] mld_newpack+0xfe/0x1a0 [ 3406.186686][T230589] add_grhead+0x87/0xa0 [ 3406.195498][T230589] add_grec+0x485/0x4e0 [ 3406.204310][T230589] ? newidle_balance+0x126/0x3f0 [ 3406.214024][T230589] mld_ifc_work+0x15d/0x450 [ 3406.223279][T230589] process_one_work+0x1e6/0x380 [ 3406.232982][T230589] worker_thread+0x50/0x3a0 [ 3406.242371][T230589] ? rescuer_thread+0x360/0x360 [ 3406.252175][T230589] kthread+0x127/0x150 [ 3406.261197][T230589] ? set_kthread_struct+0x40/0x40 [ 3406.271287][T230589] ret_from_fork+0x22/0x30 [ 3406.280812][T230589] [ 3406.288937][T230589] Modules linked in: ... [last unloaded: kheaders] [ 3406.476714][T230589] ---[ end trace 3525a7655f2f3b9e ]---

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

Published

July 16, 2024

Last Modified

July 24, 2026

Advisory Details (4)

Auto-updated Jul 24, 2026
No patch confirmed yet.
generic

ipv6: mcast: use rcu-safe version of ipv6_get_lladdr() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3e11ef1903cf6c2fba35594b193a3570854d9e9e
generic

ipv6: mcast: use rcu-safe version of ipv6_get_lladdr() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/27f567c84f446048670376827e356f9c92033bf9
generic

ipv6: mcast: use rcu-safe version of ipv6_get_lladdr() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/26394fc118d6115390bd5b3a0fb17096271da227
generic

ipv6: mcast: use rcu-safe version of ipv6_get_lladdr() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c49c69dc9f3e699fa3150aca7b189eea707b4047

Vendor Advisories for CVE-2022-48785(1)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 5.15.25—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 14× 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 112 total refreshes for this CVE.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2022-48785?
CVE-2022-48785 is a medium vulnerability published on July 16, 2024. In the Linux kernel, the following vulnerability has been resolved: ipv6: mcast: use rcu-safe version of ipv6getlladdr() Some time ago 8965779d2c0e ("ipv6,mcast: always hold idev->lock before mca_lock") switched ipv6getlladdr() to ipv6getlladdr(), which is rcu-unsafe version. That was OK, because…
When was CVE-2022-48785 disclosed?
CVE-2022-48785 was first published in the National Vulnerability Database on July 16, 2024, with the most recent update on July 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-48785 actively exploited?
CVE-2022-48785 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 93.2% of all scored CVEs.
What is the CVSS score of CVE-2022-48785?
CVE-2022-48785 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2022-48785?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-48785, 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-48785

Explore →

Is Your Infrastructure Affected by CVE-2022-48785?

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

Start Free Scan →Browse All CVEs