Learn Samba - Samba 4.24 & the Latest Features

#Introduction

Every previous episode used Samba — but have you ever stopped to ask which version you're running and what's new in it? In episode 17 we cover Samba's release lifecycle, especially the 4.24 series (2026): what changed, which are "security releases", and how to choose a version for production. This knowledge isn't trivia — it determines whether your server gets security fixes on time.

#Series 4.24.x: What's New in 2026

#Release Timeline

Samba follows a major release every ~6 months rhythm with many patch/security releases in between. For the 4.24 series:

4.24.0 — released 18 March 2026, opening the newest series.
4.24.2 — May 2026 (security release).
4.24.4 — June 2026 (security release).
4.24.5 — 28 July 2026, current stable — the version used in this series.

Check the running Samba version

smbd --version

An output of Version 4.24.5 means you're on current stable — a good benchmark for production.

#Areas of Improvement

Three areas are the focus of the 4.24 series:

AD DC: improvements in replication, schema consistency, and compatibility with modern Windows clients — Samba domains are less and less "surprising" when used with the latest Windows.
SMB3 enhancements: refinements to signing/encryption, lock handling, and oplock behavior — continuing what we covered in episode 8.
Security: every patch release (4.24.2, 4.24.4) carries CVE fixes — the reason why always upgrading to the latest patch release is a rule, not a suggestion.

#Security Release Policy

Samba publishes security releases in coordination with MITRE/CERT — details announced at samba.org/samba/latest_news.html. Correct practices for admins:

Monitor the latest news page and the samba-announce mailing list.
Upgrade to the latest patch of the series you use — don't delay security releases.
Test in staging before production (episode 3: testparm, reload).

Important

The difference between "feature release" and "security release" is very important. Never delay a security release — CVEs in Samba are often easy to exploit (this protocol is exposed to the network). Follow the policy: production must always be at the latest patch level of a supported series, and you need a fast test path (staging → production) so upgrades don't pile up.

#History: From 4.20 to 4.23

#Version Map

Leading up to 4.24, here's the path taken:

4.20 (October 2024): focused on SMB3 and AD DC fixes; beginning of client multichannel support.
4.21: internal refinements, security fixes.
4.22 (2025): SMB3 enhancements, more stable AD support — a version widely used in production in 2025.
4.23: the successor to 4.22, preparation toward 4.24.

In mid-2026, some older series are still supported: 4.23.11 (3 August 2026) and 4.22.11 still receive patches — while 4.24 is current stable.

Series status in mid-2026

4.24.x  current stable (4.24.5)
4.23.x  didukung       (4.23.11)
4.22.x  didukung       (4.22.11)
4.21.x  akhir masa hidup
4.20.x  akhir masa hidup

#Distribution LTS Support

It's important to realize: the distribution's package version ≠ upstream version. Ubuntu LTS and RHEL pin specific Samba versions for the entire life of the release — for example, some LTS releases ship Samba 4.19/4.20-series versions. This means:

You get stability and security backports from the vendor, but not automatically the newest upstream features.
For new features (like 4.24), install from source or a third-party repo — but be aware of the maintenance trade-offs.
Always prioritize vendor security (CVE backports) over chasing the highest version number, unless there's a feature you truly need.

Tip

A healthy habit: record the Samba version in your inventory and mark it "has the latest security patch". Check periodically with smbd --version on every host and compare against the series status at samba.org. Well-inventoried servers won't get "forgotten" when a CVE comes out.

#Choosing a Version for Production

#Decision Framework

All new, want the latest features → 4.24.x (latest patch).
Need vendor stability → follow the version shipped by the LTS distribution, making sure security backports are active.
Mixed environment with legacy clients → still 4.24.x with an appropriate server min protocol (episode 14), not a move back to an old version.

#Verifying the Patch Level

Package version from the package manager

dpkg -l | grep samba          # Debian/Ubuntu
rpm -q samba                  # RHEL family

And always check whether the installed version is on the supported versions list at samba.org before deciding "this is my production version".

#Closing

Key takeaways:

4.24.0 released 18 March 2026; current stable 4.24.5 (28 July 2026) — this series' reference version.
Routine security releases (4.24.2 May, 4.24.4 June 2026) — upgrading patches is a mandatory rule.
4.24 improvement focus: AD DC fixes, SMB3 enhancements, and security.
Recent history: 4.20 (2024) → 4.22 (2025) → 4.23; 4.22/4.23 still supported.
LTS distribution version ≠ upstream — balance vendor stability vs new features.

In episode 18 next, we'll cover clustering & scale-out (CTDB) — clustering Samba for high availability and scale-out nodes, with shared storage like GPFS/Ceph as the foundation. From one server to a collection of servers serving an enterprise NAS!