Integer Overflow or Wraparound The advisory has been revoked - it doesn't affect any version of package kernel-zfcpdump-core (opens in a new tab)
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-CENTOS10-KERNELZFCPDUMPCORE-22209918
- published5 Nov 2026
- disclosed16 Sept 2026
Introduced: 16 Sep 2026
CVE-2026-89918 (opens in a new tab)Amendment
The Centos security team deemed this advisory irrelevant for Centos:10.
NVD Description
Note: Versions mentioned in the description apply only to the upstream kernel-zfcpdump-core package and not the kernel-zfcpdump-core package as distributed by Centos.
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).
References
- https://bugzilla.redhat.com/show_bug.cgi?id=2535109
- https://access.redhat.com/security/cve/CVE-2026-89918
- https://git.kernel.org/stable/c/34af2c3e31f91a739dc175459fdbd99ed952b457
- https://git.kernel.org/stable/c/c624731ca6fe59ad8909ce4108301aa7560a91d6
- https://git.kernel.org/stable/c/ce447651a52ec077694172af10c4fffb11f56c43