Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bernd Kuhls <bernd@kuhls.net>
To: buildroot@buildroot.org
Cc: Christian Stewart <christian@aperture.us>
Subject: [Buildroot] [PATCH 2/5] package/docker-engine: security bump to version 28.5.2
Date: Sun, 16 Aug 2026 22:32:04 +0200	[thread overview]
Message-ID: <20260816203207.3980846-2-bernd@kuhls.net> (raw)
In-Reply-To: <20260816203207.3980846-1-bernd@kuhls.net>

https://github.com/moby/moby/releases/tag/v28.5.2
Fixes CVE-2025-31133, CVE-2025-52565 & CVE-2025-52881.

https://github.com/moby/moby/releases/tag/v28.5.1
https://github.com/moby/moby/releases/tag/v28.5.0
https://github.com/moby/moby/releases/tag/v28.4.0

Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
---
Gitlab pipelines passed:
https://gitlab.com/bkuhls/buildroot/-/commits/99b74ab8c322d7aacf9b9bee370fc273a0dc7fa5

 package/docker-engine/docker-engine.hash | 2 +-
 package/docker-engine/docker-engine.mk   | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/package/docker-engine/docker-engine.hash b/package/docker-engine/docker-engine.hash
index 7f305b6880..32bdb45ef5 100644
--- a/package/docker-engine/docker-engine.hash
+++ b/package/docker-engine/docker-engine.hash
@@ -1,3 +1,3 @@
 # Locally calculated
-sha256  3727c8963ab4bcff12291e99e4d4a6b9a29ace5236fd245717bbff648f15f8cd  docker-engine-28.3.3-go2.tar.gz
+sha256  0e450c03c536a1304ba8fd26ca4c4ff96fac62182fd042fec90ffdf4a0969d40  docker-engine-28.5.2-go2.tar.gz
 sha256  7c87873291f289713ac5df48b1f2010eb6963752bbd6b530416ab99fc37914a8  LICENSE
diff --git a/package/docker-engine/docker-engine.mk b/package/docker-engine/docker-engine.mk
index 2df260e1e5..bf2dc588fb 100644
--- a/package/docker-engine/docker-engine.mk
+++ b/package/docker-engine/docker-engine.mk
@@ -4,7 +4,7 @@
 #
 ################################################################################
 
-DOCKER_ENGINE_VERSION = 28.3.3
+DOCKER_ENGINE_VERSION = 28.5.2
 DOCKER_ENGINE_SITE = $(call github,moby,moby,v$(DOCKER_ENGINE_VERSION))
 
 DOCKER_ENGINE_LICENSE = Apache-2.0
-- 
2.47.3

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2026-08-16 20:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-16 20:32 [Buildroot] [PATCH 1/5] package/containerd: security bump version to 2.0.11 Bernd Kuhls
2026-08-16 20:32 ` Bernd Kuhls [this message]
2026-08-16 22:15   ` [Buildroot] [PATCH 2/5] package/docker-engine: security bump to version 28.5.2 Peter Korsgaard
2026-08-16 20:32 ` [Buildroot] [PATCH 3/5] package/docker-compose: bump to version 2.40.3 Bernd Kuhls
2026-08-16 22:16   ` Peter Korsgaard
2026-08-16 20:32 ` [Buildroot] [PATCH 4/5] package/docker-cli: bump version to 28.5.2 Bernd Kuhls
2026-08-16 22:15   ` Peter Korsgaard
2026-08-16 20:32 ` [Buildroot] [PATCH 5/5] package/runc: security bump version to 1.3.6 Bernd Kuhls
2026-08-16 22:20   ` Peter Korsgaard
2026-08-16 22:15 ` [Buildroot] [PATCH 1/5] package/containerd: security bump version to 2.0.11 Peter Korsgaard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260816203207.3980846-2-bernd@kuhls.net \
    --to=bernd@kuhls.net \
    --cc=buildroot@buildroot.org \
    --cc=christian@aperture.us \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox