# CVE-2026-43188: linux: In the Linux kernel, the following vulnerability has been resolved:  ceph: do not propagate page array emplacement er...

CVE-2026-43188 is fixed in 23 products on 1 platform, first by ALAS2023-2026-1702, released May 11, 2026. It is not reported as exploited. Patch Radar priority: Routine.

- Web page: https://patchblox.com/security/cve/CVE-2026-43188
- Priority: Routine
- CVSS: 5.5 (medium)
- EPSS: 0.0016
- CISA KEV: not listed
- Exploited (vendor report): no
- Publicly disclosed: no
- Published: May 6, 2026

## Description

In the Linux kernel, the following vulnerability has been resolved:  ceph: do not propagate page array emplacement errors as batch errors  When fscrypt is enabled, move_dirty_folio_in_page_array() may fail because it needs to allocate bounce buffers to store the encrypted versions of each folio. Each folio beyond the first allocates its bounce buffer with GFP_NOWAIT. Failures are common (and expected) under this allocation mode; they should flush (not abort) the batch.  However, ceph_process_folio_batch() uses the same `rc` variable for its own return code and for capturing the return codes of its routine calls; failing to reset `rc` back to 0 results in the error being propagated out to the main writeback loop, which cannot actually tolerate any errors here: once `ceph_wbc.pages` is allocated, it must be passed to ceph_submit_write() to be freed. If it survives until the next iteration (e.g. due to the goto being followed), ceph_allocate_page_array()'s BUG_ON() will oops the worker.  Note that this failure mode is currently masked due to another bug (addressed next in this series) that prevents multiple encrypted folios from being selected for the same write.  For now, just reset `rc` when redirtying the folio to prevent errors in move_dirty_folio_in_page_array() from propagating. Note that move_dirty_folio_in_page_array() is careful never to return errors on the first folio, so there is no need to check for that. After this change, ceph_process_folio_batch() no longer returns errors; its only remaining failure indicator is `locked_pages == 0`, which the caller already handles correctly.

## Where it's fixed

| Platform | Product | Fixed in | Fix | Released |
|---|---|---|---|---|
| Linux | bpftool6.18 amzn 2023 | 1:6.18.16-18.222.amzn2023 | [ALAS2023-2026-1702](https://patchblox.com/security/data/fix/linux/alas2023-2026-1702.md) | May 11, 2026 |
| Linux | bpftool6.18-debuginfo amzn 2023 | 1:6.18.16-18.222.amzn2023 | [ALAS2023-2026-1702](https://patchblox.com/security/data/fix/linux/alas2023-2026-1702.md) | May 11, 2026 |
| Linux | kernel-livepatch-6.18.16-18.222 amzn 2023 | 1:1.0-0.amzn2023 | [ALAS2023-2026-1702](https://patchblox.com/security/data/fix/linux/alas2023-2026-1702.md) | May 11, 2026 |
| Linux | kernel6.18 amzn 2023 | 1:6.18.16-18.222.amzn2023 | [ALAS2023-2026-1702](https://patchblox.com/security/data/fix/linux/alas2023-2026-1702.md) | May 11, 2026 |
| Linux | kernel6.18-debuginfo amzn 2023 | 1:6.18.16-18.222.amzn2023 | [ALAS2023-2026-1702](https://patchblox.com/security/data/fix/linux/alas2023-2026-1702.md) | May 11, 2026 |
| Linux | kernel6.18-debuginfo-common-aarch64 amzn 2023 | 1:6.18.16-18.222.amzn2023 | [ALAS2023-2026-1702](https://patchblox.com/security/data/fix/linux/alas2023-2026-1702.md) | May 11, 2026 |
| Linux | kernel6.18-debuginfo-common-x86_64 amzn 2023 | 1:6.18.16-18.222.amzn2023 | [ALAS2023-2026-1702](https://patchblox.com/security/data/fix/linux/alas2023-2026-1702.md) | May 11, 2026 |
| Linux | kernel6.18-devel amzn 2023 | 1:6.18.16-18.222.amzn2023 | [ALAS2023-2026-1702](https://patchblox.com/security/data/fix/linux/alas2023-2026-1702.md) | May 11, 2026 |
| Linux | kernel6.18-headers amzn 2023 | 1:6.18.16-18.222.amzn2023 | [ALAS2023-2026-1702](https://patchblox.com/security/data/fix/linux/alas2023-2026-1702.md) | May 11, 2026 |
| Linux | kernel6.18-libbpf amzn 2023 | 1:6.18.16-18.222.amzn2023 | [ALAS2023-2026-1702](https://patchblox.com/security/data/fix/linux/alas2023-2026-1702.md) | May 11, 2026 |
| Linux | kernel6.18-libbpf-debuginfo amzn 2023 | 1:6.18.16-18.222.amzn2023 | [ALAS2023-2026-1702](https://patchblox.com/security/data/fix/linux/alas2023-2026-1702.md) | May 11, 2026 |
| Linux | kernel6.18-libbpf-devel amzn 2023 | 1:6.18.16-18.222.amzn2023 | [ALAS2023-2026-1702](https://patchblox.com/security/data/fix/linux/alas2023-2026-1702.md) | May 11, 2026 |
| Linux | kernel6.18-libbpf-static amzn 2023 | 1:6.18.16-18.222.amzn2023 | [ALAS2023-2026-1702](https://patchblox.com/security/data/fix/linux/alas2023-2026-1702.md) | May 11, 2026 |
| Linux | kernel6.18-modules-extra amzn 2023 | 1:6.18.16-18.222.amzn2023 | [ALAS2023-2026-1702](https://patchblox.com/security/data/fix/linux/alas2023-2026-1702.md) | May 11, 2026 |
| Linux | kernel6.18-modules-extra-common amzn 2023 | 1:6.18.16-18.222.amzn2023 | [ALAS2023-2026-1702](https://patchblox.com/security/data/fix/linux/alas2023-2026-1702.md) | May 11, 2026 |
| Linux | kernel6.18-tools amzn 2023 | 1:6.18.16-18.222.amzn2023 | [ALAS2023-2026-1702](https://patchblox.com/security/data/fix/linux/alas2023-2026-1702.md) | May 11, 2026 |
| Linux | kernel6.18-tools-debuginfo amzn 2023 | 1:6.18.16-18.222.amzn2023 | [ALAS2023-2026-1702](https://patchblox.com/security/data/fix/linux/alas2023-2026-1702.md) | May 11, 2026 |
| Linux | kernel6.18-tools-devel amzn 2023 | 1:6.18.16-18.222.amzn2023 | [ALAS2023-2026-1702](https://patchblox.com/security/data/fix/linux/alas2023-2026-1702.md) | May 11, 2026 |
| Linux | linux Debian 14 | 6.19.6-1 | [DEBIAN-CVE-2026-43188](https://patchblox.com/security/data/fix/linux/debian-cve-2026-43188.md) | May 15, 2026 |
| Linux | perf6.18 amzn 2023 | 1:6.18.16-18.222.amzn2023 | [ALAS2023-2026-1702](https://patchblox.com/security/data/fix/linux/alas2023-2026-1702.md) | May 11, 2026 |
| Linux | perf6.18-debuginfo amzn 2023 | 1:6.18.16-18.222.amzn2023 | [ALAS2023-2026-1702](https://patchblox.com/security/data/fix/linux/alas2023-2026-1702.md) | May 11, 2026 |
| Linux | python3-perf6.18 amzn 2023 | 1:6.18.16-18.222.amzn2023 | [ALAS2023-2026-1702](https://patchblox.com/security/data/fix/linux/alas2023-2026-1702.md) | May 11, 2026 |
| Linux | python3-perf6.18-debuginfo amzn 2023 | 1:6.18.16-18.222.amzn2023 | [ALAS2023-2026-1702](https://patchblox.com/security/data/fix/linux/alas2023-2026-1702.md) | May 11, 2026 |

---

Data as of 2026-11-09T07:25:28Z 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.
