What is CVE-2026-98254?

CVE-2026-98254 is a High severity Linux kernel vulnerability with a CVSS score of 7.8 out of 10, affecting Linux kernel versions from 5.10.47 onward and patched in 6.12.112, 6.18.54, 7.2.8 and others. CVE-2026-98254 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

What is the CVSS score for CVE-2026-98254?

CVE-2026-98254 has a CVSS score of 7.8 out of 10, rated High severity. The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.

Is there a patch available for CVE-2026-98254?

Yes, CVE-2026-98254 has been patched. Fixed versions include 6.12.112, 6.18.54, 7.2.8 and others. If you are running Linux kernel 5.10.47 or later up to the fix versions, apply the relevant patch for your kernel branch.

Is CVE-2026-98254 actively exploited?

CVE-2026-98254 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

CVE-2026-98254

High

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.

Package Linux Kernel

Published 2026-10-06

Last modified 2026-10-07

CVSS version 3.1

Patch available

Yes

CVSS 3.1 score

7.8

out of 10

High

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Vector string

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected versions

Linux kernel versions 5.10.47, 5.12.14, 5.13 and later are affected. Fixed in 6.12.112, 6.18.54, 7.2.8, 7.3-rc4 and their respective stable series.

Affected from

≥ 5.10.47 ≥ 5.12.14 ≥ 5.13

Fixed in

✓ 6.12.112 6.12.x ✓ 6.18.54 6.18.x ✓ 7.2.8 7.2.x ✓ 7.3-rc4

References

4 total

Details

CVE ID CVE-2026-98254

Severity High

CVSS score 7.8 / 10

CVSS version 3.1

Published 2026-10-06

Modified 2026-10-07

KEV No

Patch

Yes

Package linux

Frequently asked questions

What is CVE-2026-98254?

CVE-2026-98254 is a High severity Linux kernel vulnerability with a CVSS score of 7.8 out of 10 . It affects Linux kernel versions from 5.10.47 onward and has been patched in 6.12.112, 6.18.54, 7.2.8 and others. CVE-2026-98254 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
What is the CVSS score for CVE-2026-98254?

CVE-2026-98254 has a CVSS score of 7.8 out of 10, rated High severity (CVSS 3.1). The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
Is there a patch available for CVE-2026-98254?

Yes. CVE-2026-98254 has been patched. Fixed versions include 6.12.112, 6.18.54, 7.2.8 and others. If you are running Linux kernel 5.10.47 or later up to the fix versions, apply the relevant patch for your kernel branch.
Is CVE-2026-98254 actively exploited?

No. CVE-2026-98254 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.