Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

Skip to content
cve.newCreate a CVE report
Check your stack
CVE-2026-43253

iommu/amd: move wait_on_sem() out of spinlock

Products / packages Linux

Published

Share

Severity and exploitation

Not in CISA KEV

KEV coverage does not rule out exploitation.

KEV checked 14/11/2026, 22:20:30 UTC
Linux · CVSS:3.1 · 7.5
Assessment vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Severity

high7.5

CVSS measures technical severity, not the likelihood of an attack.

Known exploitation

Not listed in the checked CISA KEV catalog

Absence from CISA KEV does not rule out attacks.

Public exploit

Not established by this record

Missing evidence does not mean no public exploit exists.

Remediation

Fix status not established

No structured fix or guidance is available here. Check the latest publisher advisory.

What this means

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

Source excerpt · Linux

Attack conditions

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.

Excerpt from the original source description below.

Review supporting sources →

Affected versions

Check the exact model, release, and any platform requirements against your installation.

Linux · Linux

Linux

6 ranges
Linux version evidence

Compare with this publisher’s ranges. This does not inspect your installation.

affected

4bf5beef578e46393f11eb69dda7d17a065e05ff → before 69d9339c02eddfc2a345be7220651068a3684383

git versions

4bf5beef578e46393f11eb69dda7d17a065e05ff → before f2f65b28d802a667119147444ec2ae33eebf9a58

git versions

4bf5beef578e46393f11eb69dda7d17a065e05ff → before 715c263119fd1b918a9fcbd8a36ea5b604a46324

git versions

4bf5beef578e46393f11eb69dda7d17a065e05ff → before e15768e68820142077bbca402d8e902f64ade1b0

git versions

4bf5beef578e46393f11eb69dda7d17a065e05ff → before 496269d12072ecb219826485bdbec70c92a8eef5

git versions

4bf5beef578e46393f11eb69dda7d17a065e05ff → before d2a0cac10597068567d336e85fa3cbdbe8ca62bf

git versions

unaffected

unknown

Other versions: unaffected

Linux · Linux

Linux

8 ranges
Linux version evidence

Compare with this publisher’s ranges. This does not inspect your installation.

affected

4.9

unaffected

0 → before 4.9

semver versions

6.1.191 → through 6.1.*

semver versions

6.6.128 → through 6.6.*

semver versions

6.12.75 → through 6.12.*

semver versions

6.18.16 → through 6.18.*

semver versions

6.19.6 → through 6.19.*

semver versions

7.0 → through *

original_commit_for_fix versions

unknown

Other versions: affected

Automatic dependency matching is unavailable for this record. Use the product evidence and publisher’s instructions to check your installation.

What to do

Compare your installed product and version with the affected versions above. A matching product name alone does not confirm exposure.

No structured fix or remediation guidance is available here. Check the full source description and vendor’s latest advisory for a patch or workaround; do not assume another version is safe.

cve.new guidance unless attributed to a publisher. This page does not inspect your installation.

Public exploit evidence

No public exploit reference is identified in the imported evidence. This is not a claim that no exploit exists.

Original source description

Read the full publisher 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.

References

6 sources
git.kernel.org/stable/c/69d9339c02eddfc2a345be7220651068a3684383
Source referenceLinux
git.kernel.org/stable/c/f2f65b28d802a667119147444ec2ae33eebf9a58
Source referenceLinux
git.kernel.org/stable/c/715c263119fd1b918a9fcbd8a36ea5b604a46324
Source referenceLinux
git.kernel.org/stable/c/e15768e68820142077bbca402d8e902f64ade1b0
Source referenceLinux
git.kernel.org/stable/c/496269d12072ecb219826485bdbec70c92a8eef5
Source referenceLinux
git.kernel.org/stable/c/d2a0cac10597068567d336e85fa3cbdbe8ca62bf
Source referenceLinux

Inside the record

Evidence available

Package identity · not supplied
Version evidence
Remediation guidance · not supplied
Weakness classification
Additional publishers

Describes the evidence in this view, not whether the product is safe.

Original records

CVE-2026-43253

View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.

cve.new JSON →

Underlying weaknesses

The source’s classification of what caused the vulnerability.

CWE-833 ↗

CWE-833 Deadlock

CISA-ADP

Related →

Environment requirements

These conditions apply together as specified by the publisher. A matching product name alone does not establish exposure.

Linux · platform conditions

Any condition may hold

Vulnerable product

cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

From (inclusive): 4.9

Before: 6.1.191

Vulnerable product

cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

From (inclusive): 4.9

Before: 6.6.128

Vulnerable product

cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

From (inclusive): 4.9

Before: 6.12.75

Vulnerable product

cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

From (inclusive): 4.9

Before: 6.18.16

Vulnerable product

cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

From (inclusive): 4.9

Before: 6.19.6

Vulnerable product

cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

From (inclusive): 4.9

Before: 7.0

Applicability preview
[
  {
    "nodes": [
      {
        "operator": "OR",
        "negate": false,
        "cpeMatch": [
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
            "versionStartIncluding": "4.9",
            "versionEndExcluding": "6.1.191"
          },
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
            "versionStartIncluding": "4.9",
            "versionEndExcluding": "6.6.128"
          },
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
            "versionStartIncluding": "4.9",
            "versionEndExcluding": "6.12.75"
          },
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
            "versionStartIncluding": "4.9",
            "versionEndExcluding": "6.18.16"
          },
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
            "versionStartIncluding": "4.9",
            "versionEndExcluding": "6.19.6"
          },
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
            "versionStartIncluding": "4.9",
            "versionEndExcluding": "7.0"
          }
        ]
      }
    ]
  }
]
Contributing organizations · 2
Linux

Assigning organization

2026-10-30
CISA-ADP

Additional data publisher

2026-10-19

Timeline

All times UTC

  1. Advisory published

    Publication date supplied by the source.

  2. Source updated

    Latest modification date supplied by the source.

  3. Last imported by cve.new

    Latest catalog import, not the date we first saw this advisory.

What changed

Follow changes
No substantive changes have been recorded here yet. History starts when cve.new observes a change after tracking is enabled; earlier edits are not reconstructed.

Large field values are marked as truncated previews. Original source snapshots remain retained.