smb: client: fix reparse buffer bounds in cifs_query_reparse_point() (Linux Linux)

CVE-2026-98168
Non disponible

En bref

Source
NVD
EPSS
EPSS 0.21 % · centile 11 ()
État
PUBLISHED
Publiée
Mise à jour
Attribuée par
Linux
Statut NVD
Received

Description

In the Linux kernel, the following vulnerability has been resolved: smb: client: fix reparse buffer bounds in cifs_query_reparse_point() In cifs_query_reparse_point(), the start >= end check before casting to struct reparse_data_buffer * only ensures the start pointer is within the response. It fails to verify that there is enough space remaining for the fixed 8-byte header of the structure. If a server provides a DataOffset that leaves less than 8 bytes remaining, the check passes, but subsequent reads of ReparseTag and ReparseDataLength will occur out-of-bounds. Fix this by ensuring the remaining space is at least the size of the reparse_data_buffer structure before accessing its fields.

Références

Références européennes

Avis du CERT-FR

Produits affectés

ProduitVersions
Linux · Linuxaffected 848d78e3625f15de09d34a562dc49a98b78a62f3 < aa00eead258e4fe8158a3a3e2d65facf06274abd ; affected 48ca7139ab7f0bbed95ff7a901ea497017769657 < 3d67f155fe5813cfb02a551a9a12d6ea06a902e9 ; affected 56e84c64fc257a95728ee73165456b025c48d408 < d1152c96a3002e3df6b9a5b007cecaa7b19b4f79 ; affected 56e84c64fc257a95728ee73165456b025c48d408 < 8dc5db3a0e583ea8d31d0613cefd99e93e095c3c ; affected 56e84c64fc257a95728ee73165456b025c48d408 < 5f0306e731e2f46e91419eae57eee3a241c055e0 ; affected c13b779d26b3702fba8f7d5fe757aba5bda85fd0
Linux · Linuxaffected 6.16 ; unaffected 0 < 6.16 ; unaffected 6.6.160 ≤ 6.6.* ; unaffected 6.12.112 ≤ 6.12.* ; unaffected 6.18.54 ≤ 6.18.* ; unaffected 7.2.8 ≤ 7.2.*

Sources

SourceLicence
CVE List (CVEProject cvelistV5)CVE Program Terms of Use
EPSS (FIRST.org)FIRST — attribution requested
ENISA EUVDENISA — reproduction authorised, source acknowledged
CERT-FR (ANSSI)Licence Ouverte / Etalab 2.0
NVD (NIST) via fkie-cad/nvd-json-data-feedsPublic domain — this product uses data from the NVD API but is not endorsed or certified by the NVD