# CVE-2026-31445: linux: In the Linux kernel, the following vulnerability has been resolved: mm/damon/core: avoid use of half-online-committe... CVE-2026-31445 is fixed in 19 products on 1 platform, first by DEBIAN-CVE-2026-31445, released May 15, 2026. It is not reported as exploited. Patch Radar priority: Routine. - Web page: https://patchblox.com/security/cve/CVE-2026-31445 - Priority: Routine - CVSS: 5.5 (medium) - EPSS: 0.0012 - CISA KEV: not listed - Exploited (vendor report): no - Publicly disclosed: no - Published: Apr 22, 2026 ## Description In the Linux kernel, the following vulnerability has been resolved: mm/damon/core: avoid use of half-online-committed context One major usage of damon_call() is online DAMON parameters update. It is done by calling damon_commit_ctx() inside the damon_call() callback function. damon_commit_ctx() can fail for two reasons: 1) invalid parameters and 2) internal memory allocation failures. In case of failures, the damon_ctx that attempted to be updated (commit destination) can be partially updated (or, corrupted from a perspective), and therefore shouldn't be used anymore. The function only ensures the damon_ctx object can safely deallocated using damon_destroy_ctx(). The API callers are, however, calling damon_commit_ctx() only after asserting the parameters are valid, to avoid damon_commit_ctx() fails due to invalid input parameters. But it can still theoretically fail if the internal memory allocation fails. In the case, DAMON may run with the partially updated damon_ctx. This can result in unexpected behaviors including even NULL pointer dereference in case of damos_commit_dests() failure [1]. Such allocation failure is arguably too small to fail, so the real world impact would be rare. But, given the bad consequence, this needs to be fixed. Avoid such partially-committed (maybe-corrupted) damon_ctx use by saving the damon_commit_ctx() failure on the damon_ctx object. For this, introduce damon_ctx->maybe_corrupted field. damon_commit_ctx() sets it when it is failed. kdamond_call() checks if the field is set after each damon_call_control->fn() is executed. If it is set, ignore remaining callback requests and return. All kdamond_call() callers including kdamond_fn() also check the maybe_corrupted field right after kdamond_call() invocations. If the field is set, break the kdamond_fn() main loop so that DAMON sill doesn't use the context that might be corrupted. [sj@kernel.org: let kdamond_call() with cancel regardless of maybe_corrupted] ## Where it's fixed | Platform | Product | Fixed in | Fix | Released | |---|---|---|---|---| | Linux | bpftool6.18 amzn 2023 | 1:6.18.25-52.107.amzn2023 | [ALAS2023-2026-1746](https://patchblox.com/security/data/fix/linux/alas2023-2026-1746.md) | May 25, 2026 | | Linux | bpftool6.18-debuginfo amzn 2023 | 1:6.18.25-52.107.amzn2023 | [ALAS2023-2026-1746](https://patchblox.com/security/data/fix/linux/alas2023-2026-1746.md) | May 25, 2026 | | Linux | kernel-livepatch-6.18.25-52.107 amzn 2023 | 1:1.0-0.amzn2023 | [ALAS2023-2026-1746](https://patchblox.com/security/data/fix/linux/alas2023-2026-1746.md) | May 25, 2026 | | Linux | kernel6.18 amzn 2023 | 1:6.18.25-52.107.amzn2023 | [ALAS2023-2026-1746](https://patchblox.com/security/data/fix/linux/alas2023-2026-1746.md) | May 25, 2026 | | Linux | kernel6.18-debuginfo amzn 2023 | 1:6.18.25-52.107.amzn2023 | [ALAS2023-2026-1746](https://patchblox.com/security/data/fix/linux/alas2023-2026-1746.md) | May 25, 2026 | | Linux | kernel6.18-debuginfo-common-aarch64 amzn 2023 | 1:6.18.25-52.107.amzn2023 | [ALAS2023-2026-1746](https://patchblox.com/security/data/fix/linux/alas2023-2026-1746.md) | May 25, 2026 | | Linux | kernel6.18-debuginfo-common-x86_64 amzn 2023 | 1:6.18.25-52.107.amzn2023 | [ALAS2023-2026-1746](https://patchblox.com/security/data/fix/linux/alas2023-2026-1746.md) | May 25, 2026 | | Linux | kernel6.18-devel amzn 2023 | 1:6.18.25-52.107.amzn2023 | [ALAS2023-2026-1746](https://patchblox.com/security/data/fix/linux/alas2023-2026-1746.md) | May 25, 2026 | | Linux | kernel6.18-headers amzn 2023 | 1:6.18.25-52.107.amzn2023 | [ALAS2023-2026-1746](https://patchblox.com/security/data/fix/linux/alas2023-2026-1746.md) | May 25, 2026 | | Linux | kernel6.18-modules-extra amzn 2023 | 1:6.18.25-52.107.amzn2023 | [ALAS2023-2026-1746](https://patchblox.com/security/data/fix/linux/alas2023-2026-1746.md) | May 25, 2026 | | Linux | kernel6.18-modules-extra-common amzn 2023 | 1:6.18.25-52.107.amzn2023 | [ALAS2023-2026-1746](https://patchblox.com/security/data/fix/linux/alas2023-2026-1746.md) | May 25, 2026 | | Linux | kernel6.18-tools amzn 2023 | 1:6.18.25-52.107.amzn2023 | [ALAS2023-2026-1746](https://patchblox.com/security/data/fix/linux/alas2023-2026-1746.md) | May 25, 2026 | | Linux | kernel6.18-tools-debuginfo amzn 2023 | 1:6.18.25-52.107.amzn2023 | [ALAS2023-2026-1746](https://patchblox.com/security/data/fix/linux/alas2023-2026-1746.md) | May 25, 2026 | | Linux | kernel6.18-tools-devel amzn 2023 | 1:6.18.25-52.107.amzn2023 | [ALAS2023-2026-1746](https://patchblox.com/security/data/fix/linux/alas2023-2026-1746.md) | May 25, 2026 | | Linux | linux Debian 14 | 6.19.11-1 | [DEBIAN-CVE-2026-31445](https://patchblox.com/security/data/fix/linux/debian-cve-2026-31445.md) | May 15, 2026 | | Linux | perf6.18 amzn 2023 | 1:6.18.25-52.107.amzn2023 | [ALAS2023-2026-1746](https://patchblox.com/security/data/fix/linux/alas2023-2026-1746.md) | May 25, 2026 | | Linux | perf6.18-debuginfo amzn 2023 | 1:6.18.25-52.107.amzn2023 | [ALAS2023-2026-1746](https://patchblox.com/security/data/fix/linux/alas2023-2026-1746.md) | May 25, 2026 | | Linux | python3-perf6.18 amzn 2023 | 1:6.18.25-52.107.amzn2023 | [ALAS2023-2026-1746](https://patchblox.com/security/data/fix/linux/alas2023-2026-1746.md) | May 25, 2026 | | Linux | python3-perf6.18-debuginfo amzn 2023 | 1:6.18.25-52.107.amzn2023 | [ALAS2023-2026-1746](https://patchblox.com/security/data/fix/linux/alas2023-2026-1746.md) | May 25, 2026 | --- Data as of 2026-11-08T06:59:42Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.