CVE-2022-50563: dm thin: Fix UAF in run_timer_softirq()
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.24% (FIRST EPSS).
- Fixed version: Linux Linux 34cd15d83b7206188d440b29b68084fcafde9395, 34fe9c2251f19786a6689149a6212c6c0de1d63b, 550a4fac7ecfee5bac6a0dd772456ca62fb72f46.
Low priority for now. Upgrade to Linux Linux 34cd15d83b7206188d440b29b68084fcafde9395, 34fe9c2251f19786a6689149a6212c6c0de1d63b, 550a4fac7ecfee5bac6a0dd772456ca62fb72f46 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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().
- Published
- Oct 22, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 16th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 3.2affected
- 991d9fa02da0dd1f843dc011376965e0c8c6c9b5 and later · before 7ee059d06a5d3c15465959e0472993e80fbe4e81affected · git
- 991d9fa02da0dd1f843dc011376965e0c8c6c9b5 and later · before 550a4fac7ecfee5bac6a0dd772456ca62fb72f46affected · git
- 991d9fa02da0dd1f843dc011376965e0c8c6c9b5 and later · before e8b8e0d2bbf7d1172c4f435621418e29ee408d46affected · git
- 991d9fa02da0dd1f843dc011376965e0c8c6c9b5 and later · before 7ae6aa649394e1e7f6dafb55ce0d578c0572a280affected · git
- 991d9fa02da0dd1f843dc011376965e0c8c6c9b5 and later · before 34fe9c2251f19786a6689149a6212c6c0de1d63baffected · git
- 991d9fa02da0dd1f843dc011376965e0c8c6c9b5 and later · before 34cd15d83b7206188d440b29b68084fcafde9395affected · git
- 991d9fa02da0dd1f843dc011376965e0c8c6c9b5 and later · before 94e231c9d6f2648d2f1f68e7f476e050ee0a6159affected · git
- 991d9fa02da0dd1f843dc011376965e0c8c6c9b5 and later · before d9971fa4d8bde63d49c743c1b32d12fbbd3a30bdaffected · git
- 991d9fa02da0dd1f843dc011376965e0c8c6c9b5 and later · before 88430ebcbc0ec637b710b947738839848c20feffaffected · git
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.4-1 | 6.1.4-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2022-50561Oct 22, 2025 · iio: fix memory leak in iio_device_register_eventset()0Monitor
- ← EarlierCVE-2022-50562Oct 22, 2025 · tpm: acpi: Call acpi_put_table() to fix memory leak0Monitor
- Later →CVE-2022-50564Oct 22, 2025 · s390/netiucv: Fix return type of netiucv_tx()0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 34cd15d83b7206188d440b29b68084fcafde9395 | Vendor (CNA) |
| Linux Linux | 34fe9c2251f19786a6689149a6212c6c0de1d63b | Vendor (CNA) |
| Linux Linux | 550a4fac7ecfee5bac6a0dd772456ca62fb72f46 | Vendor (CNA) |
| Linux Linux | 7ae6aa649394e1e7f6dafb55ce0d578c0572a280 | Vendor (CNA) |
| Linux Linux | 7ee059d06a5d3c15465959e0472993e80fbe4e81 | Vendor (CNA) |
| Linux Linux | 88430ebcbc0ec637b710b947738839848c20feff | Vendor (CNA) |
| Linux Linux | 94e231c9d6f2648d2f1f68e7f476e050ee0a6159 | Vendor (CNA) |
| Linux Linux | d9971fa4d8bde63d49c743c1b32d12fbbd3a30bd | Vendor (CNA) |
| Linux Linux | e8b8e0d2bbf7d1172c4f435621418e29ee408d46 | Vendor (CNA) |
| debian:linux | 6.1.4-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (8 more)Show less
- git.kernel.org/stable/c/34fe9c2251f19786a6689149a6212c6c0de1d63b
- git.kernel.org/stable/c/550a4fac7ecfee5bac6a0dd772456ca62fb72f46
- git.kernel.org/stable/c/7ae6aa649394e1e7f6dafb55ce0d578c0572a280
- git.kernel.org/stable/c/7ee059d06a5d3c15465959e0472993e80fbe4e81
- git.kernel.org/stable/c/88430ebcbc0ec637b710b947738839848c20feff
- git.kernel.org/stable/c/94e231c9d6f2648d2f1f68e7f476e050ee0a6159
- git.kernel.org/stable/c/d9971fa4d8bde63d49c743c1b32d12fbbd3a30bd
- git.kernel.org/stable/c/e8b8e0d2bbf7d1172c4f435621418e29ee408d46
Vendor advisories and official records. Exploit/PoC links are deliberately left out.