CVE-2026-89783 Affecting kernel-tools-devel package, versions <1:6.1.188-233.385.amzn2023
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-AMZN2023-KERNELTOOLSDEVEL-20870162
- published13 Oct 2026
- disclosed16 Sept 2026
Introduced: 16 Sep 2026
NewCVE-2026-89783 (opens in a new tab)How to fix?
Upgrade Amazon-Linux:2023 kernel-tools-devel to version 1:6.1.188-233.385.amzn2023 or higher.
This issue was patched in ALAS2023-2026-3197.
NVD Description
Note: Versions mentioned in the description apply only to the upstream kernel-tools-devel package and not the kernel-tools-devel package as distributed by Amazon-Linux.
See How to fix? for Amazon-Linux:2023 relevant fixed versions and status.
In the Linux kernel, the following vulnerability has been resolved:
xfrm6: fix out-of-bounds write in xfrm6_input_addr() when secpath is full
The depth check in xfrm6_input_addr() is off by one:
if (1 + sp->len == XFRM_MAX_DEPTH) goto drop; ... sp->xvec[sp->len++] = x;
xfrm_input() can leave sp->len == XFRM_MAX_DEPTH, and the transport-mode receive path re-enters IPv6 input via xfrm_trans_reinject() with that secpath preserved. If the inner packet carries a destination-options HAO option or a type-2 routing header, xfrm6_input_addr() is called with sp->len == XFRM_MAX_DEPTH; the check (1 + 6 == 6) is false, so sp->xvec[sp->len++] writes one slot past the 6-element xvec[]. The write stays within the sec_path allocation (invisible to KASAN); UBSAN_BOUNDS flags it and panics under panic_on_warn.
Use "sp->len >= XFRM_MAX_DEPTH", matching xfrm_input(). This also restores one chain level the old check rejected at sp->len == 5.
UBSAN: array-index-out-of-bounds in net/ipv6/xfrm6_input.c:309:10 index 6 is out of range for type 'xfrm_state *[6]'
References
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-89783
- https://git.kernel.org/stable/c/0f679e0523ddfff3fb554336ceb874b0e51e9cd3
- https://git.kernel.org/stable/c/48996649222e95008cdb98cd58579e3fc8e5ee06
- https://git.kernel.org/stable/c/5d9e3bf34fec9a5d237e4b7cef4a707bc2e091bc
- https://git.kernel.org/stable/c/5f35a29a5eed3d80befd32050843ac88dea3d61a
- https://git.kernel.org/stable/c/68e8737fe8e72f085c608cff322b3d2de8340af1
- https://git.kernel.org/stable/c/8fe2c53fb81f5ad5be43af2ad09583f7c78b4b77
- https://git.kernel.org/stable/c/91fc387f63c00ddfb5221127a17bac97549a8343
- https://git.kernel.org/stable/c/bdcda866c89f9a8b1acdabf02d26cde9fbe501d8