CVE-2026-97441

ata: ahci: fail probe if BAR too small for claimed ports

N/A
Published: September 24, 2026 at 04:03 PM UTC
Updated: October 3, 2026 at 11:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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]

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.6.12 ≤ v < 5.10.2712.6.12 ≤ v < 5.15.2222.6.12 ≤ v < 6.1.1892.6.12 ≤ v < 6.12.1112.6.12 ≤ v < 6.18.532.6.12 ≤ v < 6.6.1582.6.12 ≤ v < 7.21da177e4c3f41524e886b7f1b8a0c1fc7321cac22.6.12
Vendor states this is fixed in 533a08ea11217100cec7a0ed903cb9b9c892d6f1 (fixed)
Vendor states this is fixed in 6d29b91164424256a759ddabc8f2de1ae09bd3f1 (fixed)
Vendor states this is fixed in c4086c6e1af757e1ff26fa2d2926b3ec0195de79 (fixed)
Vendor states this is fixed in c717b20100ef8cd06b5237af70ea2cb692e058ce (fixed)
Vendor states this is fixed in df262c828b616450eb351349e91c63447551bd01 (fixed)
Vendor states this is fixed in f2e291043c37a896d7f9797e25a356dceb030177 (fixed)
Vendor states this is fixed in ff0ab535f8febbd32afa5832f8d2d9b06a8d5060 (fixed)
Vendor states this is fixed in 2.6.12 (unaffected)
Vendor states this is fixed in 5.10.271 (unaffected)
Vendor states this is fixed in 5.15.222 (unaffected)
Vendor states this is fixed in 6.1.189 (unaffected)
Vendor states this is fixed in 6.12.111 (unaffected)
Vendor states this is fixed in 6.18.53 (unaffected)
Vendor states this is fixed in 6.6.158 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card