Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/samba4: security bump version to 4.24.5
Date: Tue, 28 Jul 2026 20:53:46 +0200	[thread overview]
Message-ID: <7a07f37de158725221e503508527c3fd@free.fr> (raw)
In-Reply-To: <20260728173642.3515075-1-bernd@kuhls.net>

On 28/07/2026 19:36, Bernd Kuhls wrote:
> https://www.samba.org/samba/history/samba-4.24.5.html
> 
> This is a security release in order to address the following defects:
> 
> o CVE-2026-6949:
>   TSIG packet with name compression can crash DNS
> 
>    Incorrect size calculations when a TSIG record contains
>    compressed names can lead to a large out-of-bounds write
>    causing the server to crash.
> 
>    https://www.samba.org/samba/security/CVE-2026-6949.html
> 
> o CVE-2026-58216:
>   An authenticated user could possibly crash a KDC process
> 
>    A kpasswd packet that contains malformed ASN.1 might cause
>    the server to access 6 bytes of unallocated memory. This
>    memory is not exposed to the user, but in some
>    circumstances the server could crash.
> 
>    https://www.samba.org/samba/security/CVE-2026-58216.html
> 
> o CVE-2026-58218:
>   DNS signing DoS via TKEY name cache exhaustion
> 
>    An unauthenticated user can repeatedly register names TKEY
>    names, which floods a cache causing legitimate TKEYs to be
>    expunged. This can practically block the use DNS TSIG
>    signing.
> 
>    https://www.samba.org/samba/security/CVE-2026-58218.html
> 
> o CVE-2026-58221:
>   Samba AD authenticated LDAP access domain takeover
> 
>    Samba AD low-privilege authenticated LDAP access allows
>    modifications to internal LDB special DNs, which permits a
>    domain takeover.
> 
>    https://www.samba.org/samba/security/CVE-2026-58221.html
> 
> o CVE-2026-58222:
>   Samba AD LDAP Compare filter injection and trusted-request
>    confusion disclose protected attributes
> 
>    An ordinary authenticated domain user can bypass access
>    checks and query confidential Active Directory attributes
>    (such as KDS root keys) via LDAP Compare requests. Due to a
>    filter injection flaw and trusted execution context, the
>    LDAP Compare operation can be turned into a
>    protected-attribute disclosure oracle.
> 
>    https://www.samba.org/samba/security/CVE-2026-58222.html
> 
> o CVE-2026-58224:
>   The CTDB protocol has bounds checking issues
> 
>    CTDB fails to do integrity checking of received packets.
>    This includes failure to check field lengths against packet
>    lengths when unmarshalling packets.
> 
>    https://www.samba.org/samba/security/CVE-2026-58224.html
> 
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>

Applied to master, thanks.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2026-07-28 18:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-28 17:36 [Buildroot] [PATCH 1/1] package/samba4: security bump version to 4.24.5 Bernd Kuhls
2026-07-28 18:53 ` Julien Olivain via buildroot [this message]

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=7a07f37de158725221e503508527c3fd@free.fr \
    --to=buildroot@buildroot.org \
    --cc=bernd@kuhls.net \
    --cc=ju.o@free.fr \
    /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