Answer in brief
CVE-2026-43366 records a Unknown severity vulnerability in io_uring/kbuf: check if target buffer list is still legacy on recycle. 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.
Answer in brief
CVE-2026-43366 records a Unknown severity vulnerability in io_uring/kbuf: check if target buffer list is still legacy on recycle. 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 | >=c7fb19428d67dd0a2a78a4f237af01d39c78dc5a <a7b33671e418fca507feebd1d56e7f4952a4b25c || >=c7fb19428d67dd0a2a78a4f237af01d39c78dc5a <439a6728ec4641ffad1ca796622c19bc525e570f || >=c7fb19428d67dd0a2a78a4f237af01d39c78dc5a <f3fb54e7a8b4aadcc2836ee463eec8c88709b8aa || >=c7fb19428d67dd0a2a78a4f237af01d39c78dc5a <50ad880db3013c6fee0ef13781762a39e2e7ef83 || >=c7fb19428d67dd0a2a78a4f237af01d39c78dc5a <97b57f69fee1b61b41acbf37e7720cac9d389fa4 || >=c7fb19428d67dd0a2a78a4f237af01d39c78dc5a <c2c185be5c85d37215397c8e8781abf0a69bec1f | a7b33671e418fca507feebd1d56e7f4952a4b25c, 439a6728ec4641ffad1ca796622c19bc525e570f, f3fb54e7a8b4aadcc2836ee463eec8c88709b8aa, 50ad880db3013c6fee0ef13781762a39e2e7ef83, 97b57f69fee1b61b41acbf37e7720cac9d389fa4, c2c185be5c85d37215397c8e8781abf0a69bec1f |
| Linux/Linuxgeneric | 5.19 | 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: io_uring/kbuf: check if target buffer list is still legacy on recycle There's a gap between when the buffer was grabbed and when it potentially gets recycled, where if the list is empty, someone could've upgraded it to a ring provided type. This can happen if the request is forced via io-wq. The legacy recycling is missing checking if the buffer_list still exists, and if it's of the correct type. Add those checks.
Quoted source text, attributed separately from HOL analysis.
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 | >=c7fb19428d67dd0a2a78a4f237af01d39c78dc5a <a7b33671e418fca507feebd1d56e7f4952a4b25c || >=c7fb19428d67dd0a2a78a4f237af01d39c78dc5a <439a6728ec4641ffad1ca796622c19bc525e570f || >=c7fb19428d67dd0a2a78a4f237af01d39c78dc5a <f3fb54e7a8b4aadcc2836ee463eec8c88709b8aa || >=c7fb19428d67dd0a2a78a4f237af01d39c78dc5a <50ad880db3013c6fee0ef13781762a39e2e7ef83 || >=c7fb19428d67dd0a2a78a4f237af01d39c78dc5a <97b57f69fee1b61b41acbf37e7720cac9d389fa4 || >=c7fb19428d67dd0a2a78a4f237af01d39c78dc5a <c2c185be5c85d37215397c8e8781abf0a69bec1f | a7b33671e418fca507feebd1d56e7f4952a4b25c, 439a6728ec4641ffad1ca796622c19bc525e570f, f3fb54e7a8b4aadcc2836ee463eec8c88709b8aa, 50ad880db3013c6fee0ef13781762a39e2e7ef83, 97b57f69fee1b61b41acbf37e7720cac9d389fa4, c2c185be5c85d37215397c8e8781abf0a69bec1f |
| Linux/Linuxgeneric | 5.19 | 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: io_uring/kbuf: check if target buffer list is still legacy on recycle There's a gap between when the buffer was grabbed and when it potentially gets recycled, where if the list is empty, someone could've upgraded it to a ring provided type. This can happen if the request is forced via io-wq. The legacy recycling is missing checking if the buffer_list still exists, and if it's of the correct type. Add those checks.
Quoted source text, attributed separately from HOL analysis.