PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-93170 Linux CVE debrief

A race condition in the Linux kernel's dmaengine xilinx_dma AXIDMA and MCDMA interrupt handlers could lead to incorrect channel idle state management. This results in spurious transfers and potential descriptor corruption or missed completions, affecting system stability and potentially leading to denial of service. Linux kernel maintainers and users should assess exposure and verify the presence of the fix to mitigate these risks. The issue arises from a race condition when multiple descriptors are queued and active, an interrupt fires after completing some descriptors, and the channel is marked idle even though active_list still contains unprocessed descriptors.

Vendor
Linux
Product
Unknown
CVSS
HIGH 7.8
CISA KEV
Not listed in stored evidence
Original CVE published
2026-09-17
Original CVE updated
2026-09-18
Advisory published
2026-09-17
Advisory updated
2026-09-18

Who should care

Linux kernel maintainers, users, and administrators should assess exposure and verify the presence of the fix, as the vulnerability could lead to system instability or denial of service.

Why it matters

CVE-2026-93170 is a vulnerability in the Linux kernel's dmaengine xilinx_dma AXIDMA and MCDMA interrupt handlers that could lead to incorrect channel idle state management, causing spurious transfers and potential descriptor corruption or missed completions. Linux kernel maintainers and users should assess exposure and verify the presence of the fix.

  • Verify Linux kernel versions and configurations for exposure to the vulnerability
  • Assess the risk of system instability or denial of service due to incorrect channel idle state management
  • Monitor system logs for signs of spurious transfers or descriptor corruption
  • Prioritize verification of the fix in the Linux kernel codebase

Technical summary

The Linux kernel's dmaengine xilinx_dma AXIDMA and MCDMA interrupt handlers have a race condition that could lead to incorrect channel idle state management. This occurs when multiple descriptors are queued and active, an interrupt fires after completing some descriptors, and the channel is marked idle even though active_list still contains unprocessed descriptors. This results in spurious transfers and potential descriptor corruption or missed completions. The issue has been resolved in the Linux kernel codebase, but specific affected or fixed versions are not detailed in the CVE record or NVD entry.

Defensive priority

Linux kernel maintainers and users should assess exposure and verify the presence of the fix, as the vulnerability could lead to system instability or denial of service.

Recommended defensive actions

  • Review Linux kernel versions and configurations for exposure to the vulnerability
  • Verify the presence of the fix in the Linux kernel codebase
  • Monitor system logs for signs of spurious transfers or descriptor corruption
  • Assess the risk of system instability or denial of service due to incorrect channel idle state management
  • Prioritize verification of the fix in the Linux kernel codebase
  • Track exceptions and retest remediated assets
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, but do not specify affected or fixed versions. The Linux kernel community has resolved the issue. Defenders should verify Linux kernel versions and configurations for exposure, assess the risk of system instability or denial of service, and monitor system logs for signs of spurious transfers or descriptor corruption. Evidence is limited to CVE and NVD entries, with additional details from Linux kernel commit records.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-93170 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-93170

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-93170 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-93170

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/0b6d055edb55ecadadf54e930c2b4fab76fa9a5a

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/425630e9eea1f9f8912b8c6abf01e0dab1e27917

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/5459e02707b27a964ae72e028d3ff72a3b687c4a

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/7f4b989d7d87381927b98d64492f8dcf979f57ab

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/c27d16fd2358b2fc3e1ffaca03afd11dc28630ea

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/c3e943490ced0b9ad475844eda7661f6a9bcfb4a

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/ec927657524be4438447944a58173c7baf7f2384

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/fdaf297ab275c6efecac5e87669c31bc89b74297

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.