This update for flake-pilot fixes the following issues:
Update version to 3.1.22.
- Fixes to use flakes as normal user
Running a flake is a container based instance provisioning
and startup. Some part of this process requires root permissions
for example mounting the container instance store for the
provisioning step. This commit fixes the required calls to
be properly managed by sudo.
- seed from entropy
- Fix assignment of random sequence number
We should use a seed for the sequence as described in
https://rust-random.github.io/book/guide-seeding.html#a-simple-number
In addition the logic when a random sequence number should
be used was wrong and needed a fix regarding resume and
attach type flakes which must not use a random sequence
- Pass --init option for resume type flakes
In resume mode a sleep command is used to keep the container
open. However, without the --init option there is no signal
handling available. This commit fixes it
- Revert "kill prior remove when using %remove flag"
This reverts commit 06c7d4aa71f74865dfecba399fd08cc2fde2e1f2.
no hard killing needed with the event loop entrypoint
- Fixed CVE-2025-55159 slab: incorrect bounds check
Update to slab 0.4.11 to fix the mentioned CVE.
This Fixes bsc#1248004
- Apply clippy fixes
- Create sequence number for the same invocation
If a flake which is not a resume or attach flake is called twice
with the same invocation arguments an error message is displayed
to give this invocation a new name via the @NAME runtime option.
This commit makes this more comfortable and automatically assigns
a random sequence number for the call if no @NAME is given.
- kill prior remove when using %remove flag
In case the container instance should be removed via the %remove
flag, send a kill first, followed by a force remove. The reason
for this is because we use a never ending sleep command as entry
point for resume type containers. If they should be removed the
standard signal send on podman rm will not stop the sleep and
after a period of 10 seconds podman sends a kill signal itself.
We can speedup this process as we know the entry point command
and send the kill signal first followed by the remove which
saves us some wait time spent in podman otherwise.
- Fix clippy hints
variables can be used directly in the format! string
- Prune old images after load
Make sure no <none> image references stay in the registry
This update for libssh fixes the following issues:
- CVE-2025-8114: Fixed NULL pointer dereference when calculating the session ID
during the key exchange (KEX) process (bsc#1246974)
- CVE-2025-8277: Fixed Memory Exhaustion via Repeated Key Exchange (bsc#1249375)
This update for chrony fixes the following issues:
- Update to version 4.8:
* Add maxunreach option to limit selection of unreachable sources
* Add -u option to chronyc to drop root privileges (default
chronyc user is set by configure script)
* Fix refclock extpps option to work on Linux >= 6.15
* Validate refclock samples for reachability updates
- Fix racy socket creation allowing privilege escalation to root (bsc#1246544)
- Update to version 4.7:
* Add opencommands directive to select remote monitoring
commands
* Add interval option to driftfile directive
* Add waitsynced and waitunsynced options to local directive
* Add sanity checks for integer values in configuration
* Add support for systemd Type=notify service
* Add RTC refclock driver
* Allow PHC refclock to be specified with network interface name
* Don’t require multiple refclock samples per poll to simplify
filter configuration
* Keep refclock reachable when dropping samples with large delay
* Improve quantile-based filtering to adapt faster to larger
delay
* Improve logging of selection failures
* Detect clock interference from other processes
* Try to reopen message log (-l option) on cyclelogs command
* Fix sourcedir reloading to not multiply sources
* Fix tracking offset after failed clock step
* Drop support for NTS with Nettle < 3.6 and GnuTLS < 3.6.14
* Drop support for building without POSIX threads
- Update to version 4.6.1:
* Add ntsaeads directive to enable only selected AEAD algorithms
for NTS.
* Negotiate use of compliant NTS keys with AES-128-GCM-SIV AEAD
algorithm.
* Switch to compliant NTS keys if first response from server is
NTS NAK.
- Drop rcFOO symlinks for CODE16 (PED-266).
- Update to version 4.6:
* Add activate option to local directive to set activation threshold
* Add ipv4 and ipv6 options to server/pool/peer directive
* Add kod option to ratelimit directive for server KoD RATE support
* Add leapseclist directive to read NIST/IERS leap-seconds.list file
* Add ptpdomain directive to set PTP domain for NTP over PTP
* Allow disabling pidfile
* Improve copy server option to accept unsynchronised status instantly
* Log one selection failure on start
* Add offset command to modify source offset correction
* Add timestamp sources to ntpdata report
* Fix crash on sources reload during initstepslew or RTC initialisation
* Fix source refreshment to not repeat failed name resolving attempts
- Update to version 4.5:
* Add support for AES-GCM-SIV in GnuTLS
* Add support for corrections from PTP transparent clocks
* Add support for systemd socket activation
* Fix presend in interleaved mode
* Fix reloading of modified sources from sourcedir
This update for rust-keylime fixes the following issues:
- CVE-2025-55159: slab: incorrect bounds check in get_disjoint_mut function can lead to undefined behavior or potential crash due to out-of-bounds access (bsc#1248006)
- CVE-2025-3416: openssl: Use-After-Free in Md::fetch and Cipher::fetch in rust-openssl crate (bsc#1242623)
- CVE-2024-58266: shlex: certain bytes allowed to appear unquoted and unescaped in command arguments (bsc#1247193)
- CVE-2024-43806: rustix: rustix::fs::Dir iterator with the linux_raw backend can cause memory explosion (bsc#1229952)
- CVE-2024-12224: idna: idna accepts Punycode labels that do not produce any non-ASCII when decoded (bsc#1243861)
- RUSTSEC-2024-0006: Multiple issues involving quote API (bsc#1230029)
This update for vim fixes the following issues:
- CVE-2025-53906: malicious zip archive may cause a path traversal (bsc#1246602)
- CVE-2025-53905: malicious tar archive may cause a path traversal (bsc#1246604)
- CVE-2025-55157: use-after-free in internal tuple reference management (bsc#1247938)
- CVE-2025-55158: double-free in internal typed value (typval_T) management (bsc#1247939)
This update for python-urllib3 fixes the following issues:
- CVE-2025-50181: Pool managers now properly control redirects when retries is passed (bsc#1244925)
This update for the Linux Kernel 5.14.21-150400_24_161 fixes several issues.
The following security issues were fixed:
- CVE-2024-53168: sunrpc: fix one UAF issue caused by sunrpc kernel tcp socket (bsc#1243650).
- CVE-2025-38477: net/sched: sch_qfq: Fix race condition on qfq_aggregate (bsc#1247315).
- CVE-2025-21791: vrf: use RCU protection in l3mdev_l3_out() (bsc#1240744).
This update for the Linux Kernel 5.3.18-150300_59_207 fixes one issue.
The following security issue was fixed:
- CVE-2025-38477: net/sched: sch_qfq: Fix race condition on qfq_aggregate (bsc#1247315).
This update for the Linux Kernel 5.3.18-150300_59_179 fixes several issues.
The following security issues were fixed:
- CVE-2024-53168: sunrpc: fix one UAF issue caused by sunrpc kernel tcp socket (bsc#1243650).
- CVE-2024-50154: tcp/dccp: Do not use timer_pending() in reqsk_queue_unlink() (bsc#1233072).
- CVE-2025-38477: net/sched: sch_qfq: Fix race condition on qfq_aggregate (bsc#1247315).
- CVE-2025-21791: vrf: use RCU protection in l3mdev_l3_out() (bsc#1240744).
- CVE-2025-21692: net: sched: fix ets qdisc OOB Indexing (bsc#1237048).
This update for the Linux Kernel 6.4.0-150700_51 fixes several issues.
The following security issues were fixed:
- CVE-2025-38477: net/sched: sch_qfq: Fix race condition on qfq_aggregate (bsc#1247315).
- CVE-2025-22023: usb: xhci: Don't skip on Stopped - Length Invalid (bsc#1246754).
- CVE-2025-38089: sunrpc: handle SVC_GARBAGE during svc auth processing as auth error (bsc#1245509).
This update for the Linux Kernel 6.4.0-150700_53_3 fixes several issues.
The following security issues were fixed:
- CVE-2025-38477: net/sched: sch_qfq: Fix race condition on qfq_aggregate (bsc#1247315).
- CVE-2025-38089: sunrpc: handle SVC_GARBAGE during svc auth processing as auth error (bsc#1245509).