CVE-2026-93812 json
ksmbd: fix sd_ndr.data memory leak in ksmbd_vfs_set_sd_xattr
published last mo. modified last mo. also EUVD-2026-86200
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 6%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: fix sd_ndr.data memory leak in ksmbd_vfs_set_sd_xattr
ndr_encode_v4_ntacl() allocates sd_ndr.data via kzalloc() at entry. If any subsequent ndr_write_*() call returns error during encoding, the allocated sd_ndr.data won't be freed and causes memory leak.
Move kfree(sd_ndr.data) into out label to ensure the buffer gets released on all success and error return paths.
Patch / fix
- Linux Linux 5.15.222, 6.1.189, 6.6.158, 6.12.111, 6.18.53, 7.2
- linux Debian 12 6.1.190-1
- linux Debian 13 6.12.111-1
- linux Debian 14 7.2.6-1
- linux-6.12 Debian 12 6.12.111-1~deb12u1
debian advisories DEBIAN-CVE-2026-93812
- linux Ubuntu 22.04 LTS 5.15.0-202.212
- linux Ubuntu 24.04 LTS 6.8.0-149.149
- linux Ubuntu 26.04 LTS 7.0.0-42.42
- linux-aws Ubuntu 22.04 LTS 5.15.0-1119.126
- linux-aws Ubuntu 24.04 LTS 6.8.0-1069.74
- linux-aws Ubuntu 26.04 LTS 7.0.0-1016.17
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1120.130
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1073.81
ubuntu advisories UBUNTU-CVE-2026-93812
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/306d6f370da7e0e5532dc51c972f4ce101e42431 commit
- git.kernel.org/stable/c/dc55270e410ccb4d24e637c13b5c4c25bcd106d7 commit
- git.kernel.org/stable/c/c866c3314a6853eb06c7a8bef67f43c8a8bdfb6e commit
- git.kernel.org/stable/c/9b4dec75498fd0a1c9eaea680aef59c9519eb16f commit
- git.kernel.org/stable/c/c521dd78e036b5e0cfd394dd2ff2218890dd9e41 commit
- git.kernel.org/stable/c/d4d56b00c7df88cd5751e7415bdfabc9fdbc82a7 commit
Is CVE-2026-93812 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-93812 updated cvss 7.1
kernel: ksmbd: fix sd_ndr.data memory leak in ksmbd_vfs_set_sd_xattr
-
Red Hat Enterprise Linux 10 kernelaffected: no fix planned “Will not fix”
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9 Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9not affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.17% chance of exploitation in the next 30 days, higher than 6% of all scored CVEs (FIRST EPSS, 2026-11-11).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/306d6f370da7e0e5532dc51c972f4ce101e42431
- git.kernel.org /stable/c/dc55270e410ccb4d24e637c13b5c4c25bcd106d7
- git.kernel.org /stable/c/c866c3314a6853eb06c7a8bef67f43c8a8bdfb6e
- git.kernel.org /stable/c/9b4dec75498fd0a1c9eaea680aef59c9519eb16f
- git.kernel.org /stable/c/c521dd78e036b5e0cfd394dd2ff2218890dd9e41
- git.kernel.org /stable/c/d4d56b00c7df88cd5751e7415bdfabc9fdbc82a7
Sources
- CVE List CVE-2026-93812
- NVD CVE-2026-93812
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.