Answer in brief
CVE-2022-49085 records a Unknown severity vulnerability in drbd: Fix five use after free bugs in get_initial_state. 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-2022-49085 records a Unknown severity vulnerability in drbd: Fix five use after free bugs in get_initial_state. 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 | >=a29728463b254ce81ecefdf20c1a02e01d9361da <0489700bfeb1e53eb2039c2291c67e71b0b40103 || >=a29728463b254ce81ecefdf20c1a02e01d9361da <dcf6be17b5c53b741898d2223b23e66d682de300 || >=a29728463b254ce81ecefdf20c1a02e01d9361da <188fe6b26765edbad4055611c0f788b6870f4024 || >=a29728463b254ce81ecefdf20c1a02e01d9361da <b6a4055036eed1f5e239ce3d8b0db1ce38bba447 || >=a29728463b254ce81ecefdf20c1a02e01d9361da <594205b4936771a250f9d141e7e0fff21c3dd2d9 || >=a29728463b254ce81ecefdf20c1a02e01d9361da <a972c768723359ec995579902473028fe3cd64b1 || >=a29728463b254ce81ecefdf20c1a02e01d9361da <de63e74da2333b4068bb79983e632db730fea97e || >=a29728463b254ce81ecefdf20c1a02e01d9361da <226e993c39405292781bfcf4b039a8db56aab362 || >=a29728463b254ce81ecefdf20c1a02e01d9361da <aadb22ba2f656581b2f733deb3a467c48cc618f6 | 0489700bfeb1e53eb2039c2291c67e71b0b40103, dcf6be17b5c53b741898d2223b23e66d682de300, 188fe6b26765edbad4055611c0f788b6870f4024, b6a4055036eed1f5e239ce3d8b0db1ce38bba447, 594205b4936771a250f9d141e7e0fff21c3dd2d9, a972c768723359ec995579902473028fe3cd64b1, de63e74da2333b4068bb79983e632db730fea97e, 226e993c39405292781bfcf4b039a8db56aab362, aadb22ba2f656581b2f733deb3a467c48cc618f6 |
| Linux/Linuxgeneric | 4.5 | Not reported |
Published upstream
Feb 26, 2025
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: drbd: Fix five use after free bugs in get_initial_state In get_initial_state, it calls notify_initial_state_done(skb,..) if cb->args[5]==1. If genlmsg_put() failed in notify_initial_state_done(), the skb will be freed by nlmsg_free(skb). Then get_initial_state will goto out and the freed skb will be used by return value skb->len, which is a uaf bug. What's worse, the same problem goes even further: skb can also be freed in the notify_*_state_change -> notify_*_state calls below. Thus 4 additional uaf bugs happened. My patch lets the problem callee functions: notify_initial_state_done and notify_*_state_change return an error code if errors happen. So that the error codes could be propagated and the uaf bugs can be avoid. v2 reports a compilation warning. This v3 fixed this warning and built successfully in my local environment with no additional warnings. v2: https://lore.kernel.org/patchwork/patch/1435218/
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 | >=a29728463b254ce81ecefdf20c1a02e01d9361da <0489700bfeb1e53eb2039c2291c67e71b0b40103 || >=a29728463b254ce81ecefdf20c1a02e01d9361da <dcf6be17b5c53b741898d2223b23e66d682de300 || >=a29728463b254ce81ecefdf20c1a02e01d9361da <188fe6b26765edbad4055611c0f788b6870f4024 || >=a29728463b254ce81ecefdf20c1a02e01d9361da <b6a4055036eed1f5e239ce3d8b0db1ce38bba447 || >=a29728463b254ce81ecefdf20c1a02e01d9361da <594205b4936771a250f9d141e7e0fff21c3dd2d9 || >=a29728463b254ce81ecefdf20c1a02e01d9361da <a972c768723359ec995579902473028fe3cd64b1 || >=a29728463b254ce81ecefdf20c1a02e01d9361da <de63e74da2333b4068bb79983e632db730fea97e || >=a29728463b254ce81ecefdf20c1a02e01d9361da <226e993c39405292781bfcf4b039a8db56aab362 || >=a29728463b254ce81ecefdf20c1a02e01d9361da <aadb22ba2f656581b2f733deb3a467c48cc618f6 | 0489700bfeb1e53eb2039c2291c67e71b0b40103, dcf6be17b5c53b741898d2223b23e66d682de300, 188fe6b26765edbad4055611c0f788b6870f4024, b6a4055036eed1f5e239ce3d8b0db1ce38bba447, 594205b4936771a250f9d141e7e0fff21c3dd2d9, a972c768723359ec995579902473028fe3cd64b1, de63e74da2333b4068bb79983e632db730fea97e, 226e993c39405292781bfcf4b039a8db56aab362, aadb22ba2f656581b2f733deb3a467c48cc618f6 |
| Linux/Linuxgeneric | 4.5 | Not reported |
Published upstream
Feb 26, 2025
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: drbd: Fix five use after free bugs in get_initial_state In get_initial_state, it calls notify_initial_state_done(skb,..) if cb->args[5]==1. If genlmsg_put() failed in notify_initial_state_done(), the skb will be freed by nlmsg_free(skb). Then get_initial_state will goto out and the freed skb will be used by return value skb->len, which is a uaf bug. What's worse, the same problem goes even further: skb can also be freed in the notify_*_state_change -> notify_*_state calls below. Thus 4 additional uaf bugs happened. My patch lets the problem callee functions: notify_initial_state_done and notify_*_state_change return an error code if errors happen. So that the error codes could be propagated and the uaf bugs can be avoid. v2 reports a compilation warning. This v3 fixed this warning and built successfully in my local environment with no additional warnings. v2: https://lore.kernel.org/patchwork/patch/1435218/
Quoted source text, attributed separately from HOL analysis.