Skip to content
Systems

CVE-2026-72382

8.8
High
EPSS 0.59%Patch availableAug 17, 2026

Kernel ksmbd DACL parse flaw allows remote memory exhaustion and crash via SMB2_SET_INFO.

common questions

Is CVE-2026-72382 being exploited?

Not confirmed. CVE-2026-72382 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.59% probability of exploitation in the next 30 days.

How severe is CVE-2026-72382?

CVE-2026-72382 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-72382?

Yes. A fix has been recorded for CVE-2026-72382. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-72382 affect?

CVE-2026-72382 affects Linux kernel (ksmbd SMB server module), Linux distributions with ksmbd enabled. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-72382?

Apply kernel/ksmbd patches or update kernels; disable ksmbd or block SMB if patching delayed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Linux kernel (ksmbd SMB server module)Linux distributions with ksmbd enabled
impact

Remote attacker can send crafted SMB2_SET_INFO security descriptors to force oversized kernel allocations, causing OOM/crash (remote DoS) and possible memory corruption.

action required

Immediate action required

affected versions
Linux Linux
  • affected>= e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 and < 16fb65ec15fe7c90f50a2115854bfd9a032d4023
  • affected>= e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 and < 282847c0cf22f2e961155ac8e42f6eeab7e16049
  • affected>= e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 and < d020e7f27bf65eecd3805404702f716b2b6d9e73
  • affected>= e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 and < 15a9e9b8f7f5d7f380ae54c6f5bcbc0bdcb0f3cd
  • affected>= e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 and < 60908f7ebcd9b6cde74ad5711fab0f49c7970949
  • affected5.15
vendor says fixed in< 5.15, >= 6.6.145 and <= 6.6.*, >= 6.12.97 and <= 6.12.*, >= 6.18.40 and <= 6.18.*, >= 7.1.5 and <= 7.1.*, >= 7.2 and <= *

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free