CVE-2026-80892 Affecting kernel6.12-modules-extra-common package, versions <1:6.12.103-127.188.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-KERNEL612MODULESEXTRACOMMON-19896243
- published18 Sept 2026
- disclosed4 Sept 2026
Introduced: 4 Sep 2026
NewCVE-2026-80892 (opens in a new tab)How to fix?
Upgrade Amazon-Linux:2023 kernel6.12-modules-extra-common to version 1:6.12.103-127.188.amzn2023 or higher.
This issue was patched in ALAS2023-2026-2110.
NVD Description
Note: Versions mentioned in the description apply only to the upstream kernel6.12-modules-extra-common package and not the kernel6.12-modules-extra-common 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:
erofs: cap LZMA stream pool size
fs/erofs/decompressor_lzma.c sizes the module-global MicroLZMA stream pool from num_possible_cpus() when the lzma_streams module parameter is unset, then z_erofs_load_lzma_config() preallocates one image-supplied dictionary per stream, accepting dictionaries up to 8 MiB. On high-CPU systems, a small EROFS image can pin hundreds of MiB of vmalloc-backed decoder state until the erofs module is unloaded.
Impact: An EROFS image mounted by the system can pin up to 8 MiB of vmalloc memory per LZMA stream, either as intended or unexpectedly.
Bound the default stream count by a new CONFIG_EROFS_FS_ZIP_LZMA_DEFAULT_MAX_STREAMS option, default 16, so the worst-case default preallocation is 128 MiB if the number of CPUs is no less than 16 while preserving the existing per-image dictionary limit. An explicit lzma_streams module parameter is still honoured as-is, so administrators who deliberately size the pool are not affected.
References
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-80892
- https://git.kernel.org/stable/c/0c676903cb2a61992ded8e7907609cc6b0f11744
- https://git.kernel.org/stable/c/5aaa06dfc10f8398c8807453dbec738ea9af10e4
- https://git.kernel.org/stable/c/682cb3ece37fc5141e73bc726ccf4adb833e5189
- https://git.kernel.org/stable/c/c9b47e6b23114e939b17f818471c7a46e59006e7
- https://git.kernel.org/stable/c/e52da169b8c0d19bb2d803f2a07fe0e5a00462d6
- https://git.kernel.org/stable/c/e8b3d09aa8889dda9be9cbb3d2f0218c4b9acde4