Answer in brief
CVE-2026-31614 records a Unknown severity vulnerability in smb: client: fix off-by-8 bounds check in check_wsl_eas(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=7449d736bbbd160c76b01b8fcdf72f58a8757d4b <bfbc74df8bbe095b3ed68f6d4487b368af087890 || >=ea41367b2a602f602ea6594fc4a310520dcc64f4 <5cc0574c84aa73946ade587c41e81757b8b01cb5 || >=ea41367b2a602f602ea6594fc4a310520dcc64f4 <b2b76d09a64c538c57006180103fc1841e8cfa66 || >=ea41367b2a602f602ea6594fc4a310520dcc64f4 <ba3ad159aa61810bbe0acaf39578b1ebfb6f1a18 || >=ea41367b2a602f602ea6594fc4a310520dcc64f4 <a893f1757d9a4009e4a8d7ceb2312142fe29cea4 || >=ea41367b2a602f602ea6594fc4a310520dcc64f4 <3d8b9d06bd3ac4c6846f5498800b0f5f8062e53b || >=6.6.32 <6.6.136 | bfbc74df8bbe095b3ed68f6d4487b368af087890, 5cc0574c84aa73946ade587c41e81757b8b01cb5, b2b76d09a64c538c57006180103fc1841e8cfa66, ba3ad159aa61810bbe0acaf39578b1ebfb6f1a18, a893f1757d9a4009e4a8d7ceb2312142fe29cea4, 3d8b9d06bd3ac4c6846f5498800b0f5f8062e53b, 6.6.136 |
| Linux/Linuxgeneric | 6.9 | Not reported |
Published upstream
Apr 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 6, 2026
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.
Quoted source text, attributed separately from HOL analysis.