You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The **May 16th, 2026** release of **DietPi v10.4** comes with fixes for CVEs "Copy Fail" and "Dirty Frag", a new image for the **Orange Pi 5B** and further enhancements and fixes.
13
+
The **May 16th, 2026** release of **DietPi v10.4** comes with fixes for CVE "Copy Fail" and CVE "Dirty Frag", a new image for the **Orange Pi 5B** and further enhancements and fixes.
14
14
15
15
![Prometheus web interface](../assets/images/dietpi-release-v10_3.webp"Prometheus web interface"){: width="1280" height="720" loading="lazy"}
16
16
@@ -23,7 +23,7 @@ The **May 16th, 2026** release of **DietPi v10.4** comes with fixes for CVEs "Co
23
23
-**Linux security** :octicons-arrow-right-16: The two recent major Linux vulnerabilities CVE-2026-31431 aka "Copy Fail", CVE-2026-43284 and CVE-2026-43500 aka "Dirty Frag", have been mitigated across all supported SBCs: Debian and Raspberry Pi Ltd pushed kernel updates containing the fix, and we did so for all kernel packages distributed with our APT repository. The DietPi update will upgrade kernel packages implicitly. Else please upgrade it yourself, or prevent the affected kernel modules from being loaded, as can be read here: <https://github.com/MichaIng/DietPi/issues/8122>
24
24
-[**NanoPi R76S**](../hardware.md#nanopi-series-friendlyelec) :octicons-arrow-right-16: The network interface names for the two Ethernet ports are now persistent on reboot. They previously could randomly swap on reboot. Many thanks to @oxoocoffee for reporting this: <https://github.com/MichaIng/DietPi/issues/7844>
25
25
-**Allwinner/Amlogic/Rockchip SBCs** :octicons-arrow-right-16: We merged the `linux-dtb-*` package into the `linux-image-*` package. You might have recognized that an `apt upgrade` held back two packages, and an `apt full-upgrade` removed the `linux-dtb-*` package while upgrading `linux-image-*`, which is hence intended. Along with some other changes in our Armbian build system fork, this makes switching between kernel branches easier and more robust, and allows to keep multiple kernel branches installed concurrently safe. The DietPi update will imply the kernel upgrade, if not done yet, unless it was explicitly marked hold by the admin.
26
-
-[**DietPi-Installer**](../hardware.md#make-your-own-distribution) :octicons-arrow-right-16: Cases of GRUB BIOS images with GPT partition table, but without dedicated BIOS boot partition, are now handled gracefully. GRUB throws warnings in those cases, and by default fails, as flashing the bootloader to the gap between GPT header and first partition is considered unreliable. But obviously, the image worked that way before, and Debian's grub-pc package postinst script explicitly ignores the warnings, calling `grub-install` with the `--force` flag. The `dietpi-installer` will now do the same, if this exact case is detected: GPT partition table, no EFI partition => GRUB BIOS needed, but no BIOS boot partition either. Many thanks to @mews-se for reporting a related case of a VPS image: <https://github.com/MichaIng/DietPi/issues/8030>
26
+
-[**DietPi-Installer**](../hardware.md#make-your-own-distribution) :octicons-arrow-right-16: Cases of GRUB BIOS images with GPT partition table, but without dedicated BIOS boot partition, are now handled gracefully. GRUB throws warnings in those cases, and by default fails, as flashing the bootloader to the gap between GPT header and first partition is considered unreliable. But obviously, the image worked that way before, and Debian's `grub-pc` package `postinst` script explicitly ignores the warnings, calling `grub-install` with the `--force` flag. The `dietpi-installer` will now do the same, if this exact case is detected: GPT partition table, no EFI partition => GRUB BIOS needed, but no BIOS boot partition either. Many thanks to @mews-se for reporting a related case of a VPS image: <https://github.com/MichaIng/DietPi/issues/8030>
27
27
-[**DietPi-Software**](../dietpi_tools/software_installation.md#dietpi-software) | [**soju**](../software/social.md#soju) :octicons-arrow-right-16: We migrated to the new official soju repository at Codeberg, after the its GitHub repository got archived. This implies some new releases, hence we recommend to update your soju instance with a `dietpi-software reinstall 213`.
28
28
-[**DietPi-Software**](../dietpi_tools/software_installation.md#dietpi-software) | [**Unbound**](../software/dns_servers.md#unbound) :octicons-arrow-right-16: We push our own up-to-date Unbound packages via our APT server now. This means, that also users who did not install Unbound via `dietpi-software` get our default config and reduced Debian-only content. Please let us know if you face any issues.
29
29
-[**DietPi-Software**](../dietpi_tools/software_installation.md#dietpi-software) | [**Java**](../software/programming.md#java) :octicons-arrow-right-16: The version has been bumped to Java 26 for 64-bit systems. On 32-bit ARM, Java 21 is the highest practically usable one: from Java 22 on, 32-bit ARM support for the Hotspot JVM is broken, hence the extremely slow Zero JVM is used. This causes e.g. Airsonic on the Odroid XU4 to require 1.5 hours to start. This limits the versions of some Java applications for 32-bit, like Minecraft to max v1.21.x. This bug is unlikely to be ever resolved, due to decreasing relevancy of the 32-bit ARM architecture. The upstream bug is tracked here: <https://bugs.openjdk.org/browse/JDK-8321125>
@@ -32,7 +32,7 @@ The **May 16th, 2026** release of **DietPi v10.4** comes with fixes for CVEs "Co
32
32
33
33
-[**DietPi-Tools**](../dietpi_tools.md) | [**DietPi-Drive_Manager**](../dietpi_tools/system_configuration.md#dietpi-drive-manager) :octicons-arrow-right-16: Resolved a v10.3 regression where moving the rootfs on Raspberry Pi to a different drive caused an invalid `/boot/firmware/cmdline.txt` root entry, failing to boot. Many thanks to @TimH for reporting this issue: <https://dietpi.com/forum/t/25154>
34
34
-[**DietPi-Software**](../dietpi_tools/software_installation.md#dietpi-software) | [**Docker**](../software/system_stats.md#docker) :octicons-arrow-right-16: Resolved a v10.3 regression where a fresh Docker installation failed, since `--no-reload` was used when unmasking `docker.service`, which prevents `docker.socket` from starting up as well. Many thanks to @peracchi for reporting this issue: <https://github.com/MichaIng/DietPi/issues/8108>
35
-
-[**DietPi-Software**](../dietpi_tools/software_installation.md#dietpi-software) | [**Home Assistant**](../software/home_automation.md#home-assistant) :octicons-arrow-right-16: Resolved an issue where the installation might have failed, when starting it from within a desktop session. As we used `runuser`, environment variables were passed through to `uv`, notably `XDG_DATA_HOME`, which was then used as install dir for Python, instead of the intended service user's home directory. All runuser calls have now been replaced by `setpriv` with the `--reset-env` flag, to guarantee a clean environment. Many thanks to @btuerk89 for reporting this issue: <https://github.com/MichaIng/DietPi/issues/8116>
35
+
-[**DietPi-Software**](../dietpi_tools/software_installation.md#dietpi-software) | [**Home Assistant**](../software/home_automation.md#home-assistant) :octicons-arrow-right-16: Resolved an issue where the installation might have failed, when starting it from within a desktop session. As we used `runuser`, environment variables were passed through to `uv`, notably `XDG_DATA_HOME`, which was then used as install directory for Python, instead of the intended service user's home directory. All `runuser` calls have now been replaced by `setpriv` with the `--reset-env` flag, to guarantee a clean environment. Many thanks to @btuerk89 for reporting this issue: <https://github.com/MichaIng/DietPi/issues/8116>
36
36
-[**DietPi-Software**](../dietpi_tools/software_installation.md#dietpi-software) | [**Synapse**](../software/social.md#synapse) :octicons-arrow-right-16: Resolved an issue where the installation might have failed, since dependencies were not installed as intended.
37
37
-[**DietPi-Software**](../dietpi_tools/software_installation.md#dietpi-software) | [**Immich**](../software/cloud.md#immich)/[**ownCloud Infinite Scale**](../software/cloud.md#owncloud) :octicons-arrow-right-16: Resolved a v10.3 regression, where the service failed to start, as it does not have the permissions to "touch" its environment file, to trigger the systemd automount, if needed. Instead of "touch", automounts for environment files are now triggered with `test -e`, which does not require write access.
38
38
-[**DietPi-Software**](../dietpi_tools/software_installation.md#dietpi-software) | [**Prometheus Node Exporter**](../software/system_stats.md#prometheus-node-exporter) :octicons-arrow-right-16: Resolved an issue on Raspberry Pi where the `raspberrypi_exporter.service` stored the CPU temperature in a wrong format, if a locale with comma (,) as decimal separator was selected on the host system. The service now enforces the C locale. The change is applied during the DietPi update as well. Many thanks to @Grip for reporting this issue: <https://github.com/MichaIng/DietPi/issues/8118>
0 commit comments