CVE-2022-48662

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2022-51357 (ENISA EUVD) · GHSA-8wq2-m78j-qq93 (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

drm/i915/gem: Really move i915_gem_context.link under ref protection

i915_perf assumes that it can use the i915_gem_context reference to protect its i915->gem.contexts.list iteration. However, this requires that we do not remove the context from the list until after we drop the final reference and release the struct. If, as currently, we remove the context from the list during context_close(), the link.next pointer may be poisoned while we are holding the context reference and cause a GPF:

[ 4070.573157] i915 0000:00:02.0: [drm:i915_perf_open_ioctl [i915]] filtering on ctx_id=0x1fffff ctx_id_mask=0x1fffff [ 4070.574881] general protection fault, probably for non-canonical address 0xdead000000000100: 0000 [#1] PREEMPT SMP [ 4070.574897] CPU: 1 PID: 284392 Comm: amd_performance Tainted: G E 5.17.9 #180 [ 4070.574903] Hardware name: Intel Corporation NUC7i5BNK/NUC7i5BNB, BIOS BNKBL357.86A.0052.2017.0918.1346 09/18/2017 [ 4070.574907] RIP: 0010:oa_configure_all_contexts.isra.0+0x222/0x350 [i915] [ 4070.574982] Code: 08 e8 32 6e 10 e1 4d 8b 6d 50 b8 ff ff ff ff 49 83 ed 50 f0 41 0f c1 04 24 83 f8 01 0f 84 e3 00 00 00 85 c0 0f 8e fa 00 00 00 <49> 8b 45 50 48 8d 70 b0 49 8d 45 50 48 39 44 24 10 0f 85 34 fe ff [ 4070.574990] RSP: 0018:ffffc90002077b78 EFLAGS: 00010202 [ 4070.574995] RAX: 0000000000000002 RBX: 0000000000000002 RCX: 0000000000000000 [ 4070.575000] RDX: 0000000000000001 RSI: ffffc90002077b20 RDI: ffff88810ddc7c68 [ 4070.575004] RBP: 0000000000000001 R08: ffff888103242648 R09: fffffffffffffffc [ 4070.575008] R10: ffffffff82c50bc0 R11: 0000000000025c80 R12: ffff888101bf1860 [ 4070.575012] R13: dead0000000000b0 R14: ffffc90002077c04 R15: ffff88810be5cabc [ 4070.575016] FS: 00007f1ed50c0780(0000) GS:ffff88885ec80000(0000) knlGS:0000000000000000 [ 4070.575021] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 4070.575025] CR2: 00007f1ed5590280 CR3: 000000010ef6f005 CR4: 00000000003706e0 [ 4070.575029] Call Trace: [ 4070.575033] [ 4070.575037] lrc_configure_all_contexts+0x13e/0x150 [i915] [ 4070.575103] gen8_enable_metric_set+0x4d/0x90 [i915] [ 4070.575164] i915_perf_open_ioctl+0xbc0/0x1500 [i915] [ 4070.575224] ? asm_common_interrupt+0x1e/0x40 [ 4070.575232] ? i915_oa_init_reg_state+0x110/0x110 [i915] [ 4070.575290] drm_ioctl_kernel+0x85/0x110 [ 4070.575296] ? update_load_avg+0x5f/0x5e0 [ 4070.575302] drm_ioctl+0x1d3/0x370 [ 4070.575307] ? i915_oa_init_reg_state+0x110/0x110 [i915] [ 4070.575382] ? gen8_gt_irq_handler+0x46/0x130 [i915] [ 4070.575445] __x64_sys_ioctl+0x3c4/0x8d0 [ 4070.575451] ? __do_softirq+0xaa/0x1d2 [ 4070.575456] do_syscall_64+0x35/0x80 [ 4070.575461] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 4070.575467] RIP: 0033:0x7f1ed5c10397 [ 4070.575471] Code: 3c 1c e8 1c ff ff ff 85 c0 79 87 49 c7 c4 ff ff ff ff 5b 5d 4c 89 e0 41 5c c3 66 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d a9 da 0d 00 f7 d8 64 89 01 48 [ 4070.575478] RSP: 002b:00007ffd65c8d7a8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 [ 4070.575484] RAX: ffffffffffffffda RBX: 0000000000000006 RCX: 00007f1ed5c10397 [ 4070.575488] RDX: 00007ffd65c8d7c0 RSI: 0000000040106476 RDI: 0000000000000006 [ 4070.575492] RBP: 00005620972f9c60 R08: 000000000000000a R09: 0000000000000005 [ 4070.575496] R10: 000000000000000d R11: 0000000000000246 R12: 000000000000000a [ 4070.575500] R13: 000000000000000d R14: 0000000000000000 R15: 00007ffd65c8d7c0 [ 4070.575505] [ 4070.575507] Modules linked in: nls_ascii(E) nls_cp437(E) vfat(E) fat(E) i915(E) x86_pkg_temp_thermal(E) intel_powerclamp(E) crct10dif_pclmul(E) crc32_pclmul(E) crc32c_intel(E) aesni_intel(E) crypto_simd(E) intel_gtt(E) cryptd(E) ttm(E) rapl(E) intel_cstate(E) drm_kms_helper(E) cfbfillrect(E) syscopyarea(E) cfbimgblt(E) intel_uncore(E) sysfillrect(E) mei_me(E) sysimgblt(E) i2c_i801(E) fb_sys_fops(E) mei(E) intel_pch_thermal(E) i2c_smbus ---truncated---

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/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)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 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 low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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.2%
EPSS %ILE
16th
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 (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). 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 low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 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 low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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)14 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 total (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

April 28, 2024

Last Modified

November 21, 2024

Advisory Details (3)

Auto-updated Oct 21, 2026
Patch available.
Web page

drm/i915/gem: Really move i915_gem_context.link under ref protection - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f799e0568d6c153368b177e0bbbde7dcc4ce7f1d
Web page

drm/i915/gem: Really move i915_gem_context.link under ref protection - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d119888b09bd567e07c6b93a07f175df88857e02
Web page

drm/i915/gem: Really move i915_gem_context.link under ref protection - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/713fa3e4591f65f804bdc88e8648e219fabc9ee1

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
linuxKernel @ 5.15.72 (fixes >=5.12.0)—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

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

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2022-48662?
CVE-2022-48662 is a high-severity vulnerability; its CVE record was published on April 28, 2024. In the Linux kernel, the following vulnerability has been resolved: drm/i915/gem: Really move i915_gem_context.link under ref protection i915_perf assumes that it can use the i915_gem_context reference to protect its i915->gem.contexts.list iteration. However, this requires that we do not remove…
When was the CVE record for CVE-2022-48662 published?
The CVE record for CVE-2022-48662 was published on April 28, 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 November 21, 2024; the record at its source may have been updated since.
Is CVE-2022-48662 actively exploited?
CVE-2022-48662 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (16th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-48662?
CVE-2022-48662 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2022-48662?
A fix for CVE-2022-48662 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-2022-48662

Explore →

Is Your Infrastructure Affected by CVE-2022-48662?

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

Book a Demo →Browse All CVEs