CVE-2026-93812: ksmbd: fix sd_ndr.data memory leak in ksmbd_vfs_set_sd_xattr
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Fixed version: Linux Linux 306d6f370da7e0e5532dc51c972f4ce101e42431, 9b4dec75498fd0a1c9eaea680aef59c9519eb16f, c521dd78e036b5e0cfd394dd2ff2218890dd9e41; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes.
Low priority for now. Upgrade to Linux Linux 306d6f370da7e0e5532dc51c972f4ce101e42431, 9b4dec75498fd0a1c9eaea680aef59c9519eb16f, c521dd78e036b5e0cfd394dd2ff2218890dd9e41; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 24, 2026
- Updated
- Oct 3, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.15affected
- 303fff2b8c77a85c62dbde3b27c24b084144c04c and later · before 306d6f370da7e0e5532dc51c972f4ce101e42431affected · git
- 303fff2b8c77a85c62dbde3b27c24b084144c04c and later · before dc55270e410ccb4d24e637c13b5c4c25bcd106d7affected · git
- 303fff2b8c77a85c62dbde3b27c24b084144c04c and later · before c866c3314a6853eb06c7a8bef67f43c8a8bdfb6eaffected · git
- 303fff2b8c77a85c62dbde3b27c24b084144c04c and later · before 9b4dec75498fd0a1c9eaea680aef59c9519eb16faffected · git
- 303fff2b8c77a85c62dbde3b27c24b084144c04c and later · before c521dd78e036b5e0cfd394dd2ff2218890dd9e41affected · git
- 303fff2b8c77a85c62dbde3b27c24b084144c04c and later · before d4d56b00c7df88cd5751e7415bdfabc9fdbc82a7affected · git
- before 5.15not affected · semver
- 5.15.222 and later · up to and including 5.15.*not affected · semver
- 6.1.189 and later · up to and including 6.1.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-93810Sep 24, 2026 · cachefiles: Fix double fput28Monitor
- ← EarlierCVE-2026-93811Sep 24, 2026 · ksmbd: Fix acl.sd_buf memory leak and invalid sd_size error handling0Monitor
- Later →CVE-2026-93813Sep 24, 2026 · btrfs: tree-checker: validate INODE_REF's namelen31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 306d6f370da7e0e5532dc51c972f4ce101e42431 | Vendor (CNA) |
| Linux Linux | 9b4dec75498fd0a1c9eaea680aef59c9519eb16f | Vendor (CNA) |
| Linux Linux | c521dd78e036b5e0cfd394dd2ff2218890dd9e41 | Vendor (CNA) |
| Linux Linux | c866c3314a6853eb06c7a8bef67f43c8a8bdfb6e | Vendor (CNA) |
| Linux Linux | d4d56b00c7df88cd5751e7415bdfabc9fdbc82a7 | Vendor (CNA) |
| Linux Linux | dc55270e410ccb4d24e637c13b5c4c25bcd106d7 | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/9b4dec75498fd0a1c9eaea680aef59c9519eb16f
- git.kernel.org/stable/c/c521dd78e036b5e0cfd394dd2ff2218890dd9e41
- git.kernel.org/stable/c/c866c3314a6853eb06c7a8bef67f43c8a8bdfb6e
- git.kernel.org/stable/c/d4d56b00c7df88cd5751e7415bdfabc9fdbc82a7
- git.kernel.org/stable/c/dc55270e410ccb4d24e637c13b5c4c25bcd106d7
Vendor advisories and official records. Exploit/PoC links are deliberately left out.