CVE-2022-48633

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2022-51328 (ENISA EUVD) · GHSA-9939-379m-g97w (GitHub Security Advisories)Source: ENISA EUVD

5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

drm/gma500: Fix WARN_ON(lock->magic != lock) error

psb_gem_unpin() calls dma_resv_lock() but the underlying ww_mutex gets destroyed by drm_gem_object_release() move the drm_gem_object_release() call in psb_gem_free_object() to after the unpin to fix the below warning:

[ 79.693962] ------------[ cut here ]------------ [ 79.693992] DEBUG_LOCKS_WARN_ON(lock->magic != lock) [ 79.694015] WARNING: CPU: 0 PID: 240 at kernel/locking/mutex.c:582 __ww_mutex_lock.constprop.0+0x569/0xfb0 [ 79.694052] Modules linked in: rfcomm snd_seq_dummy snd_hrtimer qrtr bnep ath9k ath9k_common ath9k_hw snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel ath3k snd_intel_dspcfg mac80211 snd_intel_sdw_acpi btusb snd_hda_codec btrtl btbcm btintel btmtk bluetooth at24 snd_hda_core snd_hwdep uvcvideo snd_seq libarc4 videobuf2_vmalloc ath videobuf2_memops videobuf2_v4l2 videobuf2_common snd_seq_device videodev acer_wmi intel_powerclamp coretemp mc snd_pcm joydev sparse_keymap ecdh_generic pcspkr wmi_bmof cfg80211 i2c_i801 i2c_smbus snd_timer snd r8169 rfkill lpc_ich soundcore acpi_cpufreq zram rtsx_pci_sdmmc mmc_core serio_raw rtsx_pci gma500_gfx(E) video wmi ip6_tables ip_tables i2c_dev fuse [ 79.694436] CPU: 0 PID: 240 Comm: plymouthd Tainted: G W E 6.0.0-rc3+ #490 [ 79.694457] Hardware name: Packard Bell dot s/SJE01_CT, BIOS V1.10 07/23/2013 [ 79.694469] RIP: 0010:__ww_mutex_lock.constprop.0+0x569/0xfb0 [ 79.694496] Code: ff 85 c0 0f 84 15 fb ff ff 8b 05 ca 3c 11 01 85 c0 0f 85 07 fb ff ff 48 c7 c6 30 cb 84 aa 48 c7 c7 a3 e1 82 aa e8 ac 29 f8 ff <0f> 0b e9 ed fa ff ff e8 5b 83 8a ff 85 c0 74 10 44 8b 0d 98 3c 11 [ 79.694513] RSP: 0018:ffffad1dc048bbe0 EFLAGS: 00010282 [ 79.694623] RAX: 0000000000000028 RBX: 0000000000000000 RCX: 0000000000000000 [ 79.694636] RDX: 0000000000000001 RSI: ffffffffaa8b0ffc RDI: 00000000ffffffff [ 79.694650] RBP: ffffad1dc048bc80 R08: 0000000000000000 R09: ffffad1dc048ba90 [ 79.694662] R10: 0000000000000003 R11: ffffffffaad62fe8 R12: ffff9ff302103138 [ 79.694675] R13: ffff9ff306ec8000 R14: ffff9ff307779078 R15: ffff9ff3014c0270 [ 79.694690] FS: 00007ff1cccf1740(0000) GS:ffff9ff3bc200000(0000) knlGS:0000000000000000 [ 79.694705] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 79.694719] CR2: 0000559ecbcb4420 CR3: 0000000013210000 CR4: 00000000000006f0 [ 79.694734] Call Trace: [ 79.694749] [ 79.694761] ? __schedule+0x47f/0x1670 [ 79.694796] ? psb_gem_unpin+0x27/0x1a0 [gma500_gfx] [ 79.694830] ? lock_is_held_type+0xe3/0x140 [ 79.694864] ? ww_mutex_lock+0x38/0xa0 [ 79.694885] ? __cond_resched+0x1c/0x30 [ 79.694902] ww_mutex_lock+0x38/0xa0 [ 79.694925] psb_gem_unpin+0x27/0x1a0 [gma500_gfx] [ 79.694964] psb_gem_unpin+0x199/0x1a0 [gma500_gfx] [ 79.694996] drm_gem_object_release_handle+0x50/0x60 [ 79.695020] ? drm_gem_object_handle_put_unlocked+0xf0/0xf0 [ 79.695042] idr_for_each+0x4b/0xb0 [ 79.695066] ? _raw_spin_unlock_irqrestore+0x30/0x60 [ 79.695095] drm_gem_release+0x1c/0x30 [ 79.695118] drm_file_free.part.0+0x1ea/0x260 [ 79.695150] drm_release+0x6a/0x120 [ 79.695175] __fput+0x9f/0x260 [ 79.695203] task_work_run+0x59/0xa0 [ 79.695227] do_exit+0x387/0xbe0 [ 79.695250] ? seqcount_lockdep_reader_access.constprop.0+0x82/0x90 [ 79.695275] ? lockdep_hardirqs_on+0x7d/0x100 [ 79.695304] do_group_exit+0x33/0xb0 [ 79.695331] __x64_sys_exit_group+0x14/0x20 [ 79.695353] do_syscall_64+0x58/0x80 [ 79.695376] ? up_read+0x17/0x20 [ 79.695401] ? lock_is_held_type+0xe3/0x140 [ 79.695429] ? asm_exc_page_fault+0x22/0x30 [ 79.695450] ? lockdep_hardirqs_on+0x7d/0x100 [ 79.695473] entry_SYSCALL_64_after_hwframe+0x63/0xcd [ 79.695493] RIP: 0033:0x7ff1ccefe3f1 [ 79.695516] Code: Unable to access opcode bytes at RIP 0x7ff1ccefe3c7. [ 79.695607] RSP: 002b:00007ffed4413378 EFLAGS: ---truncated---

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/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)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 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 every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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
9th
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 (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-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-25). 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 every mission impact level.CISA BOD 26-04: 60 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 every mission impact level.

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

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

