Software 44856 Published by

Both systemd v261.3 and v20.5 are now available, delivering a curated batch of upstream fixes rather than new features. The updates bring proper recognition for Linux kernel 7.3's new failfs pseudo-filesystem, alongside updated kernel headers and a refreshed hardware database. Tagged by Luca Boccassi and cherry-picked primarily by Yu Watanabe, both releases are immutable and signed for security. Distributions tracking these branches should pull the patches now, though users seeking LUO/Kexec Handover or the cloud IMDS subsystem will need to upgrade to the full v261 feature set.



Systemd v261.3 and v260.5 hit your stable branches

Two patch releases drop today, bringing kernel header updates and failfs support.

Systemd has pushed v261.3 and v260.5 to its release channels as of September 10, 2026. If you are running a distro that tracks specific stable branches, these are the patches you will want to pull.

Both releases were tagged by Luca Boccassi and signed with a verified GPG key. They are immutable. The actual changes are a small, carefully selected slice of fixes cherry-picked from upstream main. Yu Watanabe did most of the backporting.

Systemd

What actually shipped today

The headline fix is failfs support. Linux kernel 7.3 introduced a new pseudo-filesystem for testing, and systemd was tripping over it during boot. Now it recognizes the type correctly. Next, kernel headers got a bump. v261.3 pulls headers through Linux 7.3-rc2, while v260.5 brings in headers up to 7.3-rc1 and back up to 7.2-rc5 for older setups. Both branches also refreshed their hardware database with entries from September 8, keeping device quirks current.

Keep in mind these are point releases, not feature drops. They do not ship the full v261 or v260 feature sets. If you want LUO/Kexec Handover, the cloud IMDS subsystem, or the new OOM rulesets, you are looking at the base v261.0 tag from earlier this year. Same goes for v260.x's earlier changes like the OpenSSL 3.0 baseline and the removal of rc-local.service. These patches just keep the branches from rotting in the meantime.

The bigger picture

The gap between these tags and main tells you where systemd is headed. v261 sits about 1,832 commits behind current development, while v260 trails by roughly 4,490. That wide margin on v260 reflects its age. It is the prior maintenance branch, and distributions not ready for v261 are slowly migrating over. Linux kernel version numbers have become a running joke at this point. Six months ago, rc2 looked like a number you would not see for another year. Now it is landing in upstream repositories, and your distro's packaging team has exactly one weekend to verify it does not break their build system. The v260 line itself raised the floor considerably. Linux kernel 5.10 minimum. glibc 2.34. OpenSSL 3.0. Python 3.9. Not exactly backward compatible, but deliberate.

It is a quiet update. You won't find new systemd units, new boot features, or major performance tweaks in these releases. But that is the point. Patch releases like this are the quiet maintenance layer that keeps rolling distributions from breaking when upstream kernel versions move fast. If your CI is currently flagging failfs as an unknown filesystem, this fixes it. If not, you can probably wait for the next point release.

Head here to grab the v261.3 release notes, and here for v260.5. The full changelogs for both are on GitHub if you want to audit the cherry-picks yourself.