CVE-2026-72382: ksmbd: reject undersized DACLs before parsing ACEs
Noroxi assessment
Priority: Monitor (action score 35/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.68% (FIRST EPSS); higher than 52.6% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 15a9e9b8f7f5d7f380ae54c6f5bcbc0bdcb0f3cd, 16fb65ec15fe7c90f50a2115854bfd9a032d4023, 282847c0cf22f2e961155ac8e42f6eeab7e16049.
Low priority for now. Upgrade to Linux Linux 15a9e9b8f7f5d7f380ae54c6f5bcbc0bdcb0f3cd, 16fb65ec15fe7c90f50a2115854bfd9a032d4023, 282847c0cf22f2e961155ac8e42f6eeab7e16049 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: reject undersized DACLs before parsing ACEs parse_dacl() limits the attacker-controlled ACE count by comparing it with the number of minimal ACEs that fit in the DACL size. The DACL size field is 16 bits, but the expression subtracts sizeof(struct smb_acl). Because sizeof() is unsigned, a DACL size smaller than the ACL header underflows to a large size_t. A malicious client can reach this with: SMB2_SET_INFO (InfoType=SMB2_O_INFO_SECURITY) -> smb2_set_info_sec() -> set_info_sec() -> parse_sec_desc() -> parse_dacl() -> init_acl_state(..., 0xffff) -> init_acl_state(..., 0xffff) -> kmalloc_objs(..., 0xffff) Thus a malformed security descriptor can make num_aces pass the guard and drive large temporary ACL state and pointer-array allocations. Reject DACLs smaller than struct smb_acl before doing the subtraction, so the ACE count check cannot be bypassed by the underflow.
- Published
- Aug 15, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.6% · 52th percentile
- CWE
- —
Report tools
Action score
35
Monitor
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 8.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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
- e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 and later · before 8dc949061e35427433feac3ebe5ec089f2aa857eaffected · git
- e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 and later · before 16fb65ec15fe7c90f50a2115854bfd9a032d4023affected · git
- e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 and later · before 282847c0cf22f2e961155ac8e42f6eeab7e16049affected · git
- e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 and later · before d020e7f27bf65eecd3805404702f716b2b6d9e73affected · git
- e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 and later · before 15a9e9b8f7f5d7f380ae54c6f5bcbc0bdcb0f3cdaffected · git
- e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 and later · before 60908f7ebcd9b6cde74ad5711fab0f49c7970949affected · git
- before 5.15not affected · semver
- 6.1.191 and later · up to and including 6.1.*not affected · semver
- 6.6.145 and later · up to and including 6.6.*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 | from 0 | — |
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-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-72379Aug 15, 2026 · fs: refuse O_TMPFILE creation with an unmapped fsuid or fsgid0Monitor
- ← EarlierCVE-2026-72380Aug 15, 2026 · xen/pvcalls: bound backend response req_id before indexing rsp[]35Monitor
- Later →CVE-2026-72383Aug 15, 2026 · sctp: fix addr_wq_timer race in sctp_free_addr_wq()31Monitor
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 | 15a9e9b8f7f5d7f380ae54c6f5bcbc0bdcb0f3cd | Vendor (CNA) |
| Linux Linux | 16fb65ec15fe7c90f50a2115854bfd9a032d4023 | Vendor (CNA) |
| Linux Linux | 282847c0cf22f2e961155ac8e42f6eeab7e16049 | Vendor (CNA) |
| Linux Linux | 60908f7ebcd9b6cde74ad5711fab0f49c7970949 | Vendor (CNA) |
| Linux Linux | 8dc949061e35427433feac3ebe5ec089f2aa857e | Vendor (CNA) |
| Linux Linux | d020e7f27bf65eecd3805404702f716b2b6d9e73 | Vendor (CNA) |
| debian:linux | 6.12.100-1 · Debian:13 | 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
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
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/16fb65ec15fe7c90f50a2115854bfd9a032d4023
- git.kernel.org/stable/c/282847c0cf22f2e961155ac8e42f6eeab7e16049
- git.kernel.org/stable/c/60908f7ebcd9b6cde74ad5711fab0f49c7970949
- git.kernel.org/stable/c/8dc949061e35427433feac3ebe5ec089f2aa857e
- git.kernel.org/stable/c/d020e7f27bf65eecd3805404702f716b2b6d9e73
Vendor advisories and official records. Exploit/PoC links are deliberately left out.