CVE-2026-46139

smb: client: use kzalloc to zero-initialize security descriptor buffer

MEDIUM
5.5
CVSS Score
Published: May 28, 2026 at 09:35 AM UTC
Updated: June 27, 2026 at 11:41 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.1%

Description

In the Linux kernel, the following vulnerability has been resolved: smb: client: use kzalloc to zero-initialize security descriptor buffer Commit 62e7dd0a39c2d ("smb: common: change the data type of num_aces to le16") split struct smb_acl's __le32 num_aces field into __le16 num_aces and __le16 reserved. The reserved field corresponds to Sbz2 in the MS-DTYP ACL wire format, which must be zero [1]. When building an ACL descriptor in build_sec_desc(), we are using a kmalloc()'ed descriptor buffer and writing the fields explicitly using le16() writes now. This never writes to the 2 byte reserved field, leaving it as uninitialized heap data. When the reserved field happens to contain non-zero slab garbage, Samba rejects the security descriptor with "ndr_pull_security_descriptor failed: Range Error", causing chmod to fail with EINVAL. Change kmalloc() to kzalloc() to ensure the entire buffer is zero-initialized. [1] https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-dtyp/20233ed8-a6c6-4097-aafa-dd545ed24428

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≥ 6.13.116.12.23 ≤ v < 6.12.886.13.11 ≤ v < 6.146.14 ≤ v < 6.18.306.14 ≤ v < 7.0.76.14 ≤ v < 7.16.14.1 ≤ v < 6.18.306.19 ≤ v < 7.0.71593ddb37bd124c131fe635397df68e854a03108191f2f444745087c3c51fd6042a0e25f42315ab06.12.236.13.116.146.14 rc66.14 rc762e7dd0a39c2d0d7ff03274c36df971f1b3d2d0d7.1 rc17.1 rc2da087905e3270e2291c0afae39a28e7d183e5ec3
Vendor states this is fixed in 4c3ed344a970aad51388ac3b0145b98318f0e21f (fixed)
Vendor states this is fixed in 5e489c6c47a2ac15edbaca153b9348e42c1eacab (fixed)
Vendor states this is fixed in 941a1e6eb35440336913afc88a82103291956d5d (fixed)
Vendor states this is fixed in 9bdb2ca31368b7671949dfb94a5d57ffccd01edd (fixed)
Vendor states this is fixed in be1ef9512a3f5a755895c24f31b334342f4aa15b (fixed)
Vendor states this is fixed in 6.12.88 (unaffected)
Vendor states this is fixed in 6.14 (unaffected)
Vendor states this is fixed in 6.18.30 (unaffected)
Vendor states this is fixed in 7.0.7 (unaffected)
Vendor states this is fixed in 7.1 (unaffected)

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusUNDERGOING ANALYSIS
CWE
CWE-908

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card