Answer in brief
CVE-2026-64016 records a Unknown severity vulnerability in ksmbd: fix durable reconnect error path file lifetime. 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 | >=ce2e164c1c51c3f7813b80f8c926836e896bcbb3 <a1a39f227c80cbf369767badc32cba2b225147d1 || >=97a0cd55283b4e63fd92804da91c8d9896adcad9 <6cb0b9385320110fe24a5d5ac0000ade4bb3a3f3 || >=1baff47b81f94f9231c91236aa511420d0e266b9 <3515503322f4819277091839eed46b695096aca5 | a1a39f227c80cbf369767badc32cba2b225147d1, 6cb0b9385320110fe24a5d5ac0000ade4bb3a3f3, 3515503322f4819277091839eed46b695096aca5 |
| Linux/Linuxgeneric | >=6.18.33 <6.18.34 || >=7.0.10 <7.0.11 | 6.18.34, 7.0.11 |
Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 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: ksmbd: fix durable reconnect error path file lifetime After a durable reconnect succeeds, ksmbd_reopen_durable_fd() republishes the same ksmbd_file into the session volatile-id table. If smb2_open() then takes a later error path, cleanup first calls ksmbd_fd_put(work, fp) and then unconditionally calls ksmbd_put_durable_fd(dh_info.fp). In this case fp and dh_info.fp are the same object. The first put drops the reconnect lookup reference, but the final durable put can run __ksmbd_close_fd(NULL, fp). Because the final close is not session-aware, it can free the file object without removing the volatile-id entry that was just published into the session table. Use the session-aware put for the final reconnect drop when the reconnect had already succeeded and the error path is cleaning up the republished file. Earlier reconnect failures, before fp is assigned to dh_info.fp, keep using the durable-only put path.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-64016 records a Unknown severity vulnerability in ksmbd: fix durable reconnect error path file lifetime. 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 | >=ce2e164c1c51c3f7813b80f8c926836e896bcbb3 <a1a39f227c80cbf369767badc32cba2b225147d1 || >=97a0cd55283b4e63fd92804da91c8d9896adcad9 <6cb0b9385320110fe24a5d5ac0000ade4bb3a3f3 || >=1baff47b81f94f9231c91236aa511420d0e266b9 <3515503322f4819277091839eed46b695096aca5 | a1a39f227c80cbf369767badc32cba2b225147d1, 6cb0b9385320110fe24a5d5ac0000ade4bb3a3f3, 3515503322f4819277091839eed46b695096aca5 |
| Linux/Linuxgeneric | >=6.18.33 <6.18.34 || >=7.0.10 <7.0.11 | 6.18.34, 7.0.11 |
Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 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: ksmbd: fix durable reconnect error path file lifetime After a durable reconnect succeeds, ksmbd_reopen_durable_fd() republishes the same ksmbd_file into the session volatile-id table. If smb2_open() then takes a later error path, cleanup first calls ksmbd_fd_put(work, fp) and then unconditionally calls ksmbd_put_durable_fd(dh_info.fp). In this case fp and dh_info.fp are the same object. The first put drops the reconnect lookup reference, but the final durable put can run __ksmbd_close_fd(NULL, fp). Because the final close is not session-aware, it can free the file object without removing the volatile-id entry that was just published into the session table. Use the session-aware put for the final reconnect drop when the reconnect had already succeeded and the error path is cleaning up the republished file. Earlier reconnect failures, before fp is assigned to dh_info.fp, keep using the durable-only put path.
Quoted source text, attributed separately from HOL analysis.