CVE-2022-50412

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 2025-09-18. 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 — 4 sources updated this week

Also known asEUVD-2025-29879 (ENISA EUVD) · GHSA-wj9m-5hmc-xhpp (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: bridge: adv7511: unregister cec i2c device after cec adapter

cec_unregister_adapter() assumes that the underlying adapter ops are callable. For example, if the CEC adapter currently has a valid physical address, then the unregistration procedure will invalidate the physical address by setting it to f.f.f.f. Whence the following kernel oops observed after removing the adv7511 module:

Unable to handle kernel execution of user memory at virtual address 0000000000000000 Internal error: Oops: 86000004 [#1] PREEMPT_RT SMP Call trace: 0x0 adv7511_cec_adap_log_addr+0x1ac/0x1c8 [adv7511] cec_adap_unconfigure+0x44/0x90 [cec] __cec_s_phys_addr.part.0+0x68/0x230 [cec] __cec_s_phys_addr+0x40/0x50 [cec] cec_unregister_adapter+0xb4/0x118 [cec] adv7511_remove+0x60/0x90 [adv7511] i2c_device_remove+0x34/0xe0 device_release_driver_internal+0x114/0x1f0 driver_detach+0x54/0xe0 bus_remove_driver+0x60/0xd8 driver_unregister+0x34/0x60 i2c_del_driver+0x2c/0x68 adv7511_exit+0x1c/0x67c [adv7511] __arm64_sys_delete_module+0x154/0x288 invoke_syscall+0x48/0x100 el0_svc_common.constprop.0+0x48/0xe8 do_el0_svc+0x28/0x88 el0_svc+0x1c/0x50 el0t_64_sync_handler+0xa8/0xb0 el0t_64_sync+0x15c/0x160 Code: bad PC value ---[ end trace 0000000000000000 ]---

Protect against this scenario by unregistering i2c_cec after unregistering the CEC adapter. Duly disable the CEC clock afterwards too.

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

September 18, 2025

Last Modified

January 14, 2026

Advisory Details (5)

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

drm: bridge: adv7511: unregister cec i2c device after cec adapter - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm: bridge: adv7511: unregister cec i2c device after cec adapter - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/86ae5170786aea3e1751123ca55700fb9b37b623
Web page

drm: bridge: adv7511: unregister cec i2c device after cec adapter - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4d4d5bc659206b187263190ad9a03513f625659d
Web page

drm: bridge: adv7511: unregister cec i2c device after cec adapter - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/40cdb02cb9f965732eb543d47f15bef8d10f0f5f
Web page

drm: bridge: adv7511: unregister cec i2c device after cec adapter - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3747465c5da7a11957a34bbb9485d9fc253b91cc

Vendor Advisories for CVE-2022-50412(2)

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 / EcosystemFix (by version range) / PatchReleasedSource
redhatkernel-0:4.18.0-513.5.1.el8_92023-11-14redhat
redhatkernel-0:5.14.0-362.8.1.el9_32023-11-07redhat
linuxKernel @ 5.10.234 (fixes >=4.15.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 ... 5.10.92-2 (44 versions)
  • every version up to 5.10.234-1: fixed in 5.10.234-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.0.3-1: fixed in 6.0.3-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.0.3-1: fixed in 6.0.3-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.0.3-1: fixed in 6.0.3-1
—

Data Freshness Timeline

(refreshed 8× 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 191 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 94 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2022-50412?
CVE-2022-50412 is a high-severity vulnerability; its CVE record was published on September 18, 2025. In the Linux kernel, the following vulnerability has been resolved: drm: bridge: adv7511: unregister cec i2c device after cec adapter cec_unregister_adapter() assumes that the underlying adapter ops are callable. For example, if the CEC adapter currently has a valid physical address, then the…
When was the CVE record for CVE-2022-50412 published?
The CVE record for CVE-2022-50412 was published on September 18, 2025. 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 January 14, 2026; the record at its source may have been updated since.
Is CVE-2022-50412 actively exploited?
CVE-2022-50412 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (7th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-50412?
CVE-2022-50412 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2022-50412?
A fix for CVE-2022-50412 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-50412 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-50412

Explore →

Is Your Infrastructure Affected by CVE-2022-50412?

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