fix(iscsi): normalize the target name in the generated netroot=
Commit 843af3e751782285cd2bc7c9a3a9d33e843fb91d normalized `rd.iscsi.initiator=`
but left the target name in the `netroot=` line on the next line unnormalized,
even though both come from the same sysfs session directory and are subject to
the same RFC 3722 rules.
fix(iscsi): do not source the boot-time net-lib.sh into module-setup.sh
That sources all of net-lib.sh into dracut.sh, not just the one function that
is wanted. net-lib.sh defines `iface_for_remote_addr()`, which is also defined
in dracut-functions.sh with a different implementation, so the boot-time version
silently replaces it for the rest of the run. The version in dracut-functions.sh
parses `ip -o route get` and prints nothing when the route has no dev token;
the version in net-lib.sh parses `ip route get` and prints the last field
unconditionally, so an unreachable route yields the literal string "unreachable"
as an interface name. `ip_params_for_remote_addr()` then builds a bogus `ip=`
line from it.
Usually boot-time libraries are not sourced into the generator, helpers on both
sides are duplicated instead, e.g.: `iface_for_remote_addr()`.
fix(net-lib): normalize iSCSI target names on the iqn./eui./naa. path
Commit 843af3e751782285cd2bc7c9a3a9d33e843fb91d added a
`normalized_iscsi_name()` call at the end of `parse_iscsi_root()`, but that
statement is only reachable via the legacy positional parsing path. When the
target name is matched by the `*:iqn.*` / `*:eui.*` / `*:naa.*` case statement,
the function returns before the normalization is ever applied.
fix(dracut): do not exit the loop in push_user_devs() without checking all items
This function was copied from `push_host_devs()`, so it inherited the same bug.
If the same device is named in both a configuration file with `add_device+=` and
on the command line with `--add-device=`, it silently discards the rest of the
listed devices after the matching one.
Benjamin Drung [Sun, 2 Aug 2026 12:24:58 +0000 (14:24 +0200)]
fix(iscsi): normalize initiator and target names
According to RFC 3720 the iSCSI names must only use lowercase ASCII
letters ('a'-'z'), digits ('0'-'9'), hyphen ('-'), period ('.'), and
colon (':'). RFC 3720 also requires case-normalization from uppercase to
lowercase.
To prevent injecting special characters into `initiatorname.iscsi`
normalize the initiator and target names before writing them to
`initiatorname.iscsi`.
Benjamin Drung [Fri, 31 Jul 2026 13:53:20 +0000 (15:53 +0200)]
fix(dracut): default to hostonly_cmdline=no in chroot
autopkgtest-build-qemu builds an image that should include a initrd that
can boot this image. It uses the `chroot` command to build the image.
Relevant log:
> (1 of 2) Job dev-mapper-loop0p1.device/start running (3s / no limit)
> (2 of 2) Job dracut-initqueue.service/start running (8s / no limit)
When installing `linux-image-amd64`, `/dev` is not mounted and dracut
turns off host-only mode. That's what we want for this image. But then
`/dev` gets mounted and the initrd is regenerated (when installing
`grub-efi-amd64`). This time the initrd is build in host-only mode and
hostonly-cmdline is enabled.
So default to `hostonly_cmdline=no` in case a chroot is detected. Users
that want to use hostonly-cmdline in a chroot can specify
`hostonly_cmdline=yes` in the dracut config or call dracut with
`--hostonly-cmdline`.
Benjamin Drung [Sat, 28 Mar 2026 17:44:41 +0000 (18:44 +0100)]
refactor(base): merge set_systemd_timeout_for_dev into wait_for_dev
The function `set_systemd_timeout_for_dev` is only used by
`wait_for_dev`. Merge this function back into `wait_for_dev` to avoid
calling `dev_unit_name` twice.
Also, pass only user-supplied SBAT to ukify, as ukify extracts the SBATs
from the stub and kernel PEs on its own. Without this the final UKI
contains duplicated SBATs for which there's not enough space:
dracut[I]: *** Using ukify to create UKI ***
Traceback (most recent call last):
File "/usr/bin/ukify", line 2568, in <module>
main()
~~~~^^
File "/usr/bin/ukify", line 2557, in main
make_uki(opts)
~~~~~~~~^^^^^^
File "/usr/bin/ukify", line 1540, in make_uki
pe_add_sections(opts, uki, unsigned_output)
~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/bin/ukify", line 1057, in pe_add_sections
raise PEError(
...<2 lines>...
)
PEError: Not enough space in existing section .sbat to append new data (need 5354, have 1024)
dracut[F]: *** Creating UEFI image file '/root/test.efi' failed ***
While the intention for removing all After= and Requires= lines on
dbus.service and dbus.socket is to remove the dependency on
sysinit.target, this unintentionally removes the Requires=dbus.socket
dependency for dbus.service as well, which is present in both upstream
dbus and dbus-broker.
Restrict the pattern to only lines mentioning sysinit.target, to better
match what Ubuntu has added downstream.
This fixes or at least works around a problem where
NetworkManager.service can fail to start in the openRuyi distribution.
The symptom is:
- dbus.service is sometimes not stopped before switching root
- ... which causes units in the (non-initrd) system to not bring up
dbus.service, since it is already active.
- Afterwards, dbus.service stops on its own, possibly because the
initramfs is gone.
- Then, NetworkManager.service tries to start, but since it
BindsTo=dbus.service, and dbus.service has already stopped,
NetworkManager.service fails to start.
Journal shows this while attempting to start NetworkManager:
systemd[1]: NetworkManager.service: Bound to unit dbus.service, but unit isn't active.
systemd[1]: Dependency failed for Network Manager.
systemd[1]: NetworkManager.service: Job NetworkManager.service/start failed with result 'dependency'.
perf(systemd-tmpfiles): do not install systemd-tmpfiles-clean.service
It does not have an "Install" section, nor is it manually installed, its only
trigger systemd-tmpfiles-clean.timer is also not installed, and it cannot be run
in the initrd [1].
tmpfilesconfdir variable was used only by the systemd-tmpfiles
dracut module, but after 73e9b64 that variable is no no longer in use.
The motivation for this PR is to explicitly disallow the use
of tmpfilesconfdir going forward as it is not recommended for
a dracut module to pick up files from /etc/tmpfiles.d.
Benjamin Drung [Wed, 22 Jul 2026 09:40:04 +0000 (11:40 +0200)]
fix(mdraid): escape slash in sed regular expression
`sed` from busybox treats the `/` from `[[:alpha:]/]` inside
`/pattern/d` as the closing delimiter for the match pattern, rather than
a character inside the bracket class:
```
sed: bad regex '(RUN|IMPORT\{program\})\+?="[[:alpha:]': Missing ']'
```
fix(systemd-tmpfiles): do not include tmpfiles configured in /etc
Users may have tmpfiles configured in /etc to be created after switching root,
always including this user configuration in the initrd may break their setups.
perf(udev-rules): do not install the mtp-probe udev helper
The mtp-probe udev helper belongs to the libmtp package, and is called from
69-libmtp.rules, which is not installed in the initrd. Since mtp-probe depends
on libmtp, libgcrypt and libgpg-error, we can save ~2.5 MB uncompressed (~1 MB
compressed) avoiding the installation of a udev helper that is not necessary.
Also, if an external udev rule would require this helper, it would be installed
by `_inst_rule_programs()`.
perf(udev-rules): do not install the hid2hci udev helper
The hid2hci udev helper belongs to the bluez package, and is called from
97-hid2hci.rules, which is not installed in the initrd. Moreover, it should be
installed by the bluetooth dracut module if it were necessary. Also, if an
external udev rule would require this helper, it would be installed by
`_inst_rule_programs()`.
perf(udev-rules): do not try to install fw_unit_symlinks.sh
This script was specific for RH/Fedora, it was last shipped in their downstream
udev package in RHEL 6/Fedora 13 [1][2], and no longer present in Fedora 14 [3].
perf(udev-rules): do not try to install udev built-ins
input_id, path_id and usb_id are udev built-ins, not binaries. These 3 were
already built-ins in the original import of the udev repository in 2012 to
systemd [1], hence they are also built-ins in eudev [2].
It was added in systemd-v258 [1], but it has become more important since
systemd-udevd-control.socket was removed [2]. Although for now it remains as a
symlink to systemd-udevd-varlink.socket for compatibility reasons,
systemd-udevd.service and systemd-udev-trigger.service no longer reference it in
"Sockets=" and "After=" respectively.
This is still working by accident. Thanks to the current symlink from
systemd-udevd-control.socket to systemd-udevd-varlink.socket, dracut resolves it
and also installs systemd-udevd-varlink.socket in the initrd. The symlink to
sockets.target.wants is not created, but since systemd-udevd.service has
`Sockets=... systemd-udevd-varlink.socket`, systemd creates automatic "Wants="
and "After=" dependencies (see systemd.service(5)), so the unit gets into the
transaction anyway.
chore(Makefile): filter out chrony dracut module for non-systemd
chrony dracut module in its current form depends on the systemd
dracut module. Filter out chrony dracut module during build
time for enviroments not supporting systemd to be consisent with
othersystemd dependent dracut modules.
Benjamin Drung [Thu, 23 Jul 2026 10:40:46 +0000 (12:40 +0200)]
fix(mdraid): install 59-persistent-storage-md.rules only when needed
Dracut installs in the initrd a custom `59-persistent-storage-md.rules`
only to set the option `db_persist`. The main purpose is that if an MD
device is activated in the initrd, its properties are kept on the udev
database after the transition from the initrd to the rootfs. This was
added to fix detection issues when LVM is on top.
mdadm 4.5 included this change from Dracut. Therefore installing
`59-persistent-storage-md.rules` is not needed any more when using
mdadm >= 4.5. `59-persistent-storage-md.rules` can be removed completely
once Dracut drops support for mdadm < 4.5.
See also: https://github.com/md-raid-utilities/mdadm/pull/143
fix(nfs): rpc.statd binary is not required for NFSv4
Dracut fails to create initramfs on nfs4-only host as
the rpc.statd binary is not required for NFSv4 and yet
dracut is checking for its existence and fails.
Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=2483609 Fixes: https://github.com/dracut-ng/dracut/issues/2488 Co-authored-by: Pavel Simó <pavel.simo@gmail.com>
This new module relies on chrony to add support for NTP in the initrd. By
default, it also uses NTP sources from DHCP.
It provides two new kernel command line options:
- `rd.ntp`: it can be used multiple times to specify server, pool and peer time
sources.
- `rd.ntp.nodhcp`: it disables the use of NTP sources from DHCP.
In some environments, it's necessary to fetch live images from HTTPS URLs. The
problem is that the hardware clock may be off, so the validation of the SSL
certificates may fail if the time is out of sync. Also, some systems may not
have access to DHCP for security reasons, that's why we need a way to configure
them on the kernel command line.
Hans de Goede [Fri, 13 Mar 2026 18:13:57 +0000 (19:13 +0100)]
feat(dracut): add module to load Qualcomm ADSP module pre-udev
On Qualcomm sc8280xp and x1e laptops the kernel reboots the ADSP with new
firmware because the BIOS loads ADSP firmware with limited functionality
without sound or battery charge/status reading support.
Unfortunately the ADSP also controls the TCPM (Type-C Port Manager) and
rebooting the ADSP also resets the TCPM, causing any USB devices connected
over Type-C ports to get disconnected as all devices on the USB bus are
removed and re-enumerated.
This breaks booting from USB-drives as the drive gets disconnected and
re-enumerated as a new block device, leaving any filesystems mounted
before the ADSP reset without any backing device.
To workaround this add a module to load the ADSP driver from a pre-udev
hook so that the USB re-enumeration happens before the rootfs is mounted.
Signed-off-by: Hans de Goede <johannes.goede@oss.qualcomm.com>
---
Changes in v5:
- Sort `inst_multiple` arguments alphabetically
Changes in v4:
- Change host-only check to [[ $hostonly_mode == "strict" ]] so that
30-qcom-adsp-pre-udev.sh gets installed in sloppy hostonly mode
- Add modprobe to list of binaries to install from install()
Changes in v3:
- Add "inst grep" to install()
Changes in v2:
- Directly use $DRACUT_ARCH instead of defining _arch local var
- Add the new module to labeler.yml and core.adoc
Benjamin Drung [Fri, 24 Jul 2026 12:41:22 +0000 (14:41 +0200)]
style: remove unneeded function keyword
`function` is a non-standard keyword that can be used to declare
functions in Bash and Ksh, but this would not work with POSIX shell.
Remove it to make the code more consistent (and potential easier to port
to POSIX).
fix(dracut-install): check return value in modalias read()
`find_kmod_module_from_sysfs_modalias()` reads the content of the modalias file
via `len = read()`, and then writes to `alias[len - 1]` without checking if
read() returned 0 (empty file) or -1 (error), potentially causing a stack buffer
out-of-bounds write.
fix(dracut-install): handle empty string in dir_len()
`strlen()` returns the unsigned type size_t, so if `file` were an empty string,
`strlen(file) - 1` would return SIZE_MAX, causing an out-of-bounds read.
Benjamin Drung [Thu, 18 Jun 2026 13:23:30 +0000 (15:23 +0200)]
ci: unify timeout to 10 min by default
Most tests take only a few seconds or minutes on AMD. The tests on ARM
are two to four times slower than their AMD counterparts (due to not
using KVM).
All tests finish in under five minutes except test 60-NFS on AMD (which
can take six to seven minutes) and following tests on ARM:
| Test | Duration | Timeout |
| ----------------- | --------- | ------- |
| 11-USR-MOUNT | 5-10 min | 20 min |
| 20-STORAGE | 9-22 min | 40 min |
| 21-OVERLAYFS | 5-11 min | 20 min |
| 26-ENC-RAID-LVM | 9-21 min | 40 min |
| 30-DMSQUASH | 5-10 min | 20 min |
| 41-FULL-SYSTEMD | 5-9 min | 20 min |
| 45-SYSTEMD-IMPORT | 7 min | 20 min |
| 60-NFS | 19-49 min | 60 min |
| 71-ISCSI | 9 min | 20 min |
| 72-ISCSI-MULTI | 9-20 min | 40 min |
So use a 10 min timeout on all AMD tests and most ARM tests, but
increase the timeout for ARM for those test mentioned above. So use 20
min timeout for several ARM tests, 40 min timeout for 20-STORAGE,
26-ENC-RAID-LVM, 72-ISCSI-MULTI on ARM, and 60 min timeout for 60-NFS
on ARM.
Jihong Min [Tue, 7 Jul 2026 22:07:05 +0000 (07:07 +0900)]
fix(kernel-modules): include xhci-pci-prom21 for early USB
Since Linux 7.2-rc1, AMD PROM21 xHCI controllers may be handled by the
separate xhci-pci-prom21 PCI glue driver.
When CONFIG_USB_XHCI_PCI_PROM21=m, plain xhci-pci intentionally returns
-ENODEV for the PROM21 PCI IDs so that xhci-pci-prom21 can bind them.
However, xhci-pci-prom21 is not a dependency of xhci-pci, so an
initramfs can include xhci-pci.ko while missing xhci-pci-prom21.ko.
On systems where USB keyboard or storage is attached through a PROM21
controller, this can make USB unavailable during initrd, for example at
Plymouth/LUKS unlock.
This is the same class of issue as xhci-pci-renesas, which dracut
already includes explicitly.
Benjamin Drung [Tue, 21 Jul 2026 23:26:43 +0000 (01:26 +0200)]
test(DRACUT-CPIO): fix specifying initrd name twice
The initrd output file name parameter was moved to the `test_dracut`.
Thus specifying the initrd name in the `test_dracut` would become the
second parameter for dracut and interpreted as kernel name. This would
lead to this `realpath` failure:
```
Calling dracut --confdir /var/tmp/dracut-test.NilYUr/dracut.conf.d --add-confdir test --tmpdir /var/tmp/dracut-test.NilYUr/initrd --no-kernel --drivers '' --add-confdir test --enhanced-cpio --no-compress --nostrip --include /var/tmp/dracut-test.NilYUr/cpio-test.Gg7wLrYrO7/simple/init.sh /usr/lib/dracut/hooks/emergency/00-init.sh --install poweroff /var/tmp/dracut-test.NilYUr/cpio-test.Gg7wLrYrO7/simple/initramfs /var/tmp/dracut-test.NilYUr/initramfs.testing
realpath: /lib/modules//var/tmp/dracut-test.NilYUr/initramfs.testing: No such file or directory
```
So use the common initrd output file name in the dracut-cpio test case
as well.
Fixes: 4d55517094f6 ("ci: consolidate output filename for test runs")
Benjamin Drung [Thu, 16 Jul 2026 14:18:08 +0000 (16:18 +0200)]
feat(resume): include in hostonly sloppy mode if supported by kernel
Systems might support hibernation. They need the resume module to get a
working hibernation. Users might configure their systems to enable
hibernation, but the correct order of steps are crucial for it.
Currently this workflow does not work:
1. Make sure system is supported the power state:
```
$ cat /sys/power/state
freeze mem disk
```
2. Configured swap partition
3. Populated the resume kernel boot parameter `resume=/dev/<swap partition>`
4. update grub
5. regenerate initrd
Regenerating the initrd will not include the resume module, because it
hits the "hibernation supported by the kernel, but not enabled" code
path (`/proc/cmdline` doesn not contain `resume=` yet and
`/sys/power/resume` contains `0:0`). A user would need to reboot once
before regenerating the initrd.
To make the system more predictable, include the `resume` module in
hostonly `sloppy` mode if hibernation is supported by the kernel.
fix(network-manager): prevent command injection while parsing DHCP options
Replacing `printf '%q'` with the custom `escape` function introduced a flaw: if
the whole format string is surrounded by single quotes (`'%s='%s'\n'`),
the shell consumes those inner `'` characters as quoting delimiters instead of
passing them to printf, so it receives just `%s=%s\n`, i.e., the surrounding
quotes around the value are gone. Since nothing is quoted, now commands can be
injected via dhcpopts files.
fix(systemd-networkd): escape values from DHCP options
Although systemd-networkd filters invalid values for DHCP options before writing
them to lease files, it's a good practice to escape values read from lease files
before writing them to ".dhcpopts" files, because ".dhcpopts" files are sourced
as a shell script in multiple parts [1][2][3].
fix(dracut-lib): sanitize variable assignments using eval
`splitsep()` uses `eval "$1='${tmp}'"` and `eval "$1='$str'"` to assign values
to caller-named variables. A single quote in the value breaks out of the
assignment.
`export_n()` uses `eval "$var=\"$val\""` to re-assign an unexported variable. A
double quote in the value breaks out of the assignment.
fix(overlayfs-crypt): prevent eval injection in parse_overlay_opts()
parse_overlay_opts() used eval "${ns}${key}='${val}'" to assign
parsed options from the rd.overlay.crypt kernel cmdline parameter.
A single quote in the value breaks out of the assignment and allows
arbitrary command execution.
Fixes: GHSA-wr6r-5whr-98qx Co-developed-by: Claude Opus 4.6 <noreply@anthropic.com>
systemd-pcrnvdone.service was added in systemd-v259, but runs in the initrd
since systemd-v261 [1], and it acts as additional separator measurement
separating pre-boot (firmware + bootloader) measurements from OS measurements.
systemd-pcrosseparator.service was added in systemd-v261 [2], and it measures a
separator event into PCR 9 once all NvPCRs have completed initialization.
Miao Wang [Fri, 3 Jul 2026 11:57:53 +0000 (19:57 +0800)]
fix(dracut-systemd): add ordering constraints
When dracut-initqueue is not enabled, there would be no
dracut-initqueue.service as a sequence point. So explicitly
declare After = basic.target to order dracut-pre-mount.service
after all the services ordered before dracut-initqueue.service.
Fixes: b1ae591945ac ("dracut-systemd: add back missing dependencies")
fix(dracut-install): remove FTS_NOSTAT in install_modules() fts traversal
install_modules() uses FTS_NOSTAT when traversing kernel module
directories. With FTS_NOSTAT, fts may skip stat() and report regular
files as FTS_NSOK instead of FTS_F. However, the fts_info check only
accepts FTS_F and FTS_SL, causing all .ko files found this way to be
silently skipped.
This was previously masked by glibc's fts implementation which ignored
FTS_NOSTAT when FTS_LOGICAL was also set, always calling stat and
returning FTS_F. A recent glibc change (commit 99303f3871, "io: Use
gnulib fts implementation") now honors FTS_NOSTAT regardless, exposing
this bug.
The result is that all '=directory' pattern module installs (=drivers,
=crypto, =fs, etc.) find zero modules, producing an initramfs with only
explicitly-named modules (~40 instead of ~500+), which typically fails
to boot.
Fix it by removing FTS_NOSTAT so that fts always stats files and
reliably reports actual file types.
Stuart Hayes [Fri, 15 May 2026 18:21:27 +0000 (20:21 +0200)]
fix(nvmf): parse json output from "nvme list-subsys"
Modify code that parses the output of "nvme list-subsys" to set up
rd.nvmf.discover parameter to use the json output of nvme rather than the
human-readable output.
A recent commit to nvme-cli changed the human-readable output to only
print the transport address rather than the address line that includes all
of the needed information, but the json output still contains the needed
information.
An even more recent commit to nvme-cli changed the json output (it moved
some details from the "Address" value to an "AddressDetails" object), so
support that as well as the previous format.
Signed-off-by: Stuart Hayes <stuart.w.hayes@gmail.com> Signed-off-by: Martin Wilck <mwilck@suse.com>
Martin Wilck [Mon, 6 Jul 2026 20:35:27 +0000 (22:35 +0200)]
fix(nvmf): make network driver determination work without nbft$X
82f7f7d ("improvement(74nvmf): lookup required NIC kernel modules for NBFT
interfaces") assumes that the NBFT network interfaces are named according
to the nbft$X convention, which is no longer true with the latest patches.
Martin Wilck [Mon, 16 Feb 2026 22:34:20 +0000 (23:34 +0100)]
feat(nvmf): allow using system interface naming policy
nm-initrd-generator from NetworkManager 1.54 or newer supports parsing the
NBFT directly. Because NM allows identifying network interface by MAC
address, we don't need the ifname= setting any more to identify the
interface at the cmdline stage. We just need to check whether the system
has an NBFT with at least one entry.
Introduce the cmdline parameter "rd.nvmf.nm" to force dracut to use
nm-initrd-generator to set up network interfaces from the NBFT.
Martin Wilck [Mon, 16 Feb 2026 19:11:26 +0000 (20:11 +0100)]
feat(nvmf): add dracut.conf option nvmf_nbft_mode
Add a dracut.conf.d option to control the generation of rd.nvmf.discover=
entries if hostonly_cmdline = "yes".
The option can take the values "static" (previous default behavior,
generate cmdline entries for every NVMe subsystem in the device stack),
"nbft" (don't generate any for tcp transport if an NBFT is present),
and "match" (only generate rd.nvmf.discover= entries for subsystems that
are not matched by current NBFT entries, as implemented by the previous
commit).
The default is "match", because this should fit user expectations best.
Martin Wilck [Mon, 16 Feb 2026 17:40:25 +0000 (18:40 +0100)]
feat(nvmf): enable adapting to NBFT reconfiguration
The cmdline() function of the nvmf module creates rd.nvmf.discover=
cmdline entries for all discovered subsystems. But this is often
not desirable for systems booting from an NBFT table, where the
contents of the table may change between reboots. With hard-coded
rd.nvmf.discover= entries, booting may fail if the NBFT configuration
has changed.
Compare the traddr/trsvcid pairs that appear in the block device
stack with the contents of the NBFT, and don't create rd.nvmf.discover=
entries for those that are matched.
Note: This approach is simplified, as entries might differ by
host_traddr. But such configurations are extremely rare, and
because we don't use interface-specific routes (VRF-lite) in the
initrd, omitting these entries can't cause boot failure, as long
as they match by transport, traddr, and trsvcid.
A follow-up patch will introduce an option to modify this behavior.
Martin Wilck [Mon, 16 Feb 2026 19:29:19 +0000 (20:29 +0100)]
fix(dracut.conf.5): move fstab/chroot warning to hostonly_mode section
The warning about using --fstab when chrooted belongs into the
hostonly_mode section, as can be seen in commit 888d53f ("replace xml
documentation with asciidoc"). It seems to have moved slowly downward.
Fix it.
fix(network-legacy): sanitize DHCP values in dhclient-script.sh
A rogue DHCP server can inject shell commands through hostname,
domain, gateway, and classless static route values. These values
are written to /tmp files that setup_net() later sources as shell.
- Sanitize hostname to RFC 952 chars (a-zA-Z0-9.-)
- Strip control chars from domain (like search already does)
- Validate gateway IPs contain only digits and dots
- Single-quote interpolated values in generated shell commands
- Validate all parse_option_121 octets are numeric upfront;
the existing inline checks only validated mask and the first
destination octet, leaving dest octets 2-4 and all four
gateway octets unchecked — those flow into shell commands
written to the initqueue/setup_net_"$netif".sh hook script
via echo
Fixes: CVE-2026-6893 Co-developed-by: Claude Opus 4.6 <noreply@anthropic.com>
Benjamin Drung [Tue, 31 Mar 2026 14:15:49 +0000 (16:15 +0200)]
ci: switch from debian:latest to ubuntu:rolling
Commit 28323e6b769c ("ci: switch from ubuntu:devel to a more stable
debian:latest") switched away from the Ubuntu devel release (which can
be more unstable since it is a release in development) but also switched
from Ubuntu to Debian.
Switch to `ubuntu:rolling` which is the latest Ubuntu release which
should be stable enough for our purposes. Ubuntu gets a new release
every six month in comparsion to Debian which cuts a new release around
every two years.
Miao Wang [Fri, 3 Jul 2026 13:02:52 +0000 (21:02 +0800)]
fix(virtfs): move mount hook to pre-mount
Mount hooks are executed after sysroot.mount when systemd is used.
However, the systemd generated sysroot.mount from kernel cmdline will
always fail when the given root= begins with virtfs:, making the system
unable to start.
Moving the mount hook to pre-mount will mount the 9p virtfs directly
onto /sysroot and the generated sysroot.mount will be ignored. This
practice is similar to what is in virtiofs.
Miao Wang [Fri, 10 Jul 2026 09:12:51 +0000 (17:12 +0800)]
test(run-qemu): use -accel kvm instead of -enable-kvm
-enable-kvm is believed to be deprecated [1] and -accel kvm should be
used instead. -enable-kvm will not support new architectures even if KVM
is actually supported on these architectures. -accel kvm is recommended
instead as a unified option to enable KVM on all the architectures.
projects / thirdparty / dracut-ng.git / log