August 13, 2026

Advisory Details (2)

Auto-updated Aug 13, 2026
Patch available.
Web page

drm/gma500: Fix WARN_ON(lock->magic != lock) error - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/gma500: Fix WARN_ON(lock->magic != lock) error - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/55c077d97fa67e9f19952bb24122a8316b089474

Vendor Advisories for CVE-2022-48633(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 / EcosystemFix (by version range) / PatchReleasedSource
linuxKernel @ 5.19.12 (fixes >=5.19.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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)
  • every version on: no fix on record
—
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 7× in last 7d / 37× 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 189 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 92 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% · 9th percentile
  2. 2026-11-01 16:30 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  3. 2026-10-31 16:29 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  4. 2026-10-30 16:31 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  5. 2026-10-29 16:30 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  6. 2026-10-28 16:28 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  7. 2026-10-27 16:28 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  8. 2026-10-25 17:55 UTCEG score recompute
  9. 2026-10-25 16:29 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  10. 2026-10-24 18:08 UTCEG score recompute
  11. 2026-10-24 18:08 UTCVendor advisory
  12. 2026-10-24 18:08 UTCGHSA enrichmentGHSA-9939-379m-g97w · GitHub CVSS 5.5
  13. 2026-10-24 16:29 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  14. 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  15. 2026-10-22 16:30 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  16. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  17. 2026-10-20 16:29 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  18. 2026-10-19 16:28 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  19. 2026-10-18 16:29 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  20. 2026-10-18 08:21 UTCEG score recompute
  21. 2026-10-17 16:29 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  22. 2026-10-16 16:35 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  23. 2026-10-15 16:28 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  24. 2026-10-14 16:29 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  25. 2026-10-13 16:29 UTCEPSS rescoreEPSS 0.2% · 8th percentile
Show 72 more
  1. 2026-10-12 18:42 UTCEG score recompute
  2. 2026-10-12 16:30 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  3. 2026-10-11 22:06 UTCEG score recompute
  4. 2026-10-11 13:45 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  5. 2026-10-10 19:57 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  6. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  7. 2026-10-08 17:05 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  8. 2026-10-07 23:45 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  9. 2026-10-07 06:35 UTCOSV refresh
  10. 2026-10-06 15:14 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  11. 2026-10-05 17:40 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  12. 2026-10-04 23:19 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  13. 2026-10-03 14:23 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  14. 2026-09-30 16:11 UTCEG score recompute
  15. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  16. 2026-09-27 13:42 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  17. 2026-09-26 15:55 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  18. 2026-09-26 00:22 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  19. 2026-09-24 14:00 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  20. 2026-09-23 13:45 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  21. 2026-09-20 20:13 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  22. 2026-09-17 12:20 UTCOSV refresh
  23. 2026-09-16 14:05 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  24. 2026-09-16 05:11 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  25. 2026-09-15 03:07 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  26. 2026-09-13 16:44 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  27. 2026-09-11 14:50 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  28. 2026-09-11 09:34 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  29. 2026-09-08 21:57 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  30. 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  31. 2026-09-06 13:45 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  32. 2026-09-05 15:25 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  33. 2026-09-04 13:57 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  34. 2026-09-04 05:04 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  35. 2026-09-02 14:09 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  36. 2026-09-01 13:51 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  37. 2026-08-30 19:15 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  38. 2026-08-30 01:19 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  39. 2026-08-29 12:43 UTCOSV refresh
  40. 2026-08-28 21:38 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  41. 2026-08-27 14:22 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  42. 2026-08-26 14:43 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  43. 2026-08-25 13:46 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  44. 2026-08-23 00:17 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  45. 2026-08-21 23:46 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  46. 2026-08-19 17:01 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  47. 2026-08-18 13:45 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  48. 2026-08-17 13:44 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  49. 2026-08-16 14:53 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  50. 2026-08-16 02:12 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  51. 2026-08-15 01:27 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  52. 2026-08-13 21:58 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  53. 2026-08-13 00:23 UTCGHSA enrichmentGHSA-9939-379m-g97w · GitHub CVSS 5.5
  54. 2026-08-13 00:06 UTCEG score recompute
  55. 2026-08-13 00:06 UTCGHSA enrichmentGHSA-9939-379m-g97w · GitHub CVSS 5.5
  56. 2026-08-12 13:48 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  57. 2026-08-09 13:44 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  58. 2026-08-08 16:34 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  59. 2026-08-07 16:24 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  60. 2026-08-06 13:44 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  61. 2026-08-05 19:15 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  62. 2026-08-04 15:07 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  63. 2026-08-03 10:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  64. 2026-08-02 02:24 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  65. 2026-08-01 05:36 UTCOSV refresh
  66. 2026-08-01 04:13 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  67. 2026-07-30 16:25 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  68. 2026-07-30 01:28 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  69. 2026-07-28 15:34 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  70. 2026-07-26 14:52 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  71. 2026-07-25 14:16 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  72. 2026-07-24 14:15 UTCEPSS rescoreEPSS 0.2% · 9th percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2022-48633?
CVE-2022-48633 is a medium-severity vulnerability; its CVE record was published on April 28, 2024. In the Linux kernel, the following vulnerability has been resolved: drm/gma500: Fix WARN_ON(lock->magic != lock) error psb_gem_unpin() calls dma_resv_lock() but the underlying ww_mutex gets destroyed by drm_gem_object_release() move the drm_gem_object_release() call in psb_gem_free_object() to…
When was the CVE record for CVE-2022-48633 published?
The CVE record for CVE-2022-48633 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 August 13, 2026; the record at its source may have been updated since.
Is CVE-2022-48633 actively exploited?
CVE-2022-48633 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (9th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-48633?
CVE-2022-48633 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2022-48633?
A fix for CVE-2022-48633 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-48633 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2022-48633?

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

Book a Demo →Browse All CVEs