CVE-2026-31614smb: client: fix off-by-8 bounds check in check_wsl_eas()
- 7.1HighCVSS base score
- 0.13%Exploitation in 30 daysEPSS · top 98% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: smb: client: fix off-by-8 bounds check in check_wsl_eas() The bounds check uses (u8 *)ea + nlen + 1 + vlen as the end of the EA name and value, but ea_data sits at offset sizeof(struct smb2_file_full_ea_info) = 8 from ea, not at offset 0. The strncmp() later reads ea->ea_data[0..nlen-1] and the value bytes follow at ea_data[nlen+1..nlen+vlen], so the actual end is ea->ea_data + 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.
Timeline
ID reserved
By Linux
- 46 days later
· 46 days later
Published
- 7 months later
· 7 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
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | High7.1 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.13% · top 98% of all CVEs (19 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.1.
Affected products
- affected 7449d736bbbd160c76b01b8fcdf72f58a8757d4b – < bfbc74df8bbe095b3ed68f6d4487b368af087890
- affected ea41367b2a602f602ea6594fc4a310520dcc64f4 – < 5cc0574c84aa73946ade587c41e81757b8b01cb5
- affected ea41367b2a602f602ea6594fc4a310520dcc64f4 – < b2b76d09a64c538c57006180103fc1841e8cfa66
- affected ea41367b2a602f602ea6594fc4a310520dcc64f4 – < ba3ad159aa61810bbe0acaf39578b1ebfb6f1a18
- affected ea41367b2a602f602ea6594fc4a310520dcc64f4 – < a893f1757d9a4009e4a8d7ceb2312142fe29cea4
- affected ea41367b2a602f602ea6594fc4a310520dcc64f4 – < 3d8b9d06bd3ac4c6846f5498800b0f5f8062e53b
- affected 6.6.32 – < 6.6.136
- affected 6.9
- unaffected < 6.9
- unaffected 6.6.136 – ≤ 6.6.*
- unaffected 6.12.83 – ≤ 6.12.*
- unaffected 6.18.24 – ≤ 6.18.*
- unaffected 6.19.14 – ≤ 6.19.*
- unaffected 7.0.1 – ≤ 7.0.*
- unaffected 7.1 – ≤ *
References
References6
- https://git.kernel.org/stable/c/bfbc74df8bbe095b3ed68f6d4487b368af087890 (opens in a new tab)
- https://git.kernel.org/stable/c/5cc0574c84aa73946ade587c41e81757b8b01cb5 (opens in a new tab)
- https://git.kernel.org/stable/c/b2b76d09a64c538c57006180103fc1841e8cfa66 (opens in a new tab)
- https://git.kernel.org/stable/c/ba3ad159aa61810bbe0acaf39578b1ebfb6f1a18 (opens in a new tab)
- https://git.kernel.org/stable/c/a893f1757d9a4009e4a8d7ceb2312142fe29cea4 (opens in a new tab)
- https://git.kernel.org/stable/c/3d8b9d06bd3ac4c6846f5498800b0f5f8062e53b (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-25507 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-31614)Record last updated .