[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"repo-stars":3,"vuln-DEBIAN-CVE-2022-48796":6},{"stargazers_count":4,"fetched_at":5},7,"2026-06-04T08:53:30.047Z",{"id":7,"descriptions":8,"cisa":9,"weaknesses":10,"exploits":11,"aliases":12,"duplicate_of":9,"upstream":13,"downstream":16,"duplicates":17,"related":18,"reserved_at":9,"published_at":19,"modified_at":20,"state":9,"summary":21,"references_raw":23,"kevs":30,"epss":9,"epss_history":31,"metrics":32,"affected":39},"DEBIAN-CVE-2022-48796","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.",null,[],[],[],[14],{"_key":15},"CVE-2022-48796",[],[],[],"2024-07-16T12:15:04.293Z","2026-04-28T20:24:55.460614Z",{"cisa_kev":22,"cisa_ransomware":22,"cisa_vendor":9,"epss_severity":9,"epss_score":9,"severity":9,"severity_score":9,"severity_version":9,"severity_source":9,"severity_vector":9,"severity_status":9},false,[24],{"url":25,"sources":26,"tags":28},"https://security-tracker.debian.org/tracker/CVE-2022-48796",[27],"osv_debian",[29],"Advisory",[],[],[33],{"source":27,"cvss_v2_0":9,"cvss_v3_0":9,"cvss_v3_1":34,"cvss_v4_0":9},{"baseScore":35,"baseSeverity":9,"vectorString":36,"impactScore":37,"exploitabilityScore":38},7.8,"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",9.8,4.6,[40],{"ecosystem":41,"name":42,"vendor":43,"product":42,"cpe_part":9,"purl_type":44,"purl_namespace":43,"purl_name":42,"source":9,"versions":45},"Debian","linux","debian","deb",[46,52,55,56],{"version":47,"is_range":48,"range_type":49,"version_start":9,"version_start_type":9,"version_end":50,"version_end_type":51,"fixed_in":9},"lt5_10_103_1",true,"ecosystem","5.10.103-1","excluding",{"version":53,"is_range":48,"range_type":49,"version_start":9,"version_start_type":9,"version_end":54,"version_end_type":51,"fixed_in":9},"lt5_16_10_1","5.16.10-1",{"version":53,"is_range":48,"range_type":49,"version_start":9,"version_start_type":9,"version_end":54,"version_end_type":51,"fixed_in":9},{"version":53,"is_range":48,"range_type":49,"version_start":9,"version_start_type":9,"version_end":54,"version_end_type":51,"fixed_in":9}]