CVE-2022-48796

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 2024-07-16. 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 — 4 sources updated this week

Also known asEUVD-2022-53675 (ENISA EUVD) · GHSA-49q2-34qp-qc35 (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:

iommu: Fix potential use-after-free during probe

Kasan has reported the following use after free on dev->iommu. when a device probe fails and it is in process of freeing dev->iommu in dev_iommu_free function, a deferred_probe_work_func runs in parallel and tries to access dev->iommu->fwspec in of_iommu_configure path thus causing use after free.

BUG: KASAN: use-after-free in of_iommu_configure+0xb4/0x4a4 Read of size 8 at addr ffffff87a2f1acb8 by task kworker/u16:2/153

Workqueue: events_unbound deferred_probe_work_func Call trace: dump_backtrace+0x0/0x33c show_stack+0x18/0x24 dump_stack_lvl+0x16c/0x1e0 print_address_description+0x84/0x39c __kasan_report+0x184/0x308 kasan_report+0x50/0x78 __asan_load8+0xc0/0xc4 of_iommu_configure+0xb4/0x4a4 of_dma_configure_id+0x2fc/0x4d4 platform_dma_configure+0x40/0x5c really_probe+0x1b4/0xb74 driver_probe_device+0x11c/0x228 __device_attach_driver+0x14c/0x304 bus_for_each_drv+0x124/0x1b0 __device_attach+0x25c/0x334 device_initial_probe+0x24/0x34 bus_probe_device+0x78/0x134 deferred_probe_work_func+0x130/0x1a8 process_one_work+0x4c8/0x970 worker_thread+0x5c8/0xaec kthread+0x1f8/0x220 ret_from_fork+0x10/0x18

Allocated by task 1: ____kasan_kmalloc+0xd4/0x114 __kasan_kmalloc+0x10/0x1c kmem_cache_alloc_trace+0xe4/0x3d4 __iommu_probe_device+0x90/0x394 probe_iommu_group+0x70/0x9c bus_for_each_dev+0x11c/0x19c bus_iommu_probe+0xb8/0x7d4 bus_set_iommu+0xcc/0x13c arm_smmu_bus_init+0x44/0x130 [arm_smmu] arm_smmu_device_probe+0xb88/0xc54 [arm_smmu] platform_drv_probe+0xe4/0x13c really_probe+0x2c8/0xb74 driver_probe_device+0x11c/0x228 device_driver_attach+0xf0/0x16c __driver_attach+0x80/0x320 bus_for_each_dev+0x11c/0x19c driver_attach+0x38/0x48 bus_add_driver+0x1dc/0x3a4 driver_register+0x18c/0x244 __platform_driver_register+0x88/0x9c init_module+0x64/0xff4 [arm_smmu] do_one_initcall+0x17c/0x2f0 do_init_module+0xe8/0x378 load_module+0x3f80/0x4a40 __se_sys_finit_module+0x1a0/0x1e4 __arm64_sys_finit_module+0x44/0x58 el0_svc_common+0x100/0x264 do_el0_svc+0x38/0xa4 el0_svc+0x20/0x30 el0_sync_handler+0x68/0xac el0_sync+0x160/0x180

Freed by task 1: kasan_set_track+0x4c/0x84 kasan_set_free_info+0x28/0x4c ____kasan_slab_free+0x120/0x15c __kasan_slab_free+0x18/0x28 slab_free_freelist_hook+0x204/0x2fc kfree+0xfc/0x3a4 __iommu_probe_device+0x284/0x394 probe_iommu_group+0x70/0x9c bus_for_each_dev+0x11c/0x19c bus_iommu_probe+0xb8/0x7d4 bus_set_iommu+0xcc/0x13c arm_smmu_bus_init+0x44/0x130 [arm_smmu] arm_smmu_device_probe+0xb88/0xc54 [arm_smmu] platform_drv_probe+0xe4/0x13c really_probe+0x2c8/0xb74 driver_probe_device+0x11c/0x228 device_driver_attach+0xf0/0x16c __driver_attach+0x80/0x320 bus_for_each_dev+0x11c/0x19c driver_attach+0x38/0x48 bus_add_driver+0x1dc/0x3a4 driver_register+0x18c/0x244 __platform_driver_register+0x88/0x9c init_module+0x64/0xff4 [arm_smmu] do_one_initcall+0x17c/0x2f0 do_init_module+0xe8/0x378 load_module+0x3f80/0x4a40 __se_sys_finit_module+0x1a0/0x1e4 __arm64_sys_finit_module+0x44/0x58 el0_svc_common+0x100/0x264 do_el0_svc+0x38/0xa4 el0_svc+0x20/0x30 el0_sync_handler+0x68/0xac el0_sync+0x160/0x180

Fix this by setting dev->iommu to NULL first and then freeing dev_iommu structure in dev_iommu_free function.

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 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.3%
EPSS %ILE
17th
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 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

July 16, 2024

Last Modified

August 5, 2026

Advisory Details (4)

Auto-updated Aug 4, 2026
Patch available.
Web page

iommu: Fix potential use-after-free during probe - kernel/git/stable/linux.git - Linux kernel stable tree

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

iommu: Fix potential use-after-free during probe - kernel/git/stable/linux.git - Linux kernel stable tree

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

iommu: Fix potential use-after-free during probe - kernel/git/stable/linux.git - Linux kernel stable tree

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

iommu: Fix potential use-after-free during probe - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/65ab30f6a6952fa9ee13009862736cf8d110e6e5

Vendor Advisories for CVE-2022-48796(3)

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

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatkernel-0:5.14.0-70.121.1.el9_02024-11-19redhat
redhatkernel-rt-0:5.14.0-70.121.1.rt21.193.el9_02024-11-19redhat
redhatkernel-0:4.18.0-372.121.1.el8_62024-09-04redhat
linuxKernel @ 5.10.101 (fixes >=5.3.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~bpo10+1 ... 5.10.92-2 (9 versions)
  • every version up to 5.10.103-1: fixed in 5.10.103-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.16.10-1: fixed in 5.16.10-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.16.10-1: fixed in 5.16.10-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.16.10-1: fixed in 5.16.10-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 41× 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 99 of 217 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 118 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.3% · 17th percentile
  2. 2026-11-01 16:30 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  3. 2026-10-31 16:29 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  4. 2026-10-30 16:31 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  5. 2026-10-29 16:30 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  6. 2026-10-28 16:28 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  7. 2026-10-28 15:57 UTCEG score recompute
  8. 2026-10-28 15:57 UTCVendor advisory
  9. 2026-10-28 15:57 UTCGHSA enrichmentGHSA-49q2-34qp-qc35 · GitHub severity HIGH · GitHub CVSS 7.8
  10. 2026-10-27 16:28 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  11. 2026-10-26 16:28 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  12. 2026-10-25 17:55 UTCEG score recompute
  13. 2026-10-25 16:29 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  14. 2026-10-24 16:29 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  15. 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  16. 2026-10-22 16:30 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  17. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  18. 2026-10-21 05:37 UTCEG score recompute
  19. 2026-10-21 05:37 UTCVendor advisory
  20. 2026-10-21 05:37 UTCGHSA enrichmentGHSA-49q2-34qp-qc35 · GitHub severity HIGH · GitHub CVSS 7.8
  21. 2026-10-20 16:29 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  22. 2026-10-19 16:28 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  23. 2026-10-19 12:25 UTCOSV refresh
  24. 2026-10-18 16:29 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  25. 2026-10-18 08:21 UTCEG score recompute
Show 74 more
  1. 2026-10-17 16:29 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  2. 2026-10-16 16:35 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  3. 2026-10-15 16:28 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  4. 2026-10-14 16:29 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  5. 2026-10-13 16:29 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  6. 2026-10-12 18:42 UTCEG score recompute
  7. 2026-10-12 16:30 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  8. 2026-10-11 22:06 UTCEG score recompute
  9. 2026-10-11 13:45 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  10. 2026-10-10 19:57 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  11. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  12. 2026-10-08 17:05 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  13. 2026-10-07 23:45 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  14. 2026-10-06 15:14 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  15. 2026-10-05 17:40 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  16. 2026-10-04 23:19 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  17. 2026-10-03 14:23 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  18. 2026-09-30 16:11 UTCEG score recompute
  19. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  20. 2026-09-27 13:42 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  21. 2026-09-26 19:33 UTCOSV refresh
  22. 2026-09-26 15:55 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  23. 2026-09-26 00:22 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  24. 2026-09-24 14:00 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  25. 2026-09-23 13:45 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  26. 2026-09-20 20:13 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  27. 2026-09-16 14:05 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  28. 2026-09-16 05:11 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  29. 2026-09-15 03:07 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  30. 2026-09-13 16:44 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  31. 2026-09-11 14:50 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  32. 2026-09-11 09:34 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  33. 2026-09-08 21:57 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  34. 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  35. 2026-09-07 04:48 UTCOSV refresh
  36. 2026-09-06 13:45 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  37. 2026-09-05 15:25 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  38. 2026-09-04 13:57 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  39. 2026-09-04 05:04 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  40. 2026-09-02 14:09 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  41. 2026-09-01 13:51 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  42. 2026-08-30 19:15 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  43. 2026-08-30 01:19 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  44. 2026-08-28 21:38 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  45. 2026-08-27 14:22 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  46. 2026-08-26 14:43 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  47. 2026-08-25 13:46 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  48. 2026-08-23 00:17 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  49. 2026-08-21 23:46 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  50. 2026-08-20 22:53 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  51. 2026-08-20 14:31 UTCOSV refresh
  52. 2026-08-19 17:01 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  53. 2026-08-18 13:45 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  54. 2026-08-17 13:44 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  55. 2026-08-16 14:53 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  56. 2026-08-16 02:12 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  57. 2026-08-15 01:27 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  58. 2026-08-13 21:58 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  59. 2026-08-12 13:48 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  60. 2026-08-09 13:44 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  61. 2026-08-08 16:34 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  62. 2026-08-07 16:24 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  63. 2026-08-06 13:44 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  64. 2026-08-05 19:15 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  65. 2026-08-05 09:39 UTCEG score recompute
  66. 2026-08-05 09:39 UTCVendor advisory
  67. 2026-08-05 09:38 UTCGHSA enrichmentGHSA-49q2-34qp-qc35 · GitHub severity HIGH · GitHub CVSS 7.8
  68. 2026-08-04 15:07 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  69. 2026-08-04 12:01 UTCEG score recompute
  70. 2026-08-04 12:01 UTCVendor advisory
  71. 2026-08-04 12:00 UTCGHSA enrichmentGHSA-49q2-34qp-qc35 · GitHub severity HIGH · GitHub CVSS 7.8
  72. 2026-08-04 10:35 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  73. 2026-08-04 09:49 UTCEG score recompute
  74. 2026-08-04 09:49 UTCVendor advisory

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2022-48796?
CVE-2022-48796 is a high-severity vulnerability; its CVE record was published on July 16, 2024. In the Linux kernel, the following vulnerability has been resolved: iommu: Fix potential use-after-free during probe Kasan has reported the following use after free on dev->iommu. when a device probe fails and it is in process of freeing dev->iommu in dev_iommu_free function, a…
When was the CVE record for CVE-2022-48796 published?
The CVE record for CVE-2022-48796 was published on July 16, 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 August 5, 2026; the record at its source may have been updated since.
Is CVE-2022-48796 actively exploited?
CVE-2022-48796 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (17th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-48796?
CVE-2022-48796 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2022-48796?
A fix for CVE-2022-48796 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-48796 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2022-48796?

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

Book a Demo →Browse All CVEs