CVE-2023-54043

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2025-12-24. the CNA's CVSS baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

A fix is available — apply it.

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

iommufd: Do not add the same hwpt to the ioas->hwpt_list twice

The hwpt is added to the hwpt_list only during its creation, it is never added again. This hunk is some missed leftover from rework. Adding it twice will corrupt the linked list in some cases.

It effects HWPT specific attachment, which is something the test suite cannot cover until we can create a legitimate struct device with a non-system iommu "driver" (ie we need the bus removed from the iommu code)

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
44(Track)
EG Risk 44/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
8%
KEV
Not listed

Published

December 24, 2025

Last Modified

August 5, 2026

Advisory Details (2)

Auto-updated Aug 4, 2026
No patch confirmed yet.
generic

iommufd: Do not add the same hwpt to the ioas->hwpt_list twice - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b4ff830eca097df51af10a9be29e8cc817327919
generic

iommufd: Do not add the same hwpt to the ioas->hwpt_list twice - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c44adefdcf472f946f0632f4e0ddcbf3e00b8516

Vendor Advisories for CVE-2023-54043(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:5.14.0-362.8.1.el9_32023-11-07redhat
linuxKernel @ 6.2.3—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.

Data Freshness Timeline

(refreshed 7× in last 7d / 28× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 187 total refreshes for this CVE.

  1. 2026-09-18 19:26 UTCEPSS rescore
  2. 2026-09-16 14:06 UTCEPSS rescore
  3. 2026-09-16 05:11 UTCEPSS rescore
  4. 2026-09-16 05:11 UTCEPSS rescore
  5. 2026-09-15 03:08 UTCEPSS rescore
  6. 2026-09-14 05:49 UTCOSV refresh
  7. 2026-09-13 16:45 UTCEPSS rescore
  8. 2026-09-12 14:58 UTCEPSS rescore
  9. 2026-09-11 14:51 UTCEPSS rescore
  10. 2026-09-11 09:34 UTCEPSS rescore
  11. 2026-09-08 21:58 UTCEPSS rescore
  12. 2026-09-07 15:59 UTCEPSS rescore
  13. 2026-09-06 13:46 UTCEPSS rescore
  14. 2026-09-05 15:26 UTCEPSS rescore
  15. 2026-09-04 13:58 UTCEPSS rescore
  16. 2026-09-04 05:04 UTCEPSS rescore
  17. 2026-09-02 14:10 UTCEPSS rescore
  18. 2026-09-01 13:52 UTCEPSS rescore
  19. 2026-09-01 04:36 UTCEPSS rescore
  20. 2026-08-30 19:15 UTCEPSS rescore
  21. 2026-08-30 01:20 UTCEPSS rescore
  22. 2026-08-28 21:39 UTCEPSS rescore
  23. 2026-08-27 14:23 UTCEPSS rescore
  24. 2026-08-26 14:44 UTCEPSS rescore
  25. 2026-08-26 06:43 UTCOSV refresh
Show 75 more
  1. 2026-08-25 13:47 UTCEPSS rescore
  2. 2026-08-21 23:47 UTCEPSS rescore
  3. 2026-08-20 22:53 UTCEPSS rescore
  4. 2026-08-19 17:02 UTCEPSS rescore
  5. 2026-08-18 13:46 UTCEPSS rescore
  6. 2026-08-16 14:54 UTCEPSS rescore
  7. 2026-08-16 02:12 UTCEPSS rescore
  8. 2026-08-15 01:28 UTCEPSS rescore
  9. 2026-08-13 21:58 UTCEPSS rescore
  10. 2026-08-12 13:49 UTCEPSS rescore
  11. 2026-08-10 23:58 UTCEPSS rescore
  12. 2026-08-09 22:49 UTCEG score recompute
  13. 2026-08-09 22:49 UTCGHSA enrichment
  14. 2026-08-09 13:44 UTCEPSS rescore
  15. 2026-08-08 16:35 UTCEPSS rescore
  16. 2026-08-08 05:27 UTCEG score recompute
  17. 2026-08-08 05:27 UTCGHSA enrichment
  18. 2026-08-07 16:25 UTCEPSS rescore
  19. 2026-08-06 13:45 UTCEPSS rescore
  20. 2026-08-06 07:12 UTCEG score recompute
  21. 2026-08-06 07:12 UTCGHSA enrichment
  22. 2026-08-05 19:15 UTCEPSS rescore
  23. 2026-08-05 19:15 UTCEPSS rescore
  24. 2026-08-05 10:15 UTCEG score recompute
  25. 2026-08-05 10:15 UTCGHSA enrichment
  26. 2026-08-04 10:50 UTCEG score recompute
  27. 2026-08-04 10:50 UTCGHSA enrichment
  28. 2026-08-04 10:36 UTCEPSS rescore
  29. 2026-08-04 09:25 UTCEG score recompute▲ 8.80
  30. 2026-08-04 09:25 UTCGHSA enrichment
  31. 2026-08-04 09:20 UTCMITRE cvelistV5CVSS v3 → 8.8 · severity → HIGH
  32. 2026-08-03 10:34 UTCEPSS rescore
  33. 2026-08-02 02:25 UTCEPSS rescore
  34. 2026-08-02 02:25 UTCEPSS rescore
  35. 2026-08-01 04:14 UTCEPSS rescore
  36. 2026-07-30 16:26 UTCEPSS rescore
  37. 2026-07-30 01:29 UTCEPSS rescore
  38. 2026-07-28 15:34 UTCEPSS rescore
  39. 2026-07-28 15:34 UTCEPSS rescore
  40. 2026-07-27 03:39 UTCOSV refresh
  41. 2026-07-26 14:53 UTCEPSS rescore
  42. 2026-07-25 14:16 UTCEPSS rescore
  43. 2026-07-24 14:16 UTCEPSS rescore
  44. 2026-07-23 14:16 UTCEPSS rescore
  45. 2026-07-23 02:30 UTCEG score recompute
  46. 2026-07-22 23:16 UTCEG score recompute
  47. 2026-07-22 14:07 UTCEPSS rescore
  48. 2026-07-22 14:07 UTCEPSS rescore
  49. 2026-07-21 15:23 UTCEPSS rescore
  50. 2026-07-20 17:06 UTCEPSS rescore
  51. 2026-07-19 14:30 UTCEPSS rescore
  52. 2026-07-19 14:29 UTCEPSS rescore
  53. 2026-07-19 02:27 UTCEPSS rescore
  54. 2026-07-19 02:27 UTCEPSS rescore
  55. 2026-07-18 10:03 UTCEPSS rescore
  56. 2026-07-18 10:03 UTCEPSS rescore
  57. 2026-07-16 17:01 UTCEPSS rescore
  58. 2026-07-15 16:56 UTCEPSS rescore
  59. 2026-07-15 01:59 UTCEPSS rescore
  60. 2026-07-15 01:59 UTCEPSS rescore
  61. 2026-07-13 22:28 UTCEPSS rescore
  62. 2026-07-13 22:28 UTCEPSS rescore
  63. 2026-07-13 06:11 UTCEPSS rescore
  64. 2026-07-12 05:45 UTCEPSS rescore
  65. 2026-07-12 05:45 UTCEPSS rescore
  66. 2026-07-11 08:26 UTCEPSS rescore
  67. 2026-07-09 22:17 UTCOSV refresh
  68. 2026-07-09 19:08 UTCEPSS rescore
  69. 2026-07-08 15:13 UTCEPSS rescore
  70. 2026-07-07 13:45 UTCEPSS rescore
  71. 2026-07-07 13:44 UTCEPSS rescore
  72. 2026-07-06 16:26 UTCEPSS rescore
  73. 2026-07-06 16:26 UTCEPSS rescore
  74. 2026-07-06 02:22 UTCEPSS rescore
  75. 2026-07-06 02:22 UTCEPSS rescore

Frequently asked(5)

What is CVE-2023-54043?
CVE-2023-54043 is a high vulnerability published on December 24, 2025. In the Linux kernel, the following vulnerability has been resolved: iommufd: Do not add the same hwpt to the ioas->hwpt_list twice The hwpt is added to the hwpt_list only during its creation, it is never added again. This hunk is some missed leftover from rework. Adding it twice will corrupt the…
When was CVE-2023-54043 disclosed?
CVE-2023-54043 was first published in the National Vulnerability Database on December 24, 2025, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-54043 actively exploited?
CVE-2023-54043 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 91.8% of all scored CVEs.
What is the CVSS score of CVE-2023-54043?
CVE-2023-54043 has a CVSS v4.0 base score of 8.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2023-54043?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-54043, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2023-54043

Explore →

Is Your Infrastructure Affected by CVE-2023-54043?

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

Start Free Scan →Browse All CVEs