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-93086

firmware: arm_scmi: Avoid IDR updates while cleaning channels

Products / packages Linux

Published

Share

Severity and exploitation

Not in CISA KEVNo CVSS score

KEV coverage does not rule out exploitation.

KEV checked 14/11/2026, 20:55:32 UTC

Severity

unknown

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

No attack-condition excerpt has been identified here. Review the full source description and references for authentication, network access, and configuration requirements.

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

22f7f35fd71b597a5d916e41d7646be6ee530c86 → before f50698c617350a6e2064dffd6cff3f391e142f55

git versions

05a2801d8b90c1b5159618d4bd3a3c65d60f3ff1 → before aed24a3c63920539e9de7fbfe7929a2e7c888cd2

git versions

05a2801d8b90c1b5159618d4bd3a3c65d60f3ff1 → before 431c6b872ba7fedcc5a3afb0ec3517db4d95d088

git versions

05a2801d8b90c1b5159618d4bd3a3c65d60f3ff1 → before 54e5a4f7d83db4552d963d0785be32d9df680dcd

git versions

05a2801d8b90c1b5159618d4bd3a3c65d60f3ff1 → before bab26acebe55e8ad3ab545abda72faa7ca28c477

git versions

05a2801d8b90c1b5159618d4bd3a3c65d60f3ff1 → before c38b1e19485aaa820e52cfe162525a8af67563da

git versions

unaffected

unknown

Other versions: unaffected

Linux · Linux

Linux

7 ranges
Linux version evidence

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

affected

6.3

unaffected

0 → before 6.3

semver versions

6.6.157 → through 6.6.*

semver versions

6.12.110 → through 6.12.*

semver versions

6.18.52 → through 6.18.*

semver versions

7.2.6 → through 7.2.*

semver versions

7.3 → 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:

firmware: arm_scmi: Avoid IDR updates while cleaning channels

scmi_cleanup_channels() walks the TX/RX channel IDRs with idr_for_each() to free transport resources and destroy the dedicated transport devices before calling idr_destroy().

The destroy callback removed each entry from the same IDR being walked. That is not needed for this cleanup path, and it is unsafe because idr_for_each() has not advanced its radix-tree iterator while the callback is running. Removing the current entry from the callback can invalidate the iterator state. The callback also cannot be protected by rcu_read_lock(), because scmi_device_destroy() may sleep.

Leave IDR teardown to the following idr_destroy() call and keep the callback limited to device destruction.

References

6 sources
git.kernel.org/stable/c/f50698c617350a6e2064dffd6cff3f391e142f55
Source referenceLinux
git.kernel.org/stable/c/aed24a3c63920539e9de7fbfe7929a2e7c888cd2
Source referenceLinux
git.kernel.org/stable/c/431c6b872ba7fedcc5a3afb0ec3517db4d95d088
Source referenceLinux
git.kernel.org/stable/c/54e5a4f7d83db4552d963d0785be32d9df680dcd
Source referenceLinux
git.kernel.org/stable/c/bab26acebe55e8ad3ab545abda72faa7ca28c477
Source referenceLinux
git.kernel.org/stable/c/c38b1e19485aaa820e52cfe162525a8af67563da
Source referenceLinux

Inside the record

Evidence available

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

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

Original records

CVE-2026-93086

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

cve.new JSON →

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): 6.3

Before: 6.6.157

Vulnerable product

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

From (inclusive): 6.3

Before: 6.12.110

Vulnerable product

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

From (inclusive): 6.3

Before: 6.18.52

Vulnerable product

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

From (inclusive): 6.3

Before: 7.2.6

Vulnerable product

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

From (inclusive): 6.3

Before: 7.3

Applicability preview
[
  {
    "nodes": [
      {
        "operator": "OR",
        "negate": false,
        "cpeMatch": [
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
            "versionStartIncluding": "6.3",
            "versionEndExcluding": "6.6.157"
          },
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
            "versionStartIncluding": "6.3",
            "versionEndExcluding": "6.12.110"
          },
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
            "versionStartIncluding": "6.3",
            "versionEndExcluding": "6.18.52"
          },
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
            "versionStartIncluding": "6.3",
            "versionEndExcluding": "7.2.6"
          },
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
            "versionStartIncluding": "6.3",
            "versionEndExcluding": "7.3"
          }
        ]
      }
    ]
  }
]
Contributing organizations · 1
Linux

Assigning organization

2026-10-30

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.