Answer in brief
CVE-2025-38737 records a Critical severity (CVSS 9.8) vulnerability in cifs: Fix oops due to uninitialised variable. 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.
CVSS is 9.8. 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.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.17:rc1:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.17:rc2:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=a2906d3316fc19bf0ade84618bb73eab604c447e <4931fe2dbe1cc0e7d350a4b51b0b330e43971d98 || >=a2906d3316fc19bf0ade84618bb73eab604c447e <6adaa9fae36f848afa7278945d725e197e33c496 || >=a2906d3316fc19bf0ade84618bb73eab604c447e <453a6d2a68e54a483d67233c6e1e24c4095ee4be | 4931fe2dbe1cc0e7d350a4b51b0b330e43971d98, 6adaa9fae36f848afa7278945d725e197e33c496, 453a6d2a68e54a483d67233c6e1e24c4095ee4be |
| Linux/Linuxgeneric | 6.12 | Not reported |
Published upstream
Sep 5, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: cifs: Fix oops due to uninitialised variable Fix smb3_init_transform_rq() to initialise buffer to NULL before calling netfs_alloc_folioq_buffer() as netfs assumes it can append to the buffer it is given. Setting it to NULL means it should start a fresh buffer, but the value is currently undefined.
Quoted source text, attributed separately from HOL analysis.