CVE-2026-98262ata: libahci: clear PxCLBU and PxFBU for AHCI_HFLAG_32BIT_ONLY
- —Not scoredno CVSS score yet
- 0.18%Exploitation in 30 daysEPSS · top 93% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: ata: libahci: clear PxCLBU and PxFBU for AHCI_HFLAG_32BIT_ONLY A user reported that commit 105c42566a55 ("ata: ahci: force 32-bit DMA for JMicron JMB582/JMB585") made the JMicron JMB585 unusable on his board. The failure is seen as soon as the ahci driver is probed, and booting with iommu=off does not solve the problem. Looking at the AHCI specification, PxCLBU and PxFBU are both read only '0' for HBAs that do not support 64-bit addressing. For HBAs that do support 64-bit addressing, the registers are read write, with a reset value that is Implementation Specific. When using the AHCI_HFLAG_32BIT_ONLY flag, the HBA does support 64-bit addressing, and a 32-bit DMA mask is set by simply clearing HOST_CAP_64. Thus, in this case, we need to explicitly clear the registers to 0.
Timeline
ID reserved
By Linux
- 11 days later
· 11 days later
Published
- 13 days later
· 13 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.18% · top 93% of all CVEs (12 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected c7a42156d99bcea7f8173ba7a6034bbaa2ecb77c – < 0191c9ff23ef1678dbfb5ad253a2dee92feb5d71
- affected c7a42156d99bcea7f8173ba7a6034bbaa2ecb77c – < 8f510f68208a1f673d7c7234a687be4671490e9c
- affected c7a42156d99bcea7f8173ba7a6034bbaa2ecb77c – < 4719424bb7cb9f20b73986bcb72dd528f0e5c6eb
- affected c7a42156d99bcea7f8173ba7a6034bbaa2ecb77c – < a5a8b4737f68bbac8aa0685af0c8921e6003c22b
- affected c7a42156d99bcea7f8173ba7a6034bbaa2ecb77c – < b28a17d4a9bb0aa38b48681c3927b012ba40eabe
- affected c7a42156d99bcea7f8173ba7a6034bbaa2ecb77c – < b691a3e244278362e552439d6d3ee5a5d3703488
- affected c7a42156d99bcea7f8173ba7a6034bbaa2ecb77c – < 7912ad8fb5233bb8cfe21d50df639c7f4854ff9d
- affected c7a42156d99bcea7f8173ba7a6034bbaa2ecb77c – < 82e47533221d4746947b74d2e79a478c36c6433a
- affected 2.6.22
- unaffected < 2.6.22
- 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.112 – ≤ 6.12.*
- unaffected 6.18.54 – ≤ 6.18.*
- unaffected 7.2.8 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References8
- https://git.kernel.org/stable/c/0191c9ff23ef1678dbfb5ad253a2dee92feb5d71 (opens in a new tab)
- https://git.kernel.org/stable/c/8f510f68208a1f673d7c7234a687be4671490e9c (opens in a new tab)
- https://git.kernel.org/stable/c/4719424bb7cb9f20b73986bcb72dd528f0e5c6eb (opens in a new tab)
- https://git.kernel.org/stable/c/a5a8b4737f68bbac8aa0685af0c8921e6003c22b (opens in a new tab)
- https://git.kernel.org/stable/c/b28a17d4a9bb0aa38b48681c3927b012ba40eabe (opens in a new tab)
- https://git.kernel.org/stable/c/b691a3e244278362e552439d6d3ee5a5d3703488 (opens in a new tab)
- https://git.kernel.org/stable/c/7912ad8fb5233bb8cfe21d50df639c7f4854ff9d (opens in a new tab)
- https://git.kernel.org/stable/c/82e47533221d4746947b74d2e79a478c36c6433a (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-93190 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-98262)Record last updated .