Storage unavailability via uncleared AHCI DMA registers
Published Oct 6, 2026 · Updated Oct 6, 2026
AHCI initialization failure in Linux kernels using the 32-bit-only DMA quirk makes affected JMicron JMB585 storage unavailable at driver probe. In ahci_start_fis_rx, libahci masks 64-bit DMA capability but leaves the writable PxCLBU and PxFBU upper address registers at hardware-specific reset values instead of zero. The condition requires a 64-bit-capable AHCI controller forced to 32-bit DMA; it is a local hardware compatibility failure, not a demonstrated remote attack.
Summary
What happened
AHCI initialization failure in Linux kernels using the 32-bit-only DMA quirk makes affected JMicron JMB585 storage unavailable at driver probe. In ahci_start_fis_rx, libahci masks 64-bit DMA capability but leaves the writable PxCLBU and PxFBU upper address registers at hardware-specific reset values instead of zero. The condition requires a 64-bit-capable AHCI controller forced to 32-bit DMA; it is a local hardware compatibility failure, not a demonstrated remote attack.
The record
- CVE
- CVE-2026-98262
- Published
- Oct 6, 2026
- Updated
- Oct 6, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 6, 2026CVE publishedPublication date reported by the CVE source.
- Oct 6, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.6.22
- Affected versionversion=c7a42156d99bcea7f8173ba7a6034bbaa2ecb77c <0191c9ff23ef1678dbfb5ad253a2dee92feb5d71
- Affected versionversion=c7a42156d99bcea7f8173ba7a6034bbaa2ecb77c <4719424bb7cb9f20b73986bcb72dd528f0e5c6eb
- Affected versionversion=c7a42156d99bcea7f8173ba7a6034bbaa2ecb77c <7912ad8fb5233bb8cfe21d50df639c7f4854ff9d
- Affected versionversion=c7a42156d99bcea7f8173ba7a6034bbaa2ecb77c <82e47533221d4746947b74d2e79a478c36c6433a
- Affected versionversion=c7a42156d99bcea7f8173ba7a6034bbaa2ecb77c <8f510f68208a1f673d7c7234a687be4671490e9c
- Affected versionversion=c7a42156d99bcea7f8173ba7a6034bbaa2ecb77c <a5a8b4737f68bbac8aa0685af0c8921e6003c22b
- Affected versionversion=c7a42156d99bcea7f8173ba7a6034bbaa2ecb77c <b28a17d4a9bb0aa38b48681c3927b012ba40eabe
- Affected versionversion=c7a42156d99bcea7f8173ba7a6034bbaa2ecb77c <b691a3e244278362e552439d6d3ee5a5d3703488
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started