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
Trending — 3 sources updated this week
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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
26.5%
KEV
Not listed

Published

May 6, 2026

Last Modified

May 11, 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(1)

Vendor / EcosystemFixed in / PatchReleasedSource
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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 32× 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 112 total refreshes for this CVE.

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

Related CVEs(same product + same CWE)

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 May 11, 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 26.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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

Explore the affected products and dependency analysis for 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