CVE-2026-98262 json
ata: libahci: clear PxCLBU and PxFBU for AHCI_HFLAG_32BIT_ONLY
published last mo. modified 23d ago also EUVD-2026-93190
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 7%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 7.3
- linux Debian 12 6.1.190-1
- linux Debian 13 6.12.113-1
- linux Debian 14 7.2.8-1
- linux-6.12 Debian 12 6.12.113-1~deb12u1
debian advisories DEBIAN-CVE-2026-98262
- linux Ubuntu 22.04 LTS 5.15.0-202.212
- linux Ubuntu 24.04 LTS 6.8.0-149.149
- linux Ubuntu 26.04 LTS 7.0.0-42.42
- linux-aws Ubuntu 22.04 LTS 5.15.0-1119.126
- linux-aws Ubuntu 24.04 LTS 6.8.0-1069.74
- linux-aws Ubuntu 26.04 LTS 7.0.0-1016.17
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1120.130
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1073.81
ubuntu advisories UBUNTU-CVE-2026-98262
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-source openSUSE Tumbleweed 7.2.10-1.1
opensuse advisories openSUSE-SU-2026:12131-1
- kernel Azure Linux 3.0 6.6.158.1-1
azure linux advisories AZL-106389
Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT
- git.kernel.org/stable/c/0191c9ff23ef1678dbfb5ad253a2dee92feb5d71 commit
- git.kernel.org/stable/c/8f510f68208a1f673d7c7234a687be4671490e9c commit
- git.kernel.org/stable/c/4719424bb7cb9f20b73986bcb72dd528f0e5c6eb commit
- git.kernel.org/stable/c/a5a8b4737f68bbac8aa0685af0c8921e6003c22b commit
- git.kernel.org/stable/c/b28a17d4a9bb0aa38b48681c3927b012ba40eabe commit
- git.kernel.org/stable/c/b691a3e244278362e552439d6d3ee5a5d3703488 commit
- git.kernel.org/stable/c/7912ad8fb5233bb8cfe21d50df639c7f4854ff9d commit
- git.kernel.org/stable/c/82e47533221d4746947b74d2e79a478c36c6433a commit
Is CVE-2026-98262 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-98262 updated cvss 7.0
kernel: ata: libahci: clear PxCLBU and PxFBU for AHCI_HFLAG_32BIT_ONLY
-
Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernel Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9 Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9affected: workaround, no fix available “Fix deferred”
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.18% chance of exploitation in the next 30 days, higher than 7% of all scored CVEs (FIRST EPSS, 2026-11-11).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/0191c9ff23ef1678dbfb5ad253a2dee92feb5d71
- git.kernel.org /stable/c/8f510f68208a1f673d7c7234a687be4671490e9c
- git.kernel.org /stable/c/4719424bb7cb9f20b73986bcb72dd528f0e5c6eb
- git.kernel.org /stable/c/a5a8b4737f68bbac8aa0685af0c8921e6003c22b
- git.kernel.org /stable/c/b28a17d4a9bb0aa38b48681c3927b012ba40eabe
- git.kernel.org /stable/c/b691a3e244278362e552439d6d3ee5a5d3703488
- git.kernel.org /stable/c/7912ad8fb5233bb8cfe21d50df639c7f4854ff9d
- git.kernel.org /stable/c/82e47533221d4746947b74d2e79a478c36c6433a
Sources
- CVE List CVE-2026-98262
- NVD CVE-2026-98262
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.