Skip to content
TrackCVE
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2022-49413

bfq: Update cgroup information before merging bio

High7.8EPSS 0.29%
Published
Updated
Reserved
Assigned by
Linux

Description

In the Linux kernel, the following vulnerability has been resolved: bfq: Update cgroup information before merging bio When the process is migrated to a different cgroup (or in case of writeback just starts submitting bios associated with a different cgroup) bfq_merge_bio() can operate with stale cgroup information in bic. Thus the bio can be merged to a request from a different cgroup or it can result in merging of bfqqs for different cgroups or bfqqs of already dead cgroups and causing possible use-after-free issues. Fix the problem by updating cgroup information in bfq_merge_bio().

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-49413, 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 (7 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.

Weakness

Affected products

  • Linux · Linux

    • affected e21b7a0b988772e82e7147e1c659a5afe2ae003c – < da9f3025d595956410ceaab2bea01980d7775948
    • affected e21b7a0b988772e82e7147e1c659a5afe2ae003c – < b06691af08b41dfd81052a3362514d9827b44bb1
    • affected e21b7a0b988772e82e7147e1c659a5afe2ae003c – < e8821f45612f2e6d9adb9c6ba0fb4184f57692aa
    • affected e21b7a0b988772e82e7147e1c659a5afe2ae003c – < d9165200c5627a2cf4408eefabdf0058bdf95e1a
    • affected e21b7a0b988772e82e7147e1c659a5afe2ae003c – < 2a1077f17169a6059992a0bbdb330e0abad1e6d9
    • affected e21b7a0b988772e82e7147e1c659a5afe2ae003c – < ea591cd4eb270393810e7be01feb8fde6a34fbbe
  • 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 (6)

Sources

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

Badge for a README or a ticket

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

Record last updated .