CVE-2023-53455

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 2025-10-01. 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-2025-32806 (ENISA EUVD) · GHSA-pc5j-pxxw-pj8m (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/vc4: drop all currently held locks if deadlock happens

If vc4_hdmi_reset_link() returns -EDEADLK, it means that a deadlock happened in the locking context. This situation should be addressed by dropping all currently held locks and block until the contended lock becomes available. Currently, vc4 is not dealing with the deadlock properly, producing the following output when PROVE_LOCKING is enabled:

[ 825.612809] ------------[ cut here ]------------ [ 825.612852] WARNING: CPU: 1 PID: 116 at drivers/gpu/drm/drm_modeset_lock.c:276 drm_modeset_drop_locks+0x60/0x68 [drm] [ 825.613458] Modules linked in: 8021q mrp garp stp llc raspberrypi_cpufreq brcmfmac brcmutil crct10dif_ce hci_uart cfg80211 btqca btbcm bluetooth vc4 raspberrypi_hwmon snd_soc_hdmi_codec cec clk_raspberrypi ecdh_generic drm_display_helper ecc rfkill drm_dma_helper drm_kms_helper pwm_bcm2835 bcm2835_thermal bcm2835_rng rng_core i2c_bcm2835 drm fuse ip_tables x_tables ipv6 [ 825.613735] CPU: 1 PID: 116 Comm: kworker/1:2 Tainted: G W 6.1.0-rc6-01399-g941aae326315 #3 [ 825.613759] Hardware name: Raspberry Pi 3 Model B Rev 1.2 (DT) [ 825.613777] Workqueue: events output_poll_execute [drm_kms_helper] [ 825.614038] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 825.614063] pc : drm_modeset_drop_locks+0x60/0x68 [drm] [ 825.614603] lr : drm_helper_probe_detect+0x120/0x1b4 [drm_kms_helper] [ 825.614829] sp : ffff800008313bf0 [ 825.614844] x29: ffff800008313bf0 x28: ffffcd7778b8b000 x27: 0000000000000000 [ 825.614883] x26: 0000000000000001 x25: 0000000000000001 x24: ffff677cc35c2758 [ 825.614920] x23: ffffcd7707d01430 x22: ffffcd7707c3edc7 x21: 0000000000000001 [ 825.614958] x20: 0000000000000000 x19: ffff800008313c10 x18: 000000000000b6d3 [ 825.614995] x17: ffffcd777835e214 x16: ffffcd7777cef870 x15: fffff81000000000 [ 825.615033] x14: 0000000000000000 x13: 0000000000000099 x12: 0000000000000002 [ 825.615070] x11: 72917988020af800 x10: 72917988020af800 x9 : 72917988020af800 [ 825.615108] x8 : ffff677cc665e0a8 x7 : d00a8c180000110c x6 : ffffcd77774c0054 [ 825.615145] x5 : 0000000000000000 x4 : 0000000000000001 x3 : 0000000000000000 [ 825.615181] x2 : ffff677cc55e1880 x1 : ffffcd7777cef8ec x0 : ffff800008313c10 [ 825.615219] Call trace: [ 825.615232] drm_modeset_drop_locks+0x60/0x68 [drm] [ 825.615773] drm_helper_probe_detect+0x120/0x1b4 [drm_kms_helper] [ 825.616003] output_poll_execute+0xe4/0x224 [drm_kms_helper] [ 825.616233] process_one_work+0x2b4/0x618 [ 825.616264] worker_thread+0x24c/0x464 [ 825.616288] kthread+0xec/0x110 [ 825.616310] ret_from_fork+0x10/0x20 [ 825.616335] irq event stamp: 7634 [ 825.616349] hardirqs last enabled at (7633): [] _raw_spin_unlock_irq+0x3c/0x78 [ 825.616384] hardirqs last disabled at (7634): [] __schedule+0x134/0x9f0 [ 825.616411] softirqs last enabled at (7630): [] local_bh_enable+0x4/0x30 [ipv6] [ 825.617019] softirqs last disabled at (7618): [] local_bh_disable+0x4/0x30 [ipv6] [ 825.617586] ---[ end trace 0000000000000000 ]---

Therefore, deal with the deadlock as suggested by [1], using the function drm_modeset_backoff().

[1] https://docs.kernel.org/gpu/drm-kms.html?highlight=kms#kms-locking

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 BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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
4th
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 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 (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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

October 1, 2025

Last Modified

January 16, 2026

References (3)

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
linuxKernel @ 6.1.16 (fixes >=6.1.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.1.20-1: fixed in 6.1.20-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.20-1: fixed in 6.1.20-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.20-1: fixed in 6.1.20-1
—

Data Freshness Timeline

(refreshed 6× in last 7d / 34× 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 93 of 192 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. 7 repeat rows among the latest 100 are merged into the row they repeat. The 99 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2023-53455?
CVE-2023-53455 is a medium-severity vulnerability; its CVE record was published on October 1, 2025. In the Linux kernel, the following vulnerability has been resolved: drm/vc4: drop all currently held locks if deadlock happens If vc4_hdmi_reset_link() returns -EDEADLK, it means that a deadlock happened in the locking context. This situation should be addressed by dropping all currently held locks…
When was the CVE record for CVE-2023-53455 published?
The CVE record for CVE-2023-53455 was published on October 1, 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 16, 2026; the record at its source may have been updated since.
Is CVE-2023-53455 actively exploited?
CVE-2023-53455 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-53455?
CVE-2023-53455 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2023-53455?
A fix for CVE-2023-53455 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-2023-53455

Explore →

Is Your Infrastructure Affected by CVE-2023-53455?

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

Book a Demo →Browse All CVEs