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-97441ata: ahci: fail probe if BAR too small for claimed ports

Description

In the Linux kernel, the following vulnerability has been resolved: ata: ahci: fail probe if BAR too small for claimed ports When an AHCI controller is disabled in BIOS, its HOST_CAP register may contain a bogus value, e.g. 0xFFFFFFFF. Since CAP.NP (Number of Ports) is a zeroes based 5-bit register field, a value of 0x1f means 32 ports. If CAP.NP claims more ports than can physically fit within the mapped BAR region, accessing port registers beyond the BAR boundary causes a kernel panic. Add validation in ahci_init_one() to check that the BAR size is sufficient for the number of ports claimed in CAP.NP. The check calculates the required MMIO size as: required_size = 0x100 (global registers) + max_ports * 0x80 If required_size exceeds the actual BAR size, the probe fails with -ENODEV, preventing the panic and providing a clear error message. [cassel: commit log]

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 9 days 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 93% of all CVEs (12 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 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 533a08ea11217100cec7a0ed903cb9b9c892d6f1
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < c717b20100ef8cd06b5237af70ea2cb692e058ce
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < ff0ab535f8febbd32afa5832f8d2d9b06a8d5060
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 6d29b91164424256a759ddabc8f2de1ae09bd3f1
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < df262c828b616450eb351349e91c63447551bd01
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < f2e291043c37a896d7f9797e25a356dceb030177
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < c4086c6e1af757e1ff26fa2d2926b3ec0195de79
  • Linux · Linux

    • affected 2.6.12
    • unaffected < 2.6.12
    • unaffected 5.10.271 – ≤ 5.10.*
    • unaffected 5.15.222 – ≤ 5.15.*
    • unaffected 6.1.189 – ≤ 6.1.*
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.111 – ≤ 6.12.*
    • unaffected 6.18.53 – ≤ 6.18.*
    • unaffected 7.2 – ≤ *

References

References7

Sources

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

Badge for a README or a ticket

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

Record last updated .