CVE-2026-31614
- Source
- https://cve.org/CVERecord?id=CVE-2026-31614
- Import Source
- https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2026-31614.json
- JSON Data
- https://api.test.osv.dev/v1/vulns/CVE-2026-31614
- Downstream
- Related
- Published
- 2026-04-24T14:42:34.153Z
- Modified
- 2026-07-03T18:29:30.254811397Z
- Summary
- smb: client: fix off-by-8 bounds check in check_wsl_eas()
- Details
-
In the Linux kernel, the following vulnerability has been resolved:
smb: client: fix off-by-8 bounds check in checkwsleas()
The bounds check uses (u8 *)ea + nlen + 1 + vlen as the end of the EA name and value, but eadata sits at offset sizeof(struct smb2filefulleainfo) = 8 from ea, not at offset 0. The strncmp() later reads ea->eadata[0..nlen-1] and the value bytes follow at eadata[nlen+1..nlen+vlen], so the actual end is ea->eadata + nlen + 1 + vlen. Isn't pointer math fun?
The earlier check (u8 *)ea > end - sizeof(*ea) only guarantees the 8-byte header is in bounds, but since the last EA is placed within 8 bytes of the end of the response, the name and value bytes are read past the end of iov.
Fix this mess all up by using ea->ea_data as the base for the bounds check.
An "untrusted" server can use this to leak up to 8 bytes of kernel heap into the EA name comparison and influence which WSL xattr the data is interpreted as.
- Database specific
{ "cna_assigner": "Linux", "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/31xxx/CVE-2026-31614.json" }- References
-
- https://git.kernel.org/stable/c/3d8b9d06bd3ac4c6846f5498800b0f5f8062e53b
- https://git.kernel.org/stable/c/5cc0574c84aa73946ade587c41e81757b8b01cb5
- https://git.kernel.org/stable/c/a893f1757d9a4009e4a8d7ceb2312142fe29cea4
- https://git.kernel.org/stable/c/b2b76d09a64c538c57006180103fc1841e8cfa66
- https://git.kernel.org/stable/c/ba3ad159aa61810bbe0acaf39578b1ebfb6f1a18
- https://git.kernel.org/stable/c/bfbc74df8bbe095b3ed68f6d4487b368af087890
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/31xxx/CVE-2026-31614.json
- https://nvd.nist.gov/vuln/detail/CVE-2026-31614
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Affected packages
Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Affected ranges
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced7449d736bbbd160c76b01b8fcdf72f58a8757d4bFixedbfbc74df8bbe095b3ed68f6d4487b368af087890
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introducedea41367b2a602f602ea6594fc4a310520dcc64f4Fixed5cc0574c84aa73946ade587c41e81757b8b01cb5Fixedb2b76d09a64c538c57006180103fc1841e8cfa66Fixedba3ad159aa61810bbe0acaf39578b1ebfb6f1a18Fixeda893f1757d9a4009e4a8d7ceb2312142fe29cea4Fixed3d8b9d06bd3ac4c6846f5498800b0f5f8062e53b
Affected versions
v6.*
Linux / Kernel
Package
- Name
- Kernel
Affected ranges
- Type
- ECOSYSTEM
- Events
-
Introduced0Unknown introduced version / All previous versions are affectedFixed6.6.136
- Type
- ECOSYSTEM
- Events
-
Introduced6.7.0Fixed6.12.83
- Type
- ECOSYSTEM
- Events
-
Introduced6.9.0Fixed6.18.24
- Type
- ECOSYSTEM
- Events
-
Introduced6.13.0Fixed6.19.14
- Type
- ECOSYSTEM
- Events
-
Introduced6.19.0Fixed7.0.1