CVE-2023-52516

MEDIUMNVD 5.55.5

Also known asEUVD-2023-57141 (ENISA EUVD) · GHSA-4jr3-hwqp-2vq3 (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:

dma-debug: don't call __dma_entry_alloc_check_leak() under free_entries_lock

__dma_entry_alloc_check_leak() calls into printk -> serial console output (qcom geni) and grabs port->lock under free_entries_lock spin lock, which is a reverse locking dependency chain as qcom_geni IRQ handler can call into dma-debug code and grab free_entries_lock under port->lock.

Move __dma_entry_alloc_check_leak() call out of free_entries_lock scope so that we don't acquire serial console's port->lock under it.

Trimmed-down lockdep splat:

The existing dependency chain (in reverse order) is:

-> #2 (free_entries_lock){-.-.}-{2:2}: _raw_spin_lock_irqsave+0x60/0x80 dma_entry_alloc+0x38/0x110 debug_dma_map_page+0x60/0xf8 dma_map_page_attrs+0x1e0/0x230 dma_map_single_attrs.constprop.0+0x6c/0xc8 geni_se_rx_dma_prep+0x40/0xcc qcom_geni_serial_isr+0x310/0x510 __handle_irq_event_percpu+0x110/0x244 handle_irq_event_percpu+0x20/0x54 handle_irq_event+0x50/0x88 handle_fasteoi_irq+0xa4/0xcc handle_irq_desc+0x28/0x40 generic_handle_domain_irq+0x24/0x30 gic_handle_irq+0xc4/0x148 do_interrupt_handler+0xa4/0xb0 el1_interrupt+0x34/0x64 el1h_64_irq_handler+0x18/0x24 el1h_64_irq+0x64/0x68 arch_local_irq_enable+0x4/0x8 ____do_softirq+0x18/0x24 ...

-> #1 (&port_lock_key){-.-.}-{2:2}: _raw_spin_lock_irqsave+0x60/0x80 qcom_geni_serial_console_write+0x184/0x1dc console_flush_all+0x344/0x454 console_unlock+0x94/0xf0 vprintk_emit+0x238/0x24c vprintk_default+0x3c/0x48 vprintk+0xb4/0xbc _printk+0x68/0x90 register_console+0x230/0x38c uart_add_one_port+0x338/0x494 qcom_geni_serial_probe+0x390/0x424 platform_probe+0x70/0xc0 really_probe+0x148/0x280 __driver_probe_device+0xfc/0x114 driver_probe_device+0x44/0x100 __device_attach_driver+0x64/0xdc bus_for_each_drv+0xb0/0xd8 __device_attach+0xe4/0x140 device_initial_probe+0x1c/0x28 bus_probe_device+0x44/0xb0 device_add+0x538/0x668 of_device_add+0x44/0x50 of_platform_device_create_pdata+0x94/0xc8 of_platform_bus_create+0x270/0x304 of_platform_populate+0xac/0xc4 devm_of_platform_populate+0x60/0xac geni_se_probe+0x154/0x160 platform_probe+0x70/0xc0 ...

-> #0 (console_owner){-...}-{0:0}: __lock_acquire+0xdf8/0x109c lock_acquire+0x234/0x284 console_flush_all+0x330/0x454 console_unlock+0x94/0xf0 vprintk_emit+0x238/0x24c vprintk_default+0x3c/0x48 vprintk+0xb4/0xbc _printk+0x68/0x90 dma_entry_alloc+0xb4/0x110 debug_dma_map_sg+0xdc/0x2f8 __dma_map_sg_attrs+0xac/0xe4 dma_map_sgtable+0x30/0x4c get_pages+0x1d4/0x1e4 [msm] msm_gem_pin_pages_locked+0x38/0xac [msm] msm_gem_pin_vma_locked+0x58/0x88 [msm] msm_ioctl_gem_submit+0xde4/0x13ac [msm] drm_ioctl_kernel+0xe0/0x15c drm_ioctl+0x2e8/0x3f4 vfs_ioctl+0x30/0x50 ...

Chain exists of: console_owner --> &port_lock_key --> free_entries_lock

Possible unsafe locking scenario:

CPU0 CPU1 ---- ---- lock(free_entries_lock); lock(&port_lock_key); lock(free_entries_lock); lock(console_owner);

* DEADLOCK *

Call trace: dump_backtrace+0xb4/0xf0 show_stack+0x20/0x30 dump_stack_lvl+0x60/0x84 dump_stack+0x18/0x24 print_circular_bug+0x1cc/0x234 check_noncircular+0x78/0xac __lock_acquire+0xdf8/0x109c lock_acquire+0x234/0x284 console_flush_all+0x330/0x454 consol ---truncated---

CVSS v3: 5.5
EG Score: 5.5MEDIUMmedium confidence
EG Risk: 25
EPSS PROB: 0.2%
EPSS %ILE: 6th
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

March 2, 2024

Last Modified

December 11, 2024

References (5)

CVE Programhttps://git.kernel.org/stable/c/ac0d068099349cbca3d93f2e3b15bb329364b08cPatch
CVE Programhttps://git.kernel.org/stable/c/be8f49029eca3efbad0d74dbff3cb9129994ffabPatch
CVE Programhttps://git.kernel.org/stable/c/c79300599923daaa30f417c75555d5566b3d31aePatch
CVE Programhttps://git.kernel.org/stable/c/fb5a4315591dae307a65fc246ca80b5159d296e1Patch
CVE Programhttps://git.kernel.org/stable/c/fe2b811a02c3244ebf6059039e4a9e715e26a9e3Patch

Patch Availability(1)

Vendor / Ecosystem	Fix (by version range) / Patch	Released	Source
linux	Kernel @ 5.10.198 (fixes >=5.0.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)

Package	Vulnerable range	Fix by version range	Dependents
linux	5.10.103-1 ... 5.10.92-2 (35 versions)	every version up to 5.10.205-1: fixed in 5.10.205-1	—

Debian:12(1)

Package	Vulnerable range	Fix by version range	Dependents
linux	6.1.27-1 ... 6.1.55-1~bpo11+1 (11 versions)	every version up to 6.1.64-1: fixed in 6.1.64-1	—

Debian:13(1)

Package	Vulnerable range	Fix by version range	Dependents
linux	—	every version up to 6.5.6-1: fixed in 6.5.6-1	—

Debian:14(1)

Package	Vulnerable range	Fix by version range	Dependents
linux	—	every version up to 6.5.6-1: fixed in 6.5.6-1	—

Weakness Classification(1)

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

CWE-667Improper Locking

Data Freshness Timeline

(refreshed 7× in last 7d / 35× 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 92 of 197 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. 8 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.

2026-11-01 16:31 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-10-31 16:30 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-10-30 16:31 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-10-29 16:30 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-10-28 16:29 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-10-27 16:29 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-10-26 16:29 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-10-25 17:29 UTCEG score recompute
2026-10-25 16:30 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-10-24 16:29 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-10-24 11:44 UTCEG score recompute
2026-10-24 11:44 UTCGHSA enrichmentGHSA-4jr3-hwqp-2vq3 · GitHub CVSS 5.5
2026-10-23 16:29 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-10-22 16:31 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-10-21 16:29 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-10-20 16:30 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-10-19 16:29 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-10-18 16:29 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-10-18 07:42 UTCEG score recompute
2026-10-16 16:36 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-10-15 16:29 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-10-14 16:30 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-10-13 16:30 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-10-12 18:13 UTCEG score recompute
2026-10-12 16:31 UTCEPSS rescoreEPSS 0.2% · 5th percentile

Show 67 more

2026-10-11 21:38 UTCEG score recompute
2026-10-11 21:24 UTCOSV refresh
2026-10-11 13:45 UTCEPSS rescoreEPSS 0.2% · 5th percentile
2026-10-10 19:58 UTCEPSS rescoreEPSS 0.2% · 5th percentile
2026-10-09 20:05 UTCEPSS rescoreEPSS 0.2% · 5th percentile
2026-10-08 17:06 UTCEPSS rescoreEPSS 0.2% · 5th percentile
2026-10-07 23:46 UTCEPSS rescoreEPSS 0.2% · 5th percentile
2026-10-06 15:15 UTCEPSS rescoreEPSS 0.2% · 5th percentile
2026-10-05 17:41 UTCEPSS rescoreEPSS 0.2% · 5th percentile
2026-10-04 23:20 UTCEPSS rescoreEPSS 0.2% · 5th percentile
2026-10-03 14:23 UTCEPSS rescoreEPSS 0.2% · 5th percentile
2026-10-01 19:48 UTCEPSS rescoreEPSS 0.2% · 5th percentile
2026-09-30 16:36 UTCEG score recompute
2026-09-30 15:01 UTCEPSS rescoreEPSS 0.2% · 5th percentile
2026-09-28 13:49 UTCEPSS rescoreEPSS 0.2% · 5th percentile
2026-09-26 00:22 UTCEPSS rescoreEPSS 0.2% · 5th percentile
2026-09-24 14:01 UTCEPSS rescoreEPSS 0.2% · 5th percentile
2026-09-23 13:46 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-09-22 06:45 UTCOSV refresh
2026-09-20 20:14 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-09-18 19:26 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-09-16 14:06 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-09-16 05:11 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-09-15 03:08 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-09-13 16:45 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-09-12 14:58 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-09-11 14:51 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-09-11 09:34 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-09-08 21:58 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-09-07 15:59 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-09-06 13:46 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-09-05 15:26 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-09-04 13:58 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-09-04 05:04 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-09-03 03:59 UTCOSV refresh
2026-09-02 14:10 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-09-01 13:52 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-08-30 19:15 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-08-28 21:39 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-08-27 14:23 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-08-26 14:44 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-08-25 13:47 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-08-23 00:17 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-08-21 23:47 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-08-20 22:53 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-08-19 17:02 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-08-18 13:46 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-08-16 16:56 UTCOSV refresh
2026-08-16 14:54 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-08-16 02:12 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-08-15 01:28 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-08-13 21:58 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-08-12 13:49 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-08-11 13:40 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-08-10 23:58 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-08-09 13:44 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-08-08 16:35 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-08-07 16:25 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-08-06 13:45 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-08-05 19:15 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-08-04 10:36 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-08-03 10:34 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-08-02 02:25 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-08-01 10:36 UTCOSV refresh
2026-08-01 04:14 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-07-30 16:26 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-07-30 01:29 UTCEPSS rescoreEPSS 0.2% · 6th percentile

Same CWE

10 shown

CWE-667

Frequently asked(5)

What is CVE-2023-52516?

CVE-2023-52516 is a medium-severity vulnerability; its CVE record was published on March 2, 2024. In the Linux kernel, the following vulnerability has been resolved: dma-debug: don't call __dma_entry_alloc_check_leak() under free_entries_lock __dma_entry_alloc_check_leak() calls into printk -> serial console output (qcom geni) and grabs port->lock under free_entries_lock spin lock, which is a…

When was the CVE record for CVE-2023-52516 published?

The CVE record for CVE-2023-52516 was published on March 2, 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 December 11, 2024; the record at its source may have been updated since.

Is CVE-2023-52516 actively exploited?

CVE-2023-52516 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).

What is the CVSS score of CVE-2023-52516?

CVE-2023-52516 has a CVSS v3 base score of 5.5 (NVD).

How do I remediate CVE-2023-52516?

A fix for CVE-2023-52516 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-52516

Explore →

Is Your Infrastructure Affected by CVE-2023-52516?

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

Book a Demo →Browse All CVEs

CVE-2023-52516

📅 Published

🔄 Last Modified

🔗 References (5)