Answer in brief
CVE-2022-49411 records a Unknown severity vulnerability in bfq: Make sure bfqg for which we are queueing requests is online. 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 | >=e21b7a0b988772e82e7147e1c659a5afe2ae003c <ccddf8cd411c1800863ed357064e56ceffd356bb || >=e21b7a0b988772e82e7147e1c659a5afe2ae003c <51f724bffa3403a5236597e6b75df7329c1ec6e9 || >=e21b7a0b988772e82e7147e1c659a5afe2ae003c <6ee0868b0c3ccead5907685fcdcdd0c08dfe4b0b || >=e21b7a0b988772e82e7147e1c659a5afe2ae003c <97bd6c56bdcb41079e488e31df56809e3b2ce628 || >=e21b7a0b988772e82e7147e1c659a5afe2ae003c <7781c38552e6cc54ed8e9040279561340516b881 || >=e21b7a0b988772e82e7147e1c659a5afe2ae003c <075a53b78b815301f8d3dd1ee2cd99554e34f0dd | ccddf8cd411c1800863ed357064e56ceffd356bb, 51f724bffa3403a5236597e6b75df7329c1ec6e9, 6ee0868b0c3ccead5907685fcdcdd0c08dfe4b0b, 97bd6c56bdcb41079e488e31df56809e3b2ce628, 7781c38552e6cc54ed8e9040279561340516b881, 075a53b78b815301f8d3dd1ee2cd99554e34f0dd |
| Linux/Linuxgeneric | 4.12 | 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: bfq: Make sure bfqg for which we are queueing requests is online Bios queued into BFQ IO scheduler can be associated with a cgroup that was already offlined. This may then cause insertion of this bfq_group into a service tree. But this bfq_group will get freed as soon as last bio associated with it is completed leading to use after free issues for service tree users. Fix the problem by making sure we always operate on online bfq_group. If the bfq_group associated with the bio is not online, we pick the first online parent.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2022-49411 records a Unknown severity vulnerability in bfq: Make sure bfqg for which we are queueing requests is online. 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 | >=e21b7a0b988772e82e7147e1c659a5afe2ae003c <ccddf8cd411c1800863ed357064e56ceffd356bb || >=e21b7a0b988772e82e7147e1c659a5afe2ae003c <51f724bffa3403a5236597e6b75df7329c1ec6e9 || >=e21b7a0b988772e82e7147e1c659a5afe2ae003c <6ee0868b0c3ccead5907685fcdcdd0c08dfe4b0b || >=e21b7a0b988772e82e7147e1c659a5afe2ae003c <97bd6c56bdcb41079e488e31df56809e3b2ce628 || >=e21b7a0b988772e82e7147e1c659a5afe2ae003c <7781c38552e6cc54ed8e9040279561340516b881 || >=e21b7a0b988772e82e7147e1c659a5afe2ae003c <075a53b78b815301f8d3dd1ee2cd99554e34f0dd | ccddf8cd411c1800863ed357064e56ceffd356bb, 51f724bffa3403a5236597e6b75df7329c1ec6e9, 6ee0868b0c3ccead5907685fcdcdd0c08dfe4b0b, 97bd6c56bdcb41079e488e31df56809e3b2ce628, 7781c38552e6cc54ed8e9040279561340516b881, 075a53b78b815301f8d3dd1ee2cd99554e34f0dd |
| Linux/Linuxgeneric | 4.12 | 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: bfq: Make sure bfqg for which we are queueing requests is online Bios queued into BFQ IO scheduler can be associated with a cgroup that was already offlined. This may then cause insertion of this bfq_group into a service tree. But this bfq_group will get freed as soon as last bio associated with it is completed leading to use after free issues for service tree users. Fix the problem by making sure we always operate on online bfq_group. If the bfq_group associated with the bio is not online, we pick the first online parent.
Quoted source text, attributed separately from HOL analysis.