Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-43253iommu/amd: move wait_on_sem() out of spinlock

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 5 days later

    Published

  3. · 6 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-43253, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVDNVD · Modified3.1High7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.37% · top 69% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: yes · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.5.

Affected products

  • Linux · Linux

    • affected 4bf5beef578e46393f11eb69dda7d17a065e05ff – < 69d9339c02eddfc2a345be7220651068a3684383
    • affected 4bf5beef578e46393f11eb69dda7d17a065e05ff – < f2f65b28d802a667119147444ec2ae33eebf9a58
    • affected 4bf5beef578e46393f11eb69dda7d17a065e05ff – < 715c263119fd1b918a9fcbd8a36ea5b604a46324
    • affected 4bf5beef578e46393f11eb69dda7d17a065e05ff – < e15768e68820142077bbca402d8e902f64ade1b0
    • affected 4bf5beef578e46393f11eb69dda7d17a065e05ff – < 496269d12072ecb219826485bdbec70c92a8eef5
    • affected 4bf5beef578e46393f11eb69dda7d17a065e05ff – < d2a0cac10597068567d336e85fa3cbdbe8ca62bf
  • Linux · Linux

    • affected 4.9
    • unaffected < 4.9
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.128 – ≤ 6.6.*
    • unaffected 6.12.75 – ≤ 6.12.*
    • unaffected 6.18.16 – ≤ 6.18.*
    • unaffected 6.19.6 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-43253 badge
[![CVE-2026-43253](https://cveledger.app/badge/CVE-2026-43253.svg)](https://cveledger.app/cve/CVE-2026-43253)

Record last updated .