CVE-2022-48895

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

Score 5.5 from GitHub Security Advisory published 2024-08-21. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2022-53774 (ENISA EUVD) · GHSA-j5pj-mr9v-2742 (GitHub Security Advisories)Source: ENISA EUVD

5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

iommu/arm-smmu: Don't unregister on shutdown

Michael Walle says he noticed the following stack trace while performing a shutdown with "reboot -f". He suggests he got "lucky" and just hit the correct spot for the reboot while there was a packet transmission in flight.

Unable to handle kernel NULL pointer dereference at virtual address 0000000000000098 CPU: 0 PID: 23 Comm: kworker/0:1 Not tainted 6.1.0-rc5-00088-gf3600ff8e322 #1930 Hardware name: Kontron KBox A-230-LS (DT) pc : iommu_get_dma_domain+0x14/0x20 lr : iommu_dma_map_page+0x9c/0x254 Call trace: iommu_get_dma_domain+0x14/0x20 dma_map_page_attrs+0x1ec/0x250 enetc_start_xmit+0x14c/0x10b0 enetc_xmit+0x60/0xdc dev_hard_start_xmit+0xb8/0x210 sch_direct_xmit+0x11c/0x420 __dev_queue_xmit+0x354/0xb20 ip6_finish_output2+0x280/0x5b0 __ip6_finish_output+0x15c/0x270 ip6_output+0x78/0x15c NF_HOOK.constprop.0+0x50/0xd0 mld_sendpack+0x1bc/0x320 mld_ifc_work+0x1d8/0x4dc process_one_work+0x1e8/0x460 worker_thread+0x178/0x534 kthread+0xe0/0xe4 ret_from_fork+0x10/0x20 Code: d503201f f9416800 d503233f d50323bf (f9404c00) ---[ end trace 0000000000000000 ]--- Kernel panic - not syncing: Oops: Fatal exception in interrupt

This appears to be reproducible when the board has a fixed IP address, is ping flooded from another host, and "reboot -f" is used.

The following is one more manifestation of the issue:

$ reboot -f kvm: exiting hardware virtualization cfg80211: failed to load regulatory.db arm-smmu 5000000.iommu: disabling translation sdhci-esdhc 2140000.mmc: Removing from iommu group 11 sdhci-esdhc 2150000.mmc: Removing from iommu group 12 fsl-edma 22c0000.dma-controller: Removing from iommu group 17 dwc3 3100000.usb: Removing from iommu group 9 dwc3 3110000.usb: Removing from iommu group 10 ahci-qoriq 3200000.sata: Removing from iommu group 2 fsl-qdma 8380000.dma-controller: Removing from iommu group 20 platform f080000.display: Removing from iommu group 0 etnaviv-gpu f0c0000.gpu: Removing from iommu group 1 etnaviv etnaviv: Removing from iommu group 1 caam_jr 8010000.jr: Removing from iommu group 13 caam_jr 8020000.jr: Removing from iommu group 14 caam_jr 8030000.jr: Removing from iommu group 15 caam_jr 8040000.jr: Removing from iommu group 16 fsl_enetc 0000:00:00.0: Removing from iommu group 4 arm-smmu 5000000.iommu: Blocked unknown Stream ID 0x429; boot with "arm-smmu.disable_bypass=0" to allow, but this may have security implications arm-smmu 5000000.iommu: GFSR 0x80000002, GFSYNR0 0x00000002, GFSYNR1 0x00000429, GFSYNR2 0x00000000 fsl_enetc 0000:00:00.1: Removing from iommu group 5 arm-smmu 5000000.iommu: Blocked unknown Stream ID 0x429; boot with "arm-smmu.disable_bypass=0" to allow, but this may have security implications arm-smmu 5000000.iommu: GFSR 0x80000002, GFSYNR0 0x00000002, GFSYNR1 0x00000429, GFSYNR2 0x00000000 arm-smmu 5000000.iommu: Blocked unknown Stream ID 0x429; boot with "arm-smmu.disable_bypass=0" to allow, but this may have security implications arm-smmu 5000000.iommu: GFSR 0x80000002, GFSYNR0 0x00000000, GFSYNR1 0x00000429, GFSYNR2 0x00000000 fsl_enetc 0000:00:00.2: Removing from iommu group 6 fsl_enetc_mdio 0000:00:00.3: Removing from iommu group 8 mscc_felix 0000:00:00.5: Removing from iommu group 3 fsl_enetc 0000:00:00.6: Removing from iommu group 7 pcieport 0001:00:00.0: Removing from iommu group 18 arm-smmu 5000000.iommu: Blocked unknown Stream ID 0x429; boot with "arm-smmu.disable_bypass=0" to allow, but this may have security implications arm-smmu 5000000.iommu: GFSR 0x00000002, GFSYNR0 0x00000000, GFSYNR1 0x00000429, GFSYNR2 0x00000000 pcieport 0002:00:00.0: Removing from iommu group 19 Unable to handle kernel NULL pointer dereference at virtual address 00000000000000a8 pc : iommu_get_dma_domain+0x14/0x20 lr : iommu_dma_unmap_page+0x38/0xe0 Call trace: iommu_get_dma_domain+0x14/0x20 dma_unmap_page_attrs+0x38/0x1d0 en ---truncated---

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/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)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 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 every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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.2%
EPSS %ILE
10th
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 (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-25). 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 every mission impact level.CISA BOD 26-04: 60 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 every mission impact level.

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 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 partial (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

August 21, 2024

Last Modified

September 11, 2024

References (2)

Patch Availability(1)

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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.7-1: fixed in 6.1.7-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.7-1: fixed in 6.1.7-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.7-1: fixed in 6.1.7-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 36× 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 96 of 188 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. 4 repeat rows among the latest 100 are merged into the row they repeat. The 92 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2022-48895?
CVE-2022-48895 is a medium-severity vulnerability; its CVE record was published on August 21, 2024. In the Linux kernel, the following vulnerability has been resolved: iommu/arm-smmu: Don't unregister on shutdown Michael Walle says he noticed the following stack trace while performing a shutdown with "reboot -f". He suggests he got "lucky" and just hit the correct spot for the reboot while there…
When was the CVE record for CVE-2022-48895 published?
The CVE record for CVE-2022-48895 was published on August 21, 2024. 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 September 11, 2024; the record at its source may have been updated since.
Is CVE-2022-48895 actively exploited?
CVE-2022-48895 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (10th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-48895?
CVE-2022-48895 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2022-48895?
A fix for CVE-2022-48895 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-48895

Explore →

Is Your Infrastructure Affected by CVE-2022-48895?

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

Book a Demo →Browse All CVEs