PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-80945 Linux CVE debrief

A vulnerability in the Linux kernel's crypto: iaa component has been resolved. On a hardware analytics error, decompress retries through the software fallback, which writes req->dst with the CPU while it is still mapped DMA_FROM_DEVICE. With SWIOTLB active, the later dma_unmap_sg() copies the stale bounce buffer over req->dst, corrupting the result. Unmap before the fallback runs.

Vendor
Linux
Product
Unknown
CVSS
CRITICAL 9.1
CISA KEV
Not listed in stored evidence
Original CVE published
2026-09-11
Original CVE updated
2026-10-19
Advisory published
2026-09-11
Advisory updated
2026-10-19

Who should care

Linux kernel maintainers, users, and administrators should assess exposure and apply patches to prevent potential data corruption. Affected operator, platform, vulnerability-management, and security-team impact should be evaluated. Linux kernel deployments require verification of affected versions and systems, and users should review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.

Why it matters

CVE-2026-80945 is a critical vulnerability in the Linux kernel that can cause data corruption. Linux kernel maintainers and users should assess exposure and apply patches to prevent potential data corruption.

  • Potential data corruption in Linux kernel deployments
  • Need for patching to prevent data corruption
  • Verification of affected versions and systems required
  • Monitoring system logs for potential issues

Technical summary

The Linux kernel's crypto: iaa component has a vulnerability that can cause data corruption on hardware analytics errors. The issue arises when decompress retries occur through the software fallback, which writes req->dst with the CPU while it is still mapped DMA_FROM_DEVICE. With SWIOTLB active, the later dma_unmap_sg() copies the stale bounce buffer over req->dst, corrupting the result. The vulnerability is resolved by unmapping dst before software fallback on decompress. Linux kernel maintainers and users should assess exposure and apply patches to prevent potential data corruption.

Defensive priority

High priority for Linux kernel maintainers and users to assess exposure and apply patches.

Recommended defensive actions

  • Assess exposure of Linux kernel deployments to CVE-2026-80945
  • Verify and apply patches from Linux kernel maintainers
  • Monitor system logs for potential data corruption
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • 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 the scope of affected versions and systems requires verification from the supplied official sources. Linux kernel maintainers and users should verify the official advisory for specific patch guidance and assess exposure to CVE-2026-80945. The vulnerability affects Linux kernel deployments, and users should check relevant monitoring, detection, and logs for exposed assets that need extra review.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-80945 CVE Program record

    Publisher, destination, and source semantics verified

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

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

  • CVE-2026-80945 NVD vulnerability detail

    Publisher, destination, and source semantics verified

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

    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/94a25930477113730372e0fa2985da4c5ac95c9a

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

  • Source reference

    Unverified legacy reference

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

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

  • Source reference

    Unverified legacy reference

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

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

  • Source reference

    Unverified legacy reference

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

    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.