Answer in brief
CVE-2026-89918 records a Unknown severity vulnerability in KVM: arm64: Correctly handle end of VA space TLBI invalidation. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=4ffa72ad8f37e73bbb6c0baa88557bcb4fd39929 <ce447651a52ec077694172af10c4fffb11f56c43 || >=4ffa72ad8f37e73bbb6c0baa88557bcb4fd39929 <c624731ca6fe59ad8909ce4108301aa7560a91d6 || >=4ffa72ad8f37e73bbb6c0baa88557bcb4fd39929 <34af2c3e31f91a739dc175459fdbd99ed952b457 | ce447651a52ec077694172af10c4fffb11f56c43, c624731ca6fe59ad8909ce4108301aa7560a91d6, 34af2c3e31f91a739dc175459fdbd99ed952b457 |
| Linux/Linuxgeneric | 6.16 | Not reported |
Published upstream
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 16, 2026
In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Correctly handle end of VA space TLBI invalidation Our TLB invalidation by VA code is based on comparing two ranges, one defined by the TLB, and one defined by the TLBI instruction. Each range is defined by a start and a size. However, the way the comparison is done doesn't account for address rollover, as it compares an address with (base + size). This works nicely until this expression represent the last page/block in the TTBR1 VA space, as the result is a big fat 0. And a failed TLB invalidation. Rewrite the comparison in a way that is immune to the address rollover (making the end address inclusive instead of exclusive), and move this into a common helper that is used by both VA and IPA invalidations, as suggested by Hyunwoo Kim (although the IPA version didn't suffer from this particular problem, obviously).
Quoted source text, attributed separately from HOL analysis.