Home/CVE/A flaw was found in Samba’s WINS server component when running as an Active Directory Domain Controller. The WINS prot
CVE
CVE-2026-3238
A flaw was found in Samba’s WINS server component when running as an Active Directory Domain Controller. The WINS prot
A flaw was found in Samba’s WINS server component when running as an Active Directory Domain Controller. The WINS protocol handlers for certain request types did not properly validate incoming packets, allowing an unauthenticated remote attacker to trigger a NULL pointer dereference and crash the WINS service using specially crafted UDP packets.
HIGH · CVSS 7.5
EPSS 0.00075
Schedule remediation
- SSVC automatable: yes - attacks can be scripted at scale
- CVSS base score ≥ 7.0
Sigma rules0
YARA rules0
Look this up elsewhere - one-click external pivots
▸
How to read a CVE - triage first, then detect and patch
This page is every public fact about CVE-2026-3238, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.
Triage: should I act now? Four signals, and they are not interchangeable:
CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked.
EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal.
CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score.
Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.
How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.
Then what - two workflows:
Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits.
PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.
Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).
◆
ATT&CK techniques
2Techniques this CVE enables - linked via CWECAPECATT&CK. High◆ = named directly in ATT&CK or Nuclei templates.
▤ Build a SIEM detection for these techniques⬡
Weakness Classification
CWE-476NULL Pointer Dereference
📦
Fixed versions by distribution
31The package version that resolves this CVE on each Linux distribution, from the vendor’s published security data. fixed in shows a patched version exists; open means the package is listed as affected with no fix yet.
alpine edgesamba fixed in 4.23.8-r0
suse sle15ldb-tools fixed in 0:4.21.10+git.501.277ba349a01-150700.3.26.1
suse sle15libldb-devel fixed in 0:4.21.10+git.501.277ba349a01-150700.3.26.1
suse sle15libldb2 fixed in 0:4.21.10+git.501.277ba349a01-150700.3.26.1
suse sle15libldb2-32bit fixed in 0:4.21.10+git.501.277ba349a01-150700.3.26.1
suse sle15libsamba-policy-devel fixed in 0:4.15.13+git.780.d2f53cbcded-150400.3.49.1
suse sle15libsamba-policy-python3-devel fixed in 0:4.19.8+git.473.51d12fd320c-150600.3.26.1
suse sle15libsamba-policy0-python3 fixed in 0:4.15.13+git.780.d2f53cbcded-150400.3.49.1
suse sle15python3-ldb fixed in 0:4.21.10+git.501.277ba349a01-150700.3.26.1
suse sle15samba fixed in 0:4.17.12+git.553.4b71189e782-150500.3.39.1
suse sle15samba-ad-dc-libs fixed in 0:4.15.13+git.780.d2f53cbcded-150400.3.49.1
suse sle15samba-ad-dc-libs-32bit fixed in 0:4.15.13+git.780.d2f53cbcded-150400.3.49.1
suse sle15samba-ceph fixed in 0:4.15.13+git.780.d2f53cbcded-150400.3.49.1
suse sle15samba-client fixed in 0:4.15.13+git.780.d2f53cbcded-150400.3.49.1
suse sle15samba-client-32bit fixed in 0:4.15.13+git.780.d2f53cbcded-150400.3.49.1
suse sle15samba-client-libs fixed in 0:4.17.12+git.553.4b71189e782-150500.3.39.1
suse sle15samba-client-libs-32bit fixed in 0:4.19.8+git.473.51d12fd320c-150600.3.26.1
suse sle15samba-dcerpc fixed in 0:4.17.12+git.553.4b71189e782-150500.3.39.1
suse sle15samba-devel fixed in 0:4.15.13+git.780.d2f53cbcded-150400.3.49.1
suse sle15samba-devel-32bit fixed in 0:4.15.13+git.780.d2f53cbcded-150400.3.49.1
suse sle15samba-dsdb-modules fixed in 0:4.15.13+git.780.d2f53cbcded-150400.3.49.1
suse sle15samba-gpupdate fixed in 0:4.17.12+git.553.4b71189e782-150500.3.39.1
suse sle15samba-ldb-ldap fixed in 0:4.15.13+git.780.d2f53cbcded-150400.3.49.1
suse sle15samba-libs fixed in 0:4.21.10+git.501.277ba349a01-150700.3.26.1
suse sle15samba-libs-32bit fixed in 0:4.17.12+git.553.4b71189e782-150500.3.39.1
suse sle15samba-libs-python3 fixed in 0:4.17.12+git.553.4b71189e782-150500.3.39.1
suse sle15samba-python3 fixed in 0:4.15.13+git.780.d2f53cbcded-150400.3.49.1
suse sle15samba-tool fixed in 0:4.15.13+git.780.d2f53cbcded-150400.3.49.1
suse sle15samba-winbind fixed in 0:4.17.12+git.553.4b71189e782-150500.3.39.1
suse sle15samba-winbind-libs fixed in 0:4.19.8+git.473.51d12fd320c-150600.3.26.1
suse sle15samba-winbind-libs-32bit fixed in 0:4.21.10+git.501.277ba349a01-150700.3.26.1
▣
Scoring & Timeline
7.5
HIGH · CVSS v3.1 · [email protected]
Attack Vector
Network
Adjacent
Local
Physical
Attack Complexity
Low
High
Privileges Required
None
Low
High
User Interaction
None
Required
Scope
Unchanged
Changed
Confidentiality
None
Low
High
Integrity
None
Low
High
Availability
None
Low
High
SSVC triage · cisa-vulnrichment
Exploitation
none
Automatable
yes
Technical impact
partial
SSVC asks the questions that actually drive patch urgency: is it being exploited, can attacks be automated, and how total is the impact.
⚑
Vendor Advisories
10suse-csafopenSUSE-SU-2026:20905-1
suse-csafSUSE-SU-2026:22045-1
suse-csafSUSE-SU-2026:2108-1
suse-csafopenSUSE-SU-2026:10884-1
usnUSN-8306-1