KVM: arm64: Correctly handle end of VA space TLBI invalidation
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 34af2c3e31f91a739dc175459fdbd99ed952b457, Kernel c624731ca6fe59ad8909ce4108301aa7560a91d6 and Kernel ce447651a52ec077694172af10c4fffb11f56c43.
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).
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.16, >=4ffa72ad8f37e73bbb6c0baa88557bcb4fd39929 <34af2c3e31f91a739dc175459fdbd99ed952b457, >=4ffa72ad8f37e73bbb6c0baa88557bcb4fd39929 <c624731ca6fe59ad8909ce4108301aa7560a91d6, >=4ffa72ad8f37e73bbb6c0baa88557bcb4fd39929 <ce447651a52ec077694172af10c4fffb11f56c43 | 34af2c3e31f91a739dc175459fdbd99ed952b457, c624731ca6fe59ad8909ce4108301aa7560a91d6, ce447651a52ec077694172af10c4fffb11f56c43 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket