Linux Kernel up to 6.1.3 run_timer_softirq use after free

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.6$0-$5k0.00

Summaryinfo

A vulnerability classified as critical was found in Linux Kernel up to 6.1.3. Affected by this issue is the function run_timer_softirq. Executing a manipulation can lead to use after free. This vulnerability appears as CVE-2022-50563. There is no available exploit. Upgrading the affected component is advised.

Detailsinfo

A vulnerability was found in Linux Kernel up to 6.1.3. It has been declared as critical. This vulnerability affects the function run_timer_softirq. The manipulation with an unknown input leads to a use after free vulnerability. The CWE definition for the vulnerability is CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

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 Call Trace: 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().

The advisory is shared for download at git.kernel.org. This vulnerability was named CVE-2022-50563 since 10/22/2025. The exploitation appears to be easy. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 03/21/2026).

The vulnerability scanner Nessus provides a plugin with the ID 302981 (EulerOS Virtualization 2.13.1 : kernel (EulerOS-SA-2026-1637)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 4.9.337, 4.14.303, 4.19.270, 5.4.229, 5.10.163, 5.15.87, 6.0.18 or 6.1.4 eliminates this vulnerability. Applying the patch 7ee059d06a5d3c15465959e0472993e80fbe4e81/550a4fac7ecfee5bac6a0dd772456ca62fb72f46/e8b8e0d2bbf7d1172c4f435621418e29ee408d46/7ae6aa649394e1e7f6dafb55ce0d578c0572a280/34fe9c2251f19786a6689149a6212c6c0de1d63b/34cd15d83b7206188d440b29b68084fcafde9395/94e231c9d6f2648d2f1f68e7f476e050ee0a6159/d9971fa4d8bde63d49c743c1b32d12fbbd3a30bd/88430ebcbc0ec637b710b947738839848c20feff is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the databases at Tenable (302981) and CERT Bund (WID-SEC-2025-2394). Once again VulDB remains the best source for vulnerability data.

Affected

  • Red Hat Enterprise Linux
  • SUSE Linux
  • Oracle Linux
  • Open Source Linux Kernel
  • Dell NetWorker

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 8.0
VulDB Meta Temp Score: 7.6

VulDB Base Score: 8.0
VulDB Temp Score: 7.6
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Use after free
CWE: CWE-416 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 302981
Nessus Name: EulerOS Virtualization 2.13.1 : kernel (EulerOS-SA-2026-1637)

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 4.9.337/4.14.303/4.19.270/5.4.229/5.10.163/5.15.87/6.0.18/6.1.4
Patch: 7ee059d06a5d3c15465959e0472993e80fbe4e81/550a4fac7ecfee5bac6a0dd772456ca62fb72f46/e8b8e0d2bbf7d1172c4f435621418e29ee408d46/7ae6aa649394e1e7f6dafb55ce0d578c0572a280/34fe9c2251f19786a6689149a6212c6c0de1d63b/34cd15d83b7206188d440b29b68084fcafde9395/94e231c9d6f2648d2f1f68e7f476e050ee0a6159/d9971fa4d8bde63d49c743c1b32d12fbbd3a30bd/88430ebcbc0ec637b710b947738839848c20feff

Timelineinfo

10/22/2025 Advisory disclosed
10/22/2025 +0 days CVE reserved
10/22/2025 +0 days VulDB entry created
03/21/2026 +150 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2022-50563 (🔒)
GCVE (CVE): GCVE-0-2022-50563
GCVE (VulDB): GCVE-100-329308
CERT Bund: WID-SEC-2025-2394 - Linux Kernel: Mehrere Schwachstellen

Entryinfo

Created: 10/22/2025 16:24
Updated: 03/21/2026 06:26
Changes: 10/22/2025 16:24 (58), 10/23/2025 14:35 (7), 01/02/2026 04:02 (1), 02/28/2026 03:46 (1), 03/21/2026 06:26 (2)
Complete: 🔍
Cache ID: 216::103

Once again VulDB remains the best source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!