Answer in brief
CVE-2025-40268 records a Unknown severity vulnerability in cifs: client: fix memory leak in smb3_fs_context_parse_param. 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 | >=af1a3d2ba9543e99d78914d8fb88b61d0531d9a1 <299bc05e1475a4aa1eb985ade8f39e68c1bba9b9 || >=af1a3d2ba9543e99d78914d8fb88b61d0531d9a1 <868fc62811d3fabcf5685e14f36377a855d5412d || >=af1a3d2ba9543e99d78914d8fb88b61d0531d9a1 <48c17341577e25a22feb13d694374b61d974edbc || >=af1a3d2ba9543e99d78914d8fb88b61d0531d9a1 <4515743cc7a42e1d67468402a6420c195532a6fa || >=af1a3d2ba9543e99d78914d8fb88b61d0531d9a1 <e8c73eb7db0a498cd4b22d2819e6ab1a6f506bd6 | 299bc05e1475a4aa1eb985ade8f39e68c1bba9b9, 868fc62811d3fabcf5685e14f36377a855d5412d, 48c17341577e25a22feb13d694374b61d974edbc, 4515743cc7a42e1d67468402a6420c195532a6fa, e8c73eb7db0a498cd4b22d2819e6ab1a6f506bd6 |
| Linux/Linuxgeneric | 5.11 | Not reported |
Published upstream
Dec 6, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 30, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 24, 2026
In the Linux kernel, the following vulnerability has been resolved: cifs: client: fix memory leak in smb3_fs_context_parse_param The user calls fsconfig twice, but when the program exits, free() only frees ctx->source for the second fsconfig, not the first. Regarding fc->source, there is no code in the fs context related to its memory reclamation. To fix this memory leak, release the source memory corresponding to ctx or fc before each parsing. syzbot reported: BUG: memory leak unreferenced object 0xffff888128afa360 (size 96): backtrace (crc 79c9c7ba): kstrdup+0x3c/0x80 mm/util.c:84 smb3_fs_context_parse_param+0x229b/0x36c0 fs/smb/client/fs_context.c:1444 BUG: memory leak unreferenced object 0xffff888112c7d900 (size 96): backtrace (crc 79c9c7ba): smb3_fs_context_fullpath+0x70/0x1b0 fs/smb/client/fs_context.c:629 smb3_fs_context_parse_param+0x2266/0x36c0 fs/smb/client/fs_context.c:1438
Quoted source text, attributed separately from HOL analysis.