Answer in brief
CVE-2024-40909 records a Unknown severity vulnerability in bpf: Fix a potential use-after-free in bpf_link_free(). 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 | >=876941f533e7b47fc69977fc4551c02f2d18af97 <91cff53136daeff50816b0baeafd38a6976f6209 || >=1a80dbcb2dbaf6e4c216e62e30fa7d3daa8001ce <fa97b8fed9896f1e89cb657513e483a152d4c382 || >=1a80dbcb2dbaf6e4c216e62e30fa7d3daa8001ce <2884dc7d08d98a89d8d65121524bb7533183a63a || 5d8d447777564b35f67000e7838e7ccb64d525c8 || >=6.6.26 <6.6.35 || >=6.8.5 <6.9 | 91cff53136daeff50816b0baeafd38a6976f6209, fa97b8fed9896f1e89cb657513e483a152d4c382, 2884dc7d08d98a89d8d65121524bb7533183a63a, 6.6.35, 6.9 |
| Linux/Linuxgeneric | 6.9 | Not reported |
Published upstream
Jul 12, 2024
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: bpf: Fix a potential use-after-free in bpf_link_free() After commit 1a80dbcb2dba, bpf_link can be freed by link->ops->dealloc_deferred, but the code still tests and uses link->ops->dealloc afterward, which leads to a use-after-free as reported by syzbot. Actually, one of them should be sufficient, so just call one of them instead of both. Also add a WARN_ON() in case of any problematic implementation.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-40909 records a Unknown severity vulnerability in bpf: Fix a potential use-after-free in bpf_link_free(). 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 | >=876941f533e7b47fc69977fc4551c02f2d18af97 <91cff53136daeff50816b0baeafd38a6976f6209 || >=1a80dbcb2dbaf6e4c216e62e30fa7d3daa8001ce <fa97b8fed9896f1e89cb657513e483a152d4c382 || >=1a80dbcb2dbaf6e4c216e62e30fa7d3daa8001ce <2884dc7d08d98a89d8d65121524bb7533183a63a || 5d8d447777564b35f67000e7838e7ccb64d525c8 || >=6.6.26 <6.6.35 || >=6.8.5 <6.9 | 91cff53136daeff50816b0baeafd38a6976f6209, fa97b8fed9896f1e89cb657513e483a152d4c382, 2884dc7d08d98a89d8d65121524bb7533183a63a, 6.6.35, 6.9 |
| Linux/Linuxgeneric | 6.9 | Not reported |
Published upstream
Jul 12, 2024
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: bpf: Fix a potential use-after-free in bpf_link_free() After commit 1a80dbcb2dba, bpf_link can be freed by link->ops->dealloc_deferred, but the code still tests and uses link->ops->dealloc afterward, which leads to a use-after-free as reported by syzbot. Actually, one of them should be sufficient, so just call one of them instead of both. Also add a WARN_ON() in case of any problematic implementation.
Quoted source text, attributed separately from HOL analysis.