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-68449ata: sata_dwc_460ex: fix infinite loop in NCQ tag completion bit-scanning

Description

In the Linux kernel, the following vulnerability has been resolved: ata: sata_dwc_460ex: fix infinite loop in NCQ tag completion bit-scanning The hand-rolled bit-scanning loop in the NCQ completion path has an infinite loop bug. When tag_mask has only high bits set (e.g. 0x80000000), the inner while loop left-shifts tag_mask until it overflows to 0. At that point !(0 & 1) is always true and 0 <<= 1 stays 0, causing an infinite loop in hardirq context with a spinlock held. Replace the open-coded bit-scanning with __ffs() which correctly finds the least significant set bit and is bounded by the width of the argument.

Timeline

  1. ID reserved

    By Linux

  2. · 13 days later

    Published

  3. · 3 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.17% · top 94% of all CVEs (14 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 62936009f35a6659cc3ebe0d90c754182d60da73 – < ea9fa4dabe476f85fe73df30a6ab61a23c22fda4
    • affected 62936009f35a6659cc3ebe0d90c754182d60da73 – < d72e8089dc332ac48293512ef0de77cbe0e04d25
    • affected 62936009f35a6659cc3ebe0d90c754182d60da73 – < 90e8cf489b593814b9398aa187ddbb790e33ec6f
    • affected 62936009f35a6659cc3ebe0d90c754182d60da73 – < 4c6e64cae2b2dab32ad9099faa339f6a72c0ce16
    • affected 62936009f35a6659cc3ebe0d90c754182d60da73 – < 8c5de0d8ab6824cfdadcbbe1be4c6c9d9f4c1f80
    • affected 62936009f35a6659cc3ebe0d90c754182d60da73 – < 1842d45f461a78988254631893329bdf4596e954
    • affected 62936009f35a6659cc3ebe0d90c754182d60da73 – < 29b916d3556bd12a95be7c56ca391b8cd572f8be
    • affected 62936009f35a6659cc3ebe0d90c754182d60da73 – < c2130f6553f4a5cbdc259de069600117a995f197
  • Linux · Linux

    • affected 2.6.36
    • unaffected < 2.6.36
    • unaffected 5.10.265 – ≤ 5.10.*
    • unaffected 5.15.216 – ≤ 5.15.*
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.148 – ≤ 6.6.*
    • unaffected 6.12.101 – ≤ 6.12.*
    • unaffected 6.18.42 – ≤ 6.18.*
    • unaffected 7.1.6 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .