CVE-2022-49196

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2022-55030 (ENISA EUVD) · GHSA-m3r4-hpjv-ph84 (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

powerpc/pseries: Fix use after free in remove_phb_dynamic()

In remove_phb_dynamic() we use &phb->io_resource, after we've called device_unregister(&host_bridge->dev). But the unregister may have freed phb, because pcibios_free_controller_deferred() is the release function for the host_bridge.

If there are no outstanding references when we call device_unregister() then phb will be freed out from under us.

This has gone mainly unnoticed, but with slub_debug and page_poison enabled it can lead to a crash:

PID: 7574 TASK: c0000000d492cb80 CPU: 13 COMMAND: "drmgr" #0 [c0000000e4f075a0] crash_kexec at c00000000027d7dc #1 [c0000000e4f075d0] oops_end at c000000000029608 #2 [c0000000e4f07650] __bad_page_fault at c0000000000904b4 #3 [c0000000e4f076c0] do_bad_slb_fault at c00000000009a5a8 #4 [c0000000e4f076f0] data_access_slb_common_virt at c000000000008b30 Data SLB Access [380] exception frame: R0: c000000000167250 R1: c0000000e4f07a00 R2: c000000002a46100 R3: c000000002b39ce8 R4: 00000000000000c0 R5: 00000000000000a9 R6: 3894674d000000c0 R7: 0000000000000000 R8: 00000000000000ff R9: 0000000000000100 R10: 6b6b6b6b6b6b6b6b R11: 0000000000008000 R12: c00000000023da80 R13: c0000009ffd38b00 R14: 0000000000000000 R15: 000000011c87f0f0 R16: 0000000000000006 R17: 0000000000000003 R18: 0000000000000002 R19: 0000000000000004 R20: 0000000000000005 R21: 000000011c87ede8 R22: 000000011c87c5a8 R23: 000000011c87d3a0 R24: 0000000000000000 R25: 0000000000000001 R26: c0000000e4f07cc8 R27: c00000004d1cc400 R28: c0080000031d00e8 R29: c00000004d23d800 R30: c00000004d1d2400 R31: c00000004d1d2540 NIP: c000000000167258 MSR: 8000000000009033 OR3: c000000000e9f474 CTR: 0000000000000000 LR: c000000000167250 XER: 0000000020040003 CCR: 0000000024088420 MQ: 0000000000000000 DAR: 6b6b6b6b6b6b6ba3 DSISR: c0000000e4f07920 Syscall Result: fffffffffffffff2 [NIP : release_resource+56] [LR : release_resource+48] #5 [c0000000e4f07a00] release_resource at c000000000167258 (unreliable) #6 [c0000000e4f07a30] remove_phb_dynamic at c000000000105648 #7 [c0000000e4f07ab0] dlpar_remove_slot at c0080000031a09e8 [rpadlpar_io] #8 [c0000000e4f07b50] remove_slot_store at c0080000031a0b9c [rpadlpar_io] #9 [c0000000e4f07be0] kobj_attr_store at c000000000817d8c #10 [c0000000e4f07c00] sysfs_kf_write at c00000000063e504 #11 [c0000000e4f07c20] kernfs_fop_write_iter at c00000000063d868 #12 [c0000000e4f07c70] new_sync_write at c00000000054339c #13 [c0000000e4f07d10] vfs_write at c000000000546624 #14 [c0000000e4f07d60] ksys_write at c0000000005469f4 #15 [c0000000e4f07db0] system_call_exception at c000000000030840 #16 [c0000000e4f07e10] system_call_vectored_common at c00000000000c168

To avoid it, we can take a reference to the host_bridge->dev until we're done using phb. Then when we drop the reference the phb will be freed.

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
19th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

February 26, 2025

Last Modified

March 25, 2025

Advisory Details (4)

Auto-updated Sep 25, 2026
Patch available.
Web page

powerpc/pseries: Fix use after free in remove_phb_dynamic() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/fe2640bd7a62f1f7c3f55fbda31084085075bc30
Web page

powerpc/pseries: Fix use after free in remove_phb_dynamic() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/895ca4ae1f72e0a0160ab162723e59c9f265ec93
Web page

powerpc/pseries: Fix use after free in remove_phb_dynamic() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/403f9e0bc5535a0a5184d1352fa3a70e6ffacb6f
Web page

powerpc/pseries: Fix use after free in remove_phb_dynamic() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/33d39efb61a84e055ca2386157d39ebbdf6b7d31

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
linuxKernel @ 5.15.33 (fixes >=4.8.0)—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.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.17.3-1: fixed in 5.17.3-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.17.3-1: fixed in 5.17.3-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.17.3-1: fixed in 5.17.3-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 37× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 97 of 193 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 3 repeat rows among the latest 100 are merged into the row they repeat. The 96 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2022-49196?
CVE-2022-49196 is a high-severity vulnerability; its CVE record was published on February 26, 2025. In the Linux kernel, the following vulnerability has been resolved: powerpc/pseries: Fix use after free in remove_phb_dynamic() In remove_phb_dynamic() we use &phb->io_resource, after we've called device_unregister(&host_bridge->dev). But the unregister may have freed phb, because…
When was the CVE record for CVE-2022-49196 published?
The CVE record for CVE-2022-49196 was published on February 26, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of March 25, 2025; the record at its source may have been updated since.
Is CVE-2022-49196 actively exploited?
CVE-2022-49196 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (19th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-49196?
CVE-2022-49196 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2022-49196?
A fix for CVE-2022-49196 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-49196

Explore →

Is Your Infrastructure Affected by CVE-2022-49196?

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

Book a Demo →Browse All CVEs