CVE-2026-43188None▾ SunlitIn 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 bo…
▾ Sunlit zone — Low / medium · no exploitation signal
impact 2.8 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
Last analysed / modified upstream
0.2%
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.
Linux >= ce80b76dd32764cc914975777e058d4fae4f0ea0 < 746840c87d76b614b14d9337c466ff022fc49823Linux >= ce80b76dd32764cc914975777e058d4fae4f0ea0 < 4c0d84c788d89c167abf0bf84fd37890c4c84f08Linux >= ce80b76dd32764cc914975777e058d4fae4f0ea0 < 707104682e3c163f7c14cdd6b07a3e95fb374759Linux 0f2b2b7cacf888229cec19126e6791b11fb35f32Linux >= 6.12.114 < 6.13Linux 6.15Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-98869Nonebpf: Infer zext_dst based on static register liveness analysis
CVE-2023-7356NoneBluetooth: ISO: Copy BASE if service data matches EIR_BAA_SERVICE_UUID
CVE-2026-98766Noneusb: gadget: aspeed-vhub: cancel wake work on device removal
CVE-2026-98768Medium· 4.7usb: typec: anx7411 - stop the IRQ before destroying the workqueue
CVE-2026-98767Noneusb: dwc3: gadget: fix IRQ storm on invalid event buffer count
CVE-2026-98770Noneusb: gadget: midi2: Fix the jack descriptor array sizes