CVE-2023-54060

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: Set end correctly when doing batch carry

Even though the test suite covers this it somehow became obscured that this wasn't working.

The test iommufd_ioas.mock_domain.access_domain_destory would blow up rarely.

end should be set to 1 because this just pushed an item, the carry, to the pfns list.

Sometimes the test would blow up with:

BUG: kernel NULL pointer dereference, address: 0000000000000000 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 0 P4D 0 Oops: 0000 [#1] SMP CPU: 5 PID: 584 Comm: iommufd Not tainted 6.5.0-rc1-dirty #1236 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 RIP: 0010:batch_unpin+0xa2/0x100 [iommufd] Code: 17 48 81 fe ff ff 07 00 77 70 48 8b 15 b7 be 97 e2 48 85 d2 74 14 48 8b 14 fa 48 85 d2 74 0b 40 0f b6 f6 48 c1 e6 04 48 01 f2 <48> 8b 3a 48 c1 e0 06 89 ca 48 89 de 48 83 e7 f0 48 01 c7 e8 96 dc RSP: 0018:ffffc90001677a58 EFLAGS: 00010246 RAX: 00007f7e2646f000 RBX: 0000000000000000 RCX: 0000000000000001 RDX: 0000000000000000 RSI: 00000000fefc4c8d RDI: 0000000000fefc4c RBP: ffffc90001677a80 R08: 0000000000000048 R09: 0000000000000200 R10: 0000000000030b98 R11: ffffffff81f3bb40 R12: 0000000000000001 R13: ffff888101f75800 R14: ffffc90001677ad0 R15: 00000000000001fe FS: 00007f9323679740(0000) GS:ffff8881ba540000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000000 CR3: 0000000105ede003 CR4: 00000000003706a0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: ? show_regs+0x5c/0x70 ? __die+0x1f/0x60 ? page_fault_oops+0x15d/0x440 ? lock_release+0xbc/0x240 ? exc_page_fault+0x4a4/0x970 ? asm_exc_page_fault+0x27/0x30 ? batch_unpin+0xa2/0x100 [iommufd] ? batch_unpin+0xba/0x100 [iommufd] __iopt_area_unfill_domain+0x198/0x430 [iommufd] ? __mutex_lock+0x8c/0xb80 ? __mutex_lock+0x6aa/0xb80 ? xa_erase+0x28/0x30 ? iopt_table_remove_domain+0x162/0x320 [iommufd] ? lock_release+0xbc/0x240 iopt_area_unfill_domain+0xd/0x10 [iommufd] iopt_table_remove_domain+0x195/0x320 [iommufd] iommufd_hw_pagetable_destroy+0xb3/0x110 [iommufd] iommufd_object_destroy_user+0x8e/0xf0 [iommufd] iommufd_device_detach+0xc5/0x140 [iommufd] iommufd_selftest_destroy+0x1f/0x70 [iommufd] iommufd_object_destroy_user+0x8e/0xf0 [iommufd] iommufd_destroy+0x3a/0x50 [iommufd] iommufd_fops_ioctl+0xfb/0x170 [iommufd] __x64_sys_ioctl+0x40d/0x9a0 do_syscall_64+0x3c/0x80 entry_SYSCALL_64_after_hwframe+0x46/0xb0

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: Set end correctly when doing batch carry - kernel/git/stable/linux.git - Linux kernel stable tree

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

iommufd: Set end correctly when doing batch carry - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/176f36a376c417b58d19f79edfce20db9317eaa2

Vendor Advisories for CVE-2023-54060(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-427.13.1.el9_42024-04-30redhat
linuxKernel @ 6.4.8—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

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux—6.4.11-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux—6.4.11-1—

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2023-54060?
CVE-2023-54060 is a high vulnerability published on December 24, 2025. In the Linux kernel, the following vulnerability has been resolved: iommufd: Set end correctly when doing batch carry Even though the test suite covers this it somehow became obscured that this wasn't working. The test iommufdioas.mockdomain.accessdomaindestory would blow up rarely. end should be…
When was CVE-2023-54060 disclosed?
CVE-2023-54060 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-54060 actively exploited?
CVE-2023-54060 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 92.3% of all scored CVEs.
What is the CVSS score of CVE-2023-54060?
CVE-2023-54060 has a CVSS v4.0 base score of 8.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2023-54060?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-54060, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-54060

Explore →

Is Your Infrastructure Affected by CVE-2023-54060?

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

Start Free Scan →Browse All CVEs