CVE-2026-98254·Kernel vulnerability
In the Linux kernel, the following vulnerability has been resolved: swiotlb: use the adjusted address for the highmem page lookup swiotlb_bounce() reads the page frame number from the slot's recorded orig_addr, then advances orig_addr by tlb_offset to reach the address the caller asked about. The highmem branch mixes the two: the offset within the page comes from the adjusted address, the page from the value before it. Once the adjustment crosses a page boundary the pair no longer describes one location, and the whole copy lands one page below the intended one for a positive tlb_offset, one above for a negative one. DMA_FROM_DEVICE writes the device data over the wrong page and leaves the intended one stale, DMA_TO_DEVICE feeds the device from a page the mapping may not cover. Partial syncs through dma_sync_single_range_for_*() are what make tlb_offset non-zero. The branch test is picked the same way, so a slot recorded in lowmem can be adjusted into highmem and the lowmem path then hands a highmem address to phys_to_virt(). Take both from orig_addr once it is final and keep pfn in the branch that uses it. PhysHighMem() asks the question straight from the address, as dma-debug already does.
- Severity
- high
- Software
- Kernel
- Fixed in
- 6.12.112, 6.18.54, 7.2.8, 7.3
- Published
How likely is exploitation
FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 0.13% — higher than 2% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.
Read the two together. CVE-2026-98254 scores 7.8 on CVSS, so a successful attack would be serious — but at 0.13%, almost nobody is currently attempting it. That is a different situation from a flaw under mass exploitation, and it is usually the difference between patching on your next maintenance window and patching tonight.
How to fix this CVE
Update your Linux kernel to a patched version to fix a critical memory addressing flaw in the swiotlb DMA subsystem. Systems using kernel versions before 6.12.112, 6.18.54, or 7.2.8 should upgrade to the latest stable release within their respective branch to prevent potential data corruption and unauthorized memory access.
sudo dnf update kernel kernel-develDefensia detects this vulnerability
How to check if you are affected
- Run `uname -r` to check your current kernel version and compare against fixed versions (6.12.112, 6.18.54, 7.2.8, or 7.3+)
- Verify swiotlb is in use by checking `cat /proc/cmdline | grep swiotlb` (if empty or not showing `swiotlb=`, DMA bouncing is active by default)
- Check dmesg logs for DMA-related errors with `dmesg | grep -i 'dma\|swiotlb\|bounce'` to identify potential exploitation or data corruption events
- Confirm patch application by verifying the kernel commit hash is present: `git log --oneline | grep -E '0219b72f5c209732b2f03a8cc0d7240b5e428a99|6e53b4d6afbde626255805d438cabb1cac482445|aa4709813b29db89f2307f968db5d24925dcdeb1|b7d7914a9ae3097e63d113007e4fb44d33d515b1'`
FAQ
What is CVE-2026-98254?
This vulnerability is a memory addressing bug in the Linux kernel's swiotlb (software I/O TLB) subsystem that causes DMA operations to target incorrect memory pages when crossing page boundaries during partial synchronizations, potentially leading to data corruption or unauthorized memory access.
Is CVE-2026-98254 being actively exploited?
No, this vulnerability is not actively exploited in the wild and no public exploit is available. However, the high CVSS score (7.8) indicates significant risk if leveraged by local attackers with process-level privileges.
What versions of Kernel are affected by CVE-2026-98254?
All kernel versions prior to the fixed stable releases are affected: versions before 6.12.112, 6.18.54, 7.2.8, and mainline before 7.3. Affected systems should upgrade within their current stable branch rather than jumping to a newer major version.
How do I check if my server is vulnerable to CVE-2026-98254?
Run `uname -r` and compare your kernel version against the fixed versions (6.12.112, 6.18.54, 7.2.8, or 7.3+). If your version is lower than the corresponding fixed release in your branch, your system is vulnerable.
Does Defensia detect CVE-2026-98254?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Kernel is installed on a monitored server, CVE-2026-98254 will appear in your dashboard with remediation steps.
Related Kernel CVEs
References
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-98254. Free for 1 server.
Get started free