CVE-2022-49413

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-02-27. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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().

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
35(Track)
EG Risk 35/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
21%
KEV
Not listed

Published

February 26, 2025

Last Modified

August 5, 2026

Advisory Details (6)

Auto-updated Aug 5, 2026
No patch confirmed yet.
generic

bfq: Update cgroup information before merging bio - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ea591cd4eb270393810e7be01feb8fde6a34fbbe
generic

bfq: Update cgroup information before merging bio - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2a1077f17169a6059992a0bbdb330e0abad1e6d9
generic

bfq: Update cgroup information before merging bio - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d9165200c5627a2cf4408eefabdf0058bdf95e1a
generic

bfq: Update cgroup information before merging bio - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e8821f45612f2e6d9adb9c6ba0fb4184f57692aa
generic

bfq: Update cgroup information before merging bio - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b06691af08b41dfd81052a3362514d9827b44bb1
generic

bfq: Update cgroup information before merging bio - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/da9f3025d595956410ceaab2bea01980d7775948

Vendor Advisories for CVE-2022-49413(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:5.14.0-162.6.1.el9_12022-11-15redhat
linuxKernel @ 5.4.198—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 50× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 119 total refreshes for this CVE.

  1. 2026-08-07 16:24 UTCEPSS rescore
  2. 2026-08-06 13:44 UTCEPSS rescore
  3. 2026-08-05 19:15 UTCEPSS rescore
  4. 2026-08-05 09:31 UTCEG score recompute
  5. 2026-08-05 09:31 UTCVendor advisory
  6. 2026-08-05 09:31 UTCGHSA enrichment
  7. 2026-08-04 15:07 UTCEPSS rescore
  8. 2026-08-04 10:35 UTCEPSS rescore
  9. 2026-08-04 09:46 UTCEG score recompute
  10. 2026-08-04 09:46 UTCVendor advisory
  11. 2026-08-04 09:46 UTCGHSA enrichment
  12. 2026-08-02 02:24 UTCEPSS rescore
  13. 2026-08-01 04:13 UTCEPSS rescore
  14. 2026-08-01 04:13 UTCEPSS rescore
  15. 2026-07-30 16:25 UTCEPSS rescore
  16. 2026-07-30 01:28 UTCEPSS rescore
  17. 2026-07-28 15:34 UTCEPSS rescore
  18. 2026-07-26 14:52 UTCEPSS rescore
  19. 2026-07-26 14:52 UTCEPSS rescore
  20. 2026-07-25 14:16 UTCEPSS rescore
  21. 2026-07-24 14:15 UTCEPSS rescore
  22. 2026-07-24 14:11 UTCOSV refresh
  23. 2026-07-23 14:16 UTCEPSS rescore
  24. 2026-07-23 14:16 UTCEPSS rescore
  25. 2026-07-23 02:16 UTCEG score recompute
Show 75 more
  1. 2026-07-22 23:04 UTCEG score recompute
  2. 2026-07-22 14:06 UTCEPSS rescore
  3. 2026-07-22 14:06 UTCEPSS rescore
  4. 2026-07-21 15:23 UTCEPSS rescore
  5. 2026-07-21 15:23 UTCEPSS rescore
  6. 2026-07-20 17:05 UTCEPSS rescore
  7. 2026-07-19 14:29 UTCEPSS rescore
  8. 2026-07-19 14:29 UTCEPSS rescore
  9. 2026-07-19 02:27 UTCEPSS rescore
  10. 2026-07-19 02:27 UTCEPSS rescore
  11. 2026-07-18 10:03 UTCEPSS rescore
  12. 2026-07-18 10:03 UTCEPSS rescore
  13. 2026-07-16 17:00 UTCEPSS rescore
  14. 2026-07-15 16:56 UTCEPSS rescore
  15. 2026-07-15 16:56 UTCEPSS rescore
  16. 2026-07-15 01:58 UTCEPSS rescore
  17. 2026-07-15 01:58 UTCEPSS rescore
  18. 2026-07-13 22:28 UTCEPSS rescore
  19. 2026-07-13 22:28 UTCEPSS rescore
  20. 2026-07-13 06:11 UTCEPSS rescore
  21. 2026-07-13 06:11 UTCEPSS rescore
  22. 2026-07-12 05:44 UTCEPSS rescore
  23. 2026-07-11 08:25 UTCEPSS rescore
  24. 2026-07-11 08:25 UTCEPSS rescore
  25. 2026-07-09 19:08 UTCEPSS rescore
  26. 2026-07-08 15:13 UTCEPSS rescore
  27. 2026-07-07 13:44 UTCEPSS rescore
  28. 2026-07-07 09:51 UTCOSV refresh
  29. 2026-07-06 16:25 UTCEPSS rescore
  30. 2026-07-06 02:21 UTCEPSS rescore
  31. 2026-07-05 02:28 UTCEPSS rescore
  32. 2026-07-04 06:29 UTCEPSS rescore
  33. 2026-07-01 15:04 UTCEPSS rescore
  34. 2026-06-30 23:21 UTCEPSS rescore
  35. 2026-06-30 23:20 UTCEPSS rescore
  36. 2026-06-29 14:04 UTCEPSS rescore
  37. 2026-06-28 14:06 UTCEPSS rescore
  38. 2026-06-28 04:54 UTCEPSS rescore
  39. 2026-06-28 04:54 UTCEPSS rescore
  40. 2026-06-27 03:07 UTCEPSS rescore
  41. 2026-06-27 03:07 UTCEPSS rescore
  42. 2026-06-25 13:48 UTCEPSS rescore
  43. 2026-06-25 13:48 UTCEPSS rescore
  44. 2026-06-24 14:03 UTCEPSS rescore
  45. 2026-06-24 14:03 UTCEPSS rescore
  46. 2026-06-23 21:31 UTCEPSS rescore
  47. 2026-06-23 21:31 UTCEPSS rescore
  48. 2026-06-22 14:24 UTCEPSS rescore
  49. 2026-06-21 14:55 UTCEPSS rescore
  50. 2026-06-21 14:55 UTCEPSS rescore
  51. 2026-06-21 01:58 UTCEPSS rescore
  52. 2026-06-21 01:58 UTCEPSS rescore
  53. 2026-06-19 19:24 UTCEPSS rescore
  54. 2026-06-19 19:24 UTCEPSS rescore
  55. 2026-06-18 20:44 UTCOSV refresh
  56. 2026-06-18 17:51 UTCEPSS rescore
  57. 2026-06-18 17:51 UTCEPSS rescore
  58. 2026-06-17 17:51 UTCEPSS rescore
  59. 2026-06-17 17:51 UTCEPSS rescore
  60. 2026-06-16 17:51 UTCEPSS rescore
  61. 2026-06-16 17:51 UTCEPSS rescore
  62. 2026-06-15 17:47 UTCEPSS rescore
  63. 2026-06-14 23:16 UTCEPSS rescore
  64. 2026-06-13 22:59 UTCEPSS rescore
  65. 2026-06-12 23:10 UTCEPSS rescore
  66. 2026-06-12 23:10 UTCEPSS rescore
  67. 2026-06-11 13:58 UTCEPSS rescore
  68. 2026-06-11 13:58 UTCEPSS rescore
  69. 2026-06-10 13:21 UTCEPSS rescore
  70. 2026-06-10 13:21 UTCEPSS rescore
  71. 2026-06-08 14:15 UTCEPSS rescore
  72. 2026-06-08 14:15 UTCEPSS rescore
  73. 2026-06-07 15:23 UTCEPSS rescore
  74. 2026-06-07 15:23 UTCEPSS rescore
  75. 2026-06-06 13:46 UTCEPSS rescore

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2022-49413?
CVE-2022-49413 is a high vulnerability published on February 26, 2025. 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) bfqmergebio() can operate with stale…
When was CVE-2022-49413 disclosed?
CVE-2022-49413 was first published in the National Vulnerability Database on February 26, 2025, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-49413 actively exploited?
CVE-2022-49413 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 78.9% of all scored CVEs.
What is the CVSS score of CVE-2022-49413?
CVE-2022-49413 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2022-49413?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-49413, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2022-49413

Explore →

Is Your Infrastructure Affected by CVE-2022-49413?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs