CVE-2023-52484

MEDIUMNVD 5.55.5

Also known asEUVD-2023-57109 (ENISA EUVD) · GHSA-6vr7-4hpq-76r6 (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:

iommu/arm-smmu-v3: Fix soft lockup triggered by arm_smmu_mm_invalidate_range

When running an SVA case, the following soft lockup is triggered: -------------------------------------------------------------------- watchdog: BUG: soft lockup - CPU#244 stuck for 26s! pstate: 83400009 (Nzcv daif +PAN -UAO +TCO +DIT -SSBS BTYPE=--) pc : arm_smmu_cmdq_issue_cmdlist+0x178/0xa50 lr : arm_smmu_cmdq_issue_cmdlist+0x150/0xa50 sp : ffff8000d83ef290 x29: ffff8000d83ef290 x28: 000000003b9aca00 x27: 0000000000000000 x26: ffff8000d83ef3c0 x25: da86c0812194a0e8 x24: 0000000000000000 x23: 0000000000000040 x22: ffff8000d83ef340 x21: ffff0000c63980c0 x20: 0000000000000001 x19: ffff0000c6398080 x18: 0000000000000000 x17: 0000000000000000 x16: 0000000000000000 x15: ffff3000b4a3bbb0 x14: ffff3000b4a30888 x13: ffff3000b4a3cf60 x12: 0000000000000000 x11: 0000000000000000 x10: 0000000000000000 x9 : ffffc08120e4d6bc x8 : 0000000000000000 x7 : 0000000000000000 x6 : 0000000000048cfa x5 : 0000000000000000 x4 : 0000000000000001 x3 : 000000000000000a x2 : 0000000080000000 x1 : 0000000000000000 x0 : 0000000000000001 Call trace: arm_smmu_cmdq_issue_cmdlist+0x178/0xa50 __arm_smmu_tlb_inv_range+0x118/0x254 arm_smmu_tlb_inv_range_asid+0x6c/0x130 arm_smmu_mm_invalidate_range+0xa0/0xa4 __mmu_notifier_invalidate_range_end+0x88/0x120 unmap_vmas+0x194/0x1e0 unmap_region+0xb4/0x144 do_mas_align_munmap+0x290/0x490 do_mas_munmap+0xbc/0x124 __vm_munmap+0xa8/0x19c __arm64_sys_munmap+0x28/0x50 invoke_syscall+0x78/0x11c el0_svc_common.constprop.0+0x58/0x1c0 do_el0_svc+0x34/0x60 el0_svc+0x2c/0xd4 el0t_64_sync_handler+0x114/0x140 el0t_64_sync+0x1a4/0x1a8 --------------------------------------------------------------------

Note that since 6.6-rc1 the arm_smmu_mm_invalidate_range above is renamed to "arm_smmu_mm_arch_invalidate_secondary_tlbs", yet the problem remains.

The commit 06ff87bae8d3 ("arm64: mm: remove unused functions and variable protoypes") fixed a similar lockup on the CPU MMU side. Yet, it can occur to SMMU too, since arm_smmu_mm_arch_invalidate_secondary_tlbs() is called typically next to MMU tlb flush function, e.g. tlb_flush_mmu_tlbonly { tlb_flush { __flush_tlb_range { // check MAX_TLBI_OPS } } mmu_notifier_arch_invalidate_secondary_tlbs { arm_smmu_mm_arch_invalidate_secondary_tlbs { // does not check MAX_TLBI_OPS } } }

Clone a CMDQ_MAX_TLBI_OPS from the MAX_TLBI_OPS in tlbflush.h, since in an SVA case SMMU uses the CPU page table, so it makes sense to align with the tlbflush code. Then, replace per-page TLBI commands with a single per-asid TLBI command, if the request size hits this threshold.

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

February 29, 2024

Last Modified

December 10, 2024

References (4)

CVE Programhttps://git.kernel.org/stable/c/3283a1bce9bbc978059f790b84f3c10c32492429Patch
CVE Programhttps://git.kernel.org/stable/c/d5afb4b47e13161b3f33904d45110f9e6463bad6Patch
CVE Programhttps://git.kernel.org/stable/c/f5a604757aa8e37ea9c7011dc9da54fa1b30f29bPatch
CVE Programhttps://git.kernel.org/stable/c/f90f4c562003ac3d3b135c5a40a5383313f27264Patch

Patch Availability(1)

Vendor / Ecosystem	Fix (by version range) / Patch	Released	Source
linux	Kernel @ 5.15.134 (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)

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 / 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 92 of 200 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 108 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

2026-11-02 16:40 UTCEPSS rescoreEPSS 0.2% · 6th percentile
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-6vr7-4hpq-76r6 · 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-17 16:30 UTCEPSS rescoreEPSS 0.2% · 6th percentile
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

Show 67 more

2026-10-12 18:13 UTCEG score recompute
2026-10-12 16:31 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-10-11 21:54 UTCOSV refresh
2026-10-11 21:38 UTCEG score recompute
2026-10-11 13:45 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-10-10 19:58 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-10-09 20:05 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-10-08 17:06 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-10-07 23:46 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-10-06 15:15 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-10-05 17:41 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-10-04 23:20 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-10-03 14:23 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-10-01 19:48 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-09-30 16:36 UTCEG score recompute
2026-09-30 15:01 UTCEPSS rescoreEPSS 0.2% · 6th percentile
2026-09-29 15:17 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% · 7th percentile
2026-09-22 06:46 UTCOSV refresh
2026-09-20 20:14 UTCEPSS rescoreEPSS 0.2% · 7th percentile
2026-09-18 19:26 UTCEPSS rescoreEPSS 0.2% · 7th percentile
2026-09-16 14:06 UTCEPSS rescoreEPSS 0.2% · 7th 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 04:29 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-30 01:20 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% · 7th percentile
2026-08-21 23:47 UTCEPSS rescoreEPSS 0.2% · 7th percentile
2026-08-20 22:53 UTCEPSS rescoreEPSS 0.2% · 7th percentile
2026-08-19 17:02 UTCEPSS rescoreEPSS 0.2% · 7th percentile
2026-08-16 17:26 UTCOSV refresh
2026-08-16 14:54 UTCEPSS rescoreEPSS 0.2% · 7th 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 11:06 UTCOSV refresh

Same CWE

10 shown

CWE-667

Frequently asked(5)

What is CVE-2023-52484?

CVE-2023-52484 is a medium-severity vulnerability; its CVE record was published on February 29, 2024. In the Linux kernel, the following vulnerability has been resolved: iommu/arm-smmu-v3: Fix soft lockup triggered by arm_smmu_mm_invalidate_range When running an SVA case, the following soft lockup is triggered: -------------------------------------------------------------------- watchdog: BUG: soft…

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

The CVE record for CVE-2023-52484 was published on February 29, 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 10, 2024; the record at its source may have been updated since.

Is CVE-2023-52484 actively exploited?

CVE-2023-52484 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-52484?

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

How do I remediate CVE-2023-52484?

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

Explore →

Is Your Infrastructure Affected by CVE-2023-52484?

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

Book a Demo →Browse All CVEs

CVE-2023-52484

📅 Published

🔄 Last Modified

🔗 References (4)