Answer in brief
CVE-2026-43379 records a Critical severity (CVSS 9.8) vulnerability in ksmbd: fix use-after-free in smb_lazy_parent_lease_break_close(). 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.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=27b40b7bfcd121fe13a150ffe11957630cf49246 <bf4d66d72e4a9e268c1012c331ce9eaedb5e2086 || >=5fb282ba4fef8985a5acf2b32681f2ec07732561 <960699317d39f46611f4ebeb69edc567c1f4e6b6 || >=5fb282ba4fef8985a5acf2b32681f2ec07732561 <dbbd328cf58261ca239756fe1c0d10c9518d3399 || >=5fb282ba4fef8985a5acf2b32681f2ec07732561 <b3568347c51c46e2cabc356bc34676df98296619 || >=5fb282ba4fef8985a5acf2b32681f2ec07732561 <eac3361e3d5dd8067b3258c69615888eb45e9f25 || >=6.6.32 <6.6.130 | bf4d66d72e4a9e268c1012c331ce9eaedb5e2086, 960699317d39f46611f4ebeb69edc567c1f4e6b6, dbbd328cf58261ca239756fe1c0d10c9518d3399, b3568347c51c46e2cabc356bc34676df98296619, eac3361e3d5dd8067b3258c69615888eb45e9f25, 6.6.130 |
| Linux/Linuxgeneric | 6.9 | Not reported |
Published upstream
May 8, 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 use-after-free in smb_lazy_parent_lease_break_close() opinfo pointer obtained via rcu_dereference(fp->f_opinfo) is being accessed after rcu_read_unlock() has been called. This creates a race condition where the memory could be freed by a concurrent writer between the unlock and the subsequent pointer dereferences (opinfo->is_lease, etc.), leading to a use-after-free.
Quoted source text, attributed separately from HOL analysis.