Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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

Timeline

  1. ID reserved

    By Linux

  2. · 15 days later

    Published

  3. · 5 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-46139, by who scored it
Scored byCVSSScoreVector
NVDNVD · Undergoing Analysis3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.12% · top 98% of all CVEs (18 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 1593ddb37bd124c131fe635397df68e854a03108 – < 4c3ed344a970aad51388ac3b0145b98318f0e21f
    • affected da087905e3270e2291c0afae39a28e7d183e5ec3 – < 941a1e6eb35440336913afc88a82103291956d5d
    • affected 62e7dd0a39c2d0d7ff03274c36df971f1b3d2d0d – < be1ef9512a3f5a755895c24f31b334342f4aa15b
    • affected 62e7dd0a39c2d0d7ff03274c36df971f1b3d2d0d – < 9bdb2ca31368b7671949dfb94a5d57ffccd01edd
    • affected 62e7dd0a39c2d0d7ff03274c36df971f1b3d2d0d – < 5e489c6c47a2ac15edbaca153b9348e42c1eacab
    • affected 191f2f444745087c3c51fd6042a0e25f42315ab0
    • affected 6.12.23 – < 6.12.88
    • affected 6.13.11 – < 6.14
  • Linux · Linux

    • affected 6.14
    • unaffected < 6.14
    • unaffected 6.12.88 – ≤ 6.12.*
    • unaffected 6.18.30 – ≤ 6.18.*
    • unaffected 7.0.7 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-46139 badge
[![CVE-2026-46139](https://cveledger.app/badge/CVE-2026-46139.svg)](https://cveledger.app/cve/CVE-2026-46139)

Record last updated .