CVE-2026-97559

Vulnérabilité non évaluée dans Linux (Linux)

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : <=*, <d433376abc47e10870ae732f89c7c1a60b199a0c, <=6.12.*, <d05045177a855386bca5e1909e08d06290e6e3b3, 7.2.7, 6.12.112, <=6.18.*, <2ef532a01f44687f5b95001e88247cf05bff9892, 5.12, 6.18.53, 0, 7.3, <5.12, <=7.2.*, <ee13d687d06a6fbb2008625dd560c654231b28e0, f5065508897a922327f32223082325d10b069ebc

Description

In the Linux kernel, the following vulnerability has been resolved: smb: client: fail DACL rewrite when the new DACL exceeds 64K replace_sids_and_copy_aces() and set_chmod_dacl() accumulate the size of the DACL they build in a u16. That accumulator can wrap. validate_dacl() caps num_aces at (dacl_size - sizeof(struct smb_acl)) / 20, i.e. 3276 for a maximally sized DACL, while each rewritten ACE can grow to sizeof(struct smb_ace) (76 bytes) once its SID is replaced with one carrying SID_MAX_SUB_AUTHORITIES sub-authorities. The worst case is therefore sizeof(struct smb_acl) + 3276 * 76 = 248984 bytes, far beyond what a u16 can hold. A wraparound is reached with 863 ACEs. After the wraparound, ndacl_ptr->size becomes meaningless and the offset will point anywhere in the ACE array. As a result, we will see corruption of the DACL, which then gets sent to the server. This is not an out-of-bounds write as the allocation now covers the worst-case expansion, so writes will always go into the buffer. Adjust the code to use a u32 internally and return -EOVERFLOW in the overflow case. The operation must be refused, because a DACL can only hold 2^16-1 bytes on the wire and larger DACLs cannot be represented. set_chmod_dacl() carries the same pattern and is fixed the same way. It only wraps once the source DACL comes within roughly 380 bytes of the 64K ceiling, but the failure mode is identical.

Gravité et risque d'exploitation

CVE-2026-97559 obtient un score CVSS de 0.0/10, soit une gravité non évaluée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.20 %, ce qui la place devant 9.3 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=*, <d433376abc47e10870ae732f89c7c1a60b199a0c, <=6.12.*, <d05045177a855386bca5e1909e08d06290e6e3b3, 7.2.7, 6.12.112, <=6.18.*, <2ef532a01f44687f5b95001e88247cf05bff9892, 5.12, 6.18.53, 0, 7.3, <5.12, <=7.2.*, <ee13d687d06a6fbb2008625dd560c654231b28e0, f5065508897a922327f32223082325d10b069ebc) est présent sur votre parc.
  • Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
  • À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
  • Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références