Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2022-49411bfq: Make sure bfqg for which we are queueing requests is online

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 18 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2022-49411, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CISA-ADPADP (enrichment)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Analyzed3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.29% · top 78% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected e21b7a0b988772e82e7147e1c659a5afe2ae003c – < ccddf8cd411c1800863ed357064e56ceffd356bb
    • affected e21b7a0b988772e82e7147e1c659a5afe2ae003c – < 51f724bffa3403a5236597e6b75df7329c1ec6e9
    • affected e21b7a0b988772e82e7147e1c659a5afe2ae003c – < 6ee0868b0c3ccead5907685fcdcdd0c08dfe4b0b
    • affected e21b7a0b988772e82e7147e1c659a5afe2ae003c – < 97bd6c56bdcb41079e488e31df56809e3b2ce628
    • affected e21b7a0b988772e82e7147e1c659a5afe2ae003c – < 7781c38552e6cc54ed8e9040279561340516b881
    • affected e21b7a0b988772e82e7147e1c659a5afe2ae003c – < 075a53b78b815301f8d3dd1ee2cd99554e34f0dd
  • Linux · Linux

    • affected 4.12
    • unaffected < 4.12
    • unaffected 5.4.198 – ≤ 5.4.*
    • unaffected 5.10.121 – ≤ 5.10.*
    • unaffected 5.15.46 – ≤ 5.15.*
    • unaffected 5.17.14 – ≤ 5.17.*
    • unaffected 5.18.3 – ≤ 5.18.*
    • unaffected 5.19 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2022-49411 badge
[![CVE-2022-49411](https://cveledger.app/badge/CVE-2022-49411.svg)](https://cveledger.app/cve/CVE-2022-49411)

Record last updated .