QEMU security fixes and PostgreSQL executor work
QEMU stable and development trees picked up fixes for three CVEs in the QED, DMG, and RTL8139 paths, alongside a large multi-target build cleanup. On the PostgreSQL side, asynchronous MergeAppend moved toward commit and a hash-index WAL series addressed a recovery hazard.
QEMU stable backports QED cluster conversion fix
Stable series 10.0.16 and 11.1.4 both received a backport of the fix for CVE-2026-118594 in qed_bytes_to_clusters(). An incorrect denominator in that conversion could leak or disclose heap memory to a guest using the QED block driver. Operators on those stable branches should take the update if they still serve QED images.
DMG LZFSE short-decode disclosure patched
A two-patch series fixes CVE-2026-116483, a heap disclosure when the DMG LZFSE path returns a short decode, and adds a regression test. The bug matters to anyone opening untrusted DMG images under QEMU.
RTL8139 DMA limited to plain memory
A patch restricts RTL8139 DMA transfers to plain memory, closing CVE-2026-128868. The re-entrancy bug could delete devices in the middle of an operation.
Series to uniquify QOM type names
A 48-patch series, already under heavy review, aims to resolve QOM type conflicts in multi-target builds by enforcing unique type names and replacing aliases and is_available hooks. The work is aimed at building one QEMU binary that covers multiple targets without type collisions.
Runtime endianness proposed for aarch64 linux-user
A 12-patch series for 12.0 proposes selecting aarch64 and arm endianness at runtime in linux-user, which would deprecate separate big-endian targets. Maintainers have questioned the value and raised implications for MIPS.
Asynchronous MergeAppend nears commit
Etsuro Fujita posted a reworked asynchronous MergeAppend patch on pgsql-hackers. Reviewers approved the approach, and he plans to commit after one week.
Hash index WAL drops pin-only bucket registrations
A patch series refactors hash-index WAL logging so pin-only bucket pages are no longer registered with REGBUF_NO_CHANGE, and it fixes a pre-existing torn-page hazard during recovery. The change is relevant to anyone relying on hash indexes through crash recovery.