CVE-2026-43253

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-05-06. NVD baseline CVSS 7.5; sources differ by 0.0.

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

A fix is available — apply it.

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

iommu/amd: move wait_on_sem() out of spinlock

With iommu.strict=1, the existing completion wait path can cause soft lockups under stressed environment, as wait_on_sem() busy-waits under the spinlock with interrupts disabled.

Move the completion wait in iommu_completion_wait() out of the spinlock. wait_on_sem() only polls the hardware-updated cmd_sem and does not require iommu->lock, so holding the lock during the busy wait unnecessarily increases contention and extends the time with interrupts disabled.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
38(Track)
EG Risk 38/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
Severity75% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
28%
KEV
Not listed

Published

May 6, 2026

Last Modified

August 5, 2026

Advisory Details (5)

Auto-updated May 11, 2026
No patch confirmed yet.
generic

iommu/amd: move wait_on_sem() out of spinlock - kernel/git/stable/linux.git - Linux kernel stable tree

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

iommu/amd: move wait_on_sem() out of spinlock - kernel/git/stable/linux.git - Linux kernel stable tree

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

iommu/amd: move wait_on_sem() out of spinlock - kernel/git/stable/linux.git - Linux kernel stable tree

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

iommu/amd: move wait_on_sem() out of spinlock - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/715c263119fd1b918a9fcbd8a36ea5b604a46324
generic

iommu/amd: move wait_on_sem() out of spinlock - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/496269d12072ecb219826485bdbec70c92a8eef5

Patch Availability(13)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-realtime-hwe-22.04 (6.8.1-1055.56~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1058.61.1) @ noble2026-08-23ubuntu
ubuntulinux-tools-lowlatency-hwe-22.04-edge (6.8.0-134.134.1~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1029.30) @ noble2026-08-23ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1032.33) @ noble2026-08-23ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2049.50) @ noble2026-08-23ubuntu
ubuntulinux-tools-raspi-6.8 (6.8.0-1060.64) @ noble2026-08-23ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-134.134+fips1) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-08-23ubuntu
linuxKernel @ 6.6.128—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)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (350 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (116 versions)6.19.6-1—

Weakness Classification(1)

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

All Vendor Advisories

(12)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 5× in last 7d / 27× 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 228 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-43253?
CVE-2026-43253 is a high vulnerability published on May 6, 2026. In the Linux kernel, the following vulnerability has been resolved: iommu/amd: move waitonsem() out of spinlock With iommu.strict=1, the existing completion wait path can cause soft lockups under stressed environment, as waitonsem() busy-waits under the spinlock with interrupts disabled. Move the…
When was CVE-2026-43253 disclosed?
CVE-2026-43253 was first published in the National Vulnerability Database on May 6, 2026, 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-2026-43253 actively exploited?
CVE-2026-43253 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 72.4% of all scored CVEs.
What is the CVSS score of CVE-2026-43253?
CVE-2026-43253 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-43253?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43253, 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-2026-43253

Explore →

Is Your Infrastructure Affected by CVE-2026-43253?

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

Start Free Scan →Browse All CVEs