Vulnerability · Published Oct 22, 2025 · Assigned by Linux

CVE-2022-50563dm thin: Fix UAF in run_timer_softirq()

Unrated

In plain English

A security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 16% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS )–Not rated
Exploit odds (30 days)0.2%top 83.7% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: dm thin: Fix UAF in run_timer_softirq() When dm_resume() and dm_destroy() are concurrent, it will lead to UAF, as follows: BUG: KASAN: use-after-free in __run_timers+0x173/0x710 Write of size 8 at addr ffff88816d9490f0 by task swapper/0/0 <snip> Call Trace: <IRQ> dump_stack_lvl+0x73/0x9f print_report.cold+0x132/0xaa2 _raw_spin_lock_irqsave+0xcd/0x160 __run_timers+0x173/0x710 kasan_report+0xad/0x110 __run_timers+0x173/0x710 __asan_store8+0x9c/0x140 __run_timers+0x173/0x710 call_timer_fn+0x310/0x310 pvclock_clocksource_read+0xfa/0x250 kvm_clock_read+0x2c/0x70 kvm_clock_get_cycles+0xd/0x20 ktime_get+0x5c/0x110 lapic_next_event+0x38/0x50 clockevents_program_event+0xf1/0x1e0 run_timer_softirq+0x49/0x90 __do_softirq+0x16e/0x62c __irq_exit_rcu+0x1fa/0x270 irq_exit_rcu+0x12/0x20 sysvec_apic_timer_interrupt+0x8e/0xc0 One of the concurrency UAF can be shown as below: use free do_resume | __find_device_hash_cell | dm_get | atomic_inc(&md->holders) | | dm_destroy | __dm_destroy | if (!dm_suspended_md(md)) | atomic_read(&md->holders) | msleep(1) dm_resume | __dm_resume | dm_table_resume_targets | pool_resume | do_waker #add delay work | dm_put | atomic_dec(&md->holders) | | dm_table_destroy | pool_dtr | __pool_dec | __pool_destroy | destroy_workqueue | kfree(pool) # free pool time out __do_softirq run_timer_softirq # pool has already been freed This can be easily reproduced using: 1. create thin-pool 2. dmsetup suspend pool 3. dmsetup resume pool 4. dmsetup remove_all # Concurrent with 3 The root cause of this UAF bug is that dm_resume() adds timer after dm_destroy() skips cancelling the timer because of suspend status. After timeout, it will call run_timer_softirq(), however pool has already been freed. The concurrency UAF bug will happen. Therefore, cancelling timer again in __pool_destroy().

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linux6.1.4-1DEBIAN-CVE-2022-50563
Debian:13linux6.1.4-1DEBIAN-CVE-2022-50563
Debian:14linux6.1.4-1DEBIAN-CVE-2022-50563
Ubuntu:22.04:LTSlinux5.15.0-69.76UBUNTU-CVE-2022-50563
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2022-50563
Ubuntu:22.04:LTSlinux-aws5.15.0-1033.37UBUNTU-CVE-2022-50563
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2022-50563
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2022-50563
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2022-50563
Ubuntu:22.04:LTSlinux-azure5.15.0-1035.42UBUNTU-CVE-2022-50563
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2022-50563
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2022-50563
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2022-50563
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2022-50563
Ubuntu:22.04:LTSlinux-azure-fde5.15.0-1035.42.1UBUNTU-CVE-2022-50563
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2022-50563
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2022-50563
Ubuntu:22.04:LTSlinux-gcp5.15.0-1031.38UBUNTU-CVE-2022-50563
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2022-50563
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2022-50563
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2022-50563
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2022-50563
Ubuntu:22.04:LTSlinux-gke5.15.0-1030.35UBUNTU-CVE-2022-50563
Ubuntu:22.04:LTSlinux-gkeop5.15.0-1017.22UBUNTU-CVE-2022-50563
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2022-50563
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2022-50563
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2022-50563
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2022-50563
Ubuntu:22.04:LTSlinux-ibm5.15.0-1027.30UBUNTU-CVE-2022-50563
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2022-50563
Ubuntu:22.04:LTSlinux-intel-iotg5.15.0-1027.32UBUNTU-CVE-2022-50563
Ubuntu:22.04:LTSlinux-kvm5.15.0-1030.35UBUNTU-CVE-2022-50563
Ubuntu:22.04:LTSlinux-lowlatency5.15.0-69.76UBUNTU-CVE-2022-50563
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2022-50563
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2022-50563
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2022-50563
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2022-50563
Ubuntu:22.04:LTSlinux-nvidia5.15.0-1023.23UBUNTU-CVE-2022-50563
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2022-50563
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2022-50563
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2022-50563
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2022-50563
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2022-50563
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2022-50563
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2022-50563
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2022-50563
Ubuntu:22.04:LTSlinux-oracle5.15.0-1032.38UBUNTU-CVE-2022-50563
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2022-50563
Ubuntu:22.04:LTSlinux-raspi5.15.0-1026.28UBUNTU-CVE-2022-50563
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2022-50563
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2022-50563
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2022-50563
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2022-50563
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2022-50563
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2022-50563
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2022-50563
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2022-50563
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2022-50563
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2022-50563

Affected products (as reported)

VendorProductVersions
Linux Linux 991d9fa02da0dd1f843dc011376965e0c8c6c9b5 – before 7ee059d06a5d3c15465959e0472993e80fbe4e81991d9fa02da0dd1f843dc011376965e0c8c6c9b5 – before 550a4fac7ecfee5bac6a0dd772456ca62fb72f46991d9fa02da0dd1f843dc011376965e0c8c6c9b5 – before e8b8e0d2bbf7d1172c4f435621418e29ee408d46991d9fa02da0dd1f843dc011376965e0c8c6c9b5 – before 7ae6aa649394e1e7f6dafb55ce0d578c0572a280991d9fa02da0dd1f843dc011376965e0c8c6c9b5 – before 34fe9c2251f19786a6689149a6212c6c0de1d63b991d9fa02da0dd1f843dc011376965e0c8c6c9b5 – before 34cd15d83b7206188d440b29b68084fcafde9395991d9fa02da0dd1f843dc011376965e0c8c6c9b5 – before 94e231c9d6f2648d2f1f68e7f476e050ee0a6159991d9fa02da0dd1f843dc011376965e0c8c6c9b5 – before d9971fa4d8bde63d49c743c1b32d12fbbd3a30bd
Linux Linux 3.2

References