🛡️ CVE-2022-50534 on Ubuntu — linux
Description
In the Linux kernel, the following vulnerability has been resolved: dm thin: Use last transaction's pmd->root when commit failed Recently we found a softlock up problem in dm thin pool btree lookup code due to corrupted metadata: Kernel panic - not syncing: softlockup: hung tasks CPU: 7 PID: 2669225 Comm: kworker/u16:3 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996) Workqueue: dm-thin do_worker [dm_thin_pool] Call Trace: <IRQ> dump_stack+0x9c/0xd3 panic+0x35d/0x6b9 watchdog_timer_fn.cold+0x16/0x25 __run_hrtimer+0xa2/0x2d0 </IRQ> RIP: 0010:__relink_lru+0x102/0x220 [dm_bufio] __bufio_new+0x11f/0x4f0 [dm_bufio] new_read+0xa3/0x1e0 [dm_bufio] dm_bm_read_lock+0x33/0xd0 [dm_persistent_data] ro_step+0x63/0x100 [dm_persistent_data] btree_lookup_raw.constprop.0+0x44/0x220 [dm_persistent_data] dm_btree_lookup+0x16f/0x210 [dm_persistent_data] dm_thin_find_block+0x12c/0x210 [dm_thin_pool] __process_bio_read_only+0xc5/0x400 [dm_thin_pool] process_thin_deferred_bios+0x1a4/0x4a0 [dm_thin_pool] process_one_work+0x3c5/0x730 Following process may generate a broken btree mixed with fresh and stale btree nodes, which could get dm thin trapped in an infinite loop while looking up data block: Transaction 1: pmd->root = A, A->B->C // One path in btree pmd->root = X, X->Y->Z // Copy-up Transaction 2: X,Z is updated on disk, Y write failed. // Commit failed, dm thin becomes read-only. process_bio_read_only dm_thin_find_block __find_block dm_btree_lookup(pmd->root) The pmd->root points to a broken btree, Y may contain stale node pointing to any block, for example X, which gets dm thin trapped into a dead loop while looking up Z. Fix this by setting pmd->root in __open_metadata(), so that dm thin will use the last transaction's pmd->root if commit failed. Fetch a reproducer in [Link]. Linke: https://bugzilla.kernel.org/show_bug.cgi?id=216790
Distribution advisory
This page covers CVE-2022-50534 as tracked by Ubuntu, for the package linux. The fix is available in version 5.15.0-69.76; earlier versions remain affected.
How this vulnerability can be exploited
This issue can be reached with local access to the system, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity none, availability high.
CVSS metrics in full
The score comes from this vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- Attack vector: Local — a local account, shell or session on the host is needed.
- Attack complexity: Low — the attack works reliably, with no preparation.
- Privileges required: Low — an ordinary user account is enough.
- User interaction: None — nobody has to be tricked into anything.
- Scope: Unchanged — the damage stays inside the vulnerable component.
- Confidentiality impact: None.
- Integrity impact: None.
- Availability impact: High — total loss, or loss the attacker controls.
Affected software
UBUNTU-CVE-2022-50534 is recorded against 120 packages.
- linux (fixed in 5.15.0-69.76)
- linux-allwinner-5.19
- linux-aws (fixed in 5.15.0-1033.37)
- linux-aws-5.0
- linux-aws-5.11
- linux-aws-5.13
- linux-aws-5.15 (fixed in 5.15.0-1033.37~20.04.1)
- linux-aws-5.19
- linux-aws-5.3
- linux-aws-5.4 (fixed in 5.4.0-1097.105~18.04.1)
- linux-aws-5.8
- linux-aws-6.2
- linux-aws-6.5
- linux-aws-fips
- linux-aws-hwe (fixed in 4.15.0-1153.166~16.04.1)
- linux-azure (fixed in 5.15.0-1035.42)
- linux-azure-4.15 (fixed in 4.15.0-1162.177)
- linux-azure-5.11
- linux-azure-5.13
- linux-azure-5.15 (fixed in 5.15.0-1035.42~20.04.1)
- linux-azure-5.19
- linux-azure-5.3
- linux-azure-5.4 (fixed in 5.4.0-1104.110~18.04.1)
- linux-azure-5.8
Show the remaining 96 packages
- linux-azure-6.11
- linux-azure-6.2
- linux-azure-6.5
- linux-azure-edge
- linux-azure-fde
- linux-azure-fde-5.19
- linux-azure-fde-6.2
- linux-azure-fips
- linux-bluefield
- linux-fips
- linux-gcp (fixed in 5.15.0-1031.38)
- linux-gcp-4.15 (fixed in 4.15.0-1147.163)
- linux-gcp-5.11
- linux-gcp-5.13
- linux-gcp-5.15 (fixed in 5.15.0-1031.38~20.04.1)
- linux-gcp-5.19
- linux-gcp-5.3
- linux-gcp-5.4 (fixed in 5.4.0-1101.110~18.04.1)
- linux-gcp-5.8
- linux-gcp-6.11
- linux-gcp-6.2
- linux-gcp-6.5
- linux-gcp-fips
- linux-gke (fixed in 5.15.0-1030.35)
- linux-gke-4.15
- linux-gke-5.15
- linux-gke-5.4
- linux-gkeop (fixed in 5.15.0-1017.22)
- linux-gkeop-5.15
- linux-gkeop-5.4
- linux-hwe
- linux-hwe-5.11
- linux-hwe-5.13
- linux-hwe-5.15 (fixed in 5.15.0-69.76~20.04.1)
- linux-hwe-5.19
- linux-hwe-5.4 (fixed in 5.4.0-144.161~18.04.1)
- linux-hwe-5.8
- linux-hwe-6.11
- linux-hwe-6.2
- linux-hwe-6.5
- linux-hwe-edge
- linux-ibm (fixed in 5.15.0-1027.30)
- linux-ibm-5.4 (fixed in 5.4.0-1045.50~18.04.1)
- linux-intel
- linux-intel-5.13
- linux-intel-iot-realtime (fixed in 5.15.0-1023.28)
- linux-intel-iotg (fixed in 5.15.0-1027.32)
- linux-intel-iotg-5.15 (fixed in 5.15.0-1027.32~20.04.1)
- linux-iot (fixed in 5.4.0-1013.15)
- linux-kvm (fixed in 5.15.0-1030.35)
- linux-lowlatency (fixed in 5.15.0-69.76)
- linux-lowlatency-hwe-5.15 (fixed in 5.15.0-69.76~20.04.1)
- linux-lowlatency-hwe-5.19
- linux-lowlatency-hwe-6.11
- linux-lowlatency-hwe-6.2
- linux-lowlatency-hwe-6.5
- linux-lts-xenial
- linux-nvidia (fixed in 5.15.0-1023.23)
- linux-nvidia-6.2
- linux-nvidia-6.5
- linux-nvidia-tegra-5.15 (fixed in 5.15.0-1014.14~20.04.1)
- linux-oem
- linux-oem-5.10
- linux-oem-5.13
- linux-oem-5.14
- linux-oem-5.17
- linux-oem-5.6
- linux-oem-6.0
- linux-oem-6.1
- linux-oem-6.11
- linux-oem-6.5
- linux-oem-6.8
- linux-oracle (fixed in 5.15.0-1032.38)
- linux-oracle-5.0
- linux-oracle-5.11
- linux-oracle-5.13
- linux-oracle-5.15 (fixed in 5.15.0-1032.38~20.04.1)
- linux-oracle-5.3
- linux-oracle-5.4 (fixed in 5.4.0-1094.103~18.04.1)
- linux-oracle-5.8
- linux-oracle-6.5
- linux-raspi (fixed in 5.15.0-1026.28)
- linux-raspi-5.4 (fixed in 5.4.0-1081.92~18.04.1)
- linux-raspi-realtime
- linux-raspi2
- linux-realtime
- linux-riscv
- linux-riscv-5.11
- linux-riscv-5.15 (fixed in 5.15.0-1030.34~20.04.1)
- linux-riscv-5.19
- linux-riscv-5.8
- linux-riscv-6.5
- linux-starfive-5.19
- linux-starfive-6.2
- linux-starfive-6.5
- linux-xilinx-zynqmp (fixed in 5.4.0-1022.26)
Timeline and source
Published on 7 October 2025 and last revised on 19 August 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.
References
ubuntu.com (Report)
www.cve.org (Report)
git.kernel.org (Report)
git.kernel.org (Report)
git.kernel.org (Report)
git.kernel.org (Report)
git.kernel.org (Report)
git.kernel.org (Report)
git.kernel.org (Report)
git.kernel.org (Report)
git.kernel.org (Report)
git.kernel.org (Report)
Other advisories for this package
linux has other advisories on record. If you are patching this one, these are worth checking on the same host:
- DEBIAN-CVE-2022-4994 (published 30 Jul 2026)
- CVE-2026-35233 (4.4 Medium, published 1 May 2026)
- CVE-2026-21996 (3.3 Low, published 1 May 2026)
- CVE-2026-21991 (5.5 Medium, published 16 Mar 2026)
- CGA-w6xv-3fg4-grm5 (published 29 Jan 2026)
- CGA-mcwh-q4vm-9f29 (published 29 Jan 2026)
- CGA-wf5v-37v7-wvrh (published 7 Jan 2026)
- CGA-58q9-gmq4-72q9 (published 7 Jan 2026)
CVE-2022-50534 on other distributions
Each distribution ships its own build and its own fixed version. Pick the one you run:
Details
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| linux | — | 5.15.0-69.76 |
| linux-allwinner-5.19 | — | — |
| linux-aws | — | 5.15.0-1033.37 |
| linux-aws-5.0 | — | — |
| linux-aws-5.11 | — | — |
| linux-aws-5.13 | — | — |
| linux-aws-5.15 | — | 5.15.0-1033.37~20.04.1 |
| linux-aws-5.19 | — | — |
| linux-aws-5.3 | — | — |
| linux-aws-5.4 | — | 5.4.0-1097.105~18.04.1 |
| linux-aws-5.8 | — | — |
| linux-aws-6.2 | — | — |
| linux-aws-6.5 | — | — |
| linux-aws-fips | — | — |
| linux-aws-hwe | — | 4.15.0-1153.166~16.04.1 |
| linux-azure | — | 5.15.0-1035.42 |
| linux-azure-4.15 | — | 4.15.0-1162.177 |
| linux-azure-5.11 | — | — |
| linux-azure-5.13 | — | — |
| linux-azure-5.15 | — | 5.15.0-1035.42~20.04.1 |
| linux-azure-5.19 | — | — |
| linux-azure-5.3 | — | — |
| linux-azure-5.4 | — | 5.4.0-1104.110~18.04.1 |
| linux-azure-5.8 | — | — |
| linux-azure-6.11 | — | — |
| linux-azure-6.2 | — | — |
| linux-azure-6.5 | — | — |
| linux-azure-edge | — | — |
| linux-azure-fde | — | — |
| linux-azure-fde-5.19 | — | — |
| linux-azure-fde-6.2 | — | — |
| linux-azure-fips | — | — |
| linux-bluefield | — | — |
| linux-fips | — | — |
| linux-gcp | — | 5.15.0-1031.38 |
| linux-gcp-4.15 | — | 4.15.0-1147.163 |
| linux-gcp-5.11 | — | — |
| linux-gcp-5.13 | — | — |
| linux-gcp-5.15 | — | 5.15.0-1031.38~20.04.1 |
| linux-gcp-5.19 | — | — |
| linux-gcp-5.3 | — | — |
| linux-gcp-5.4 | — | 5.4.0-1101.110~18.04.1 |
| linux-gcp-5.8 | — | — |
| linux-gcp-6.11 | — | — |
| linux-gcp-6.2 | — | — |
| linux-gcp-6.5 | — | — |
| linux-gcp-fips | — | — |
| linux-gke | — | 5.15.0-1030.35 |
| linux-gke-4.15 | — | — |
| linux-gke-5.15 | — | — |
| linux-gke-5.4 | — | — |
| linux-gkeop | — | 5.15.0-1017.22 |
| linux-gkeop-5.15 | — | — |
| linux-gkeop-5.4 | — | — |
| linux-hwe | — | — |
| linux-hwe-5.11 | — | — |
| linux-hwe-5.13 | — | — |
| linux-hwe-5.15 | — | 5.15.0-69.76~20.04.1 |
| linux-hwe-5.19 | — | — |
| linux-hwe-5.4 | — | 5.4.0-144.161~18.04.1 |
| linux-hwe-5.8 | — | — |
| linux-hwe-6.11 | — | — |
| linux-hwe-6.2 | — | — |
| linux-hwe-6.5 | — | — |
| linux-hwe-edge | — | — |
| linux-ibm | — | 5.15.0-1027.30 |
| linux-ibm-5.4 | — | 5.4.0-1045.50~18.04.1 |
| linux-intel | — | — |
| linux-intel-5.13 | — | — |
| linux-intel-iot-realtime | — | 5.15.0-1023.28 |
| linux-intel-iotg | — | 5.15.0-1027.32 |
| linux-intel-iotg-5.15 | — | 5.15.0-1027.32~20.04.1 |
| linux-iot | — | 5.4.0-1013.15 |
| linux-kvm | — | 5.15.0-1030.35 |
| linux-lowlatency | — | 5.15.0-69.76 |
| linux-lowlatency-hwe-5.15 | — | 5.15.0-69.76~20.04.1 |
| linux-lowlatency-hwe-5.19 | — | — |
| linux-lowlatency-hwe-6.11 | — | — |
| linux-lowlatency-hwe-6.2 | — | — |
| linux-lowlatency-hwe-6.5 | — | — |
| linux-lts-xenial | — | — |
| linux-nvidia | — | 5.15.0-1023.23 |
| linux-nvidia-6.2 | — | — |
| linux-nvidia-6.5 | — | — |
| linux-nvidia-tegra-5.15 | — | 5.15.0-1014.14~20.04.1 |
| linux-oem | — | — |
| linux-oem-5.10 | — | — |
| linux-oem-5.13 | — | — |
| linux-oem-5.14 | — | — |
| linux-oem-5.17 | — | — |
| linux-oem-5.6 | — | — |
| linux-oem-6.0 | — | — |
| linux-oem-6.1 | — | — |
| linux-oem-6.11 | — | — |
| linux-oem-6.5 | — | — |
| linux-oem-6.8 | — | — |
| linux-oracle | — | 5.15.0-1032.38 |
| linux-oracle-5.0 | — | — |
| linux-oracle-5.11 | — | — |
| linux-oracle-5.13 | — | — |
| linux-oracle-5.15 | — | 5.15.0-1032.38~20.04.1 |
| linux-oracle-5.3 | — | — |
| linux-oracle-5.4 | — | 5.4.0-1094.103~18.04.1 |
| linux-oracle-5.8 | — | — |
| linux-oracle-6.5 | — | — |
| linux-raspi | — | 5.15.0-1026.28 |
| linux-raspi-5.4 | — | 5.4.0-1081.92~18.04.1 |
| linux-raspi-realtime | — | — |
| linux-raspi2 | — | — |
| linux-realtime | — | — |
| linux-riscv | — | — |
| linux-riscv-5.11 | — | — |
| linux-riscv-5.15 | — | 5.15.0-1030.34~20.04.1 |
| linux-riscv-5.19 | — | — |
| linux-riscv-5.8 | — | — |
| linux-riscv-6.5 | — | — |
| linux-starfive-5.19 | — | — |
| linux-starfive-6.2 | — | — |
| linux-starfive-6.5 | — | — |
| linux-xilinx-zynqmp | — | 5.4.0-1022.26 |
References
Similar Threats
- Unknown CGA-23jx-hhcx-m389
- Unknown CGA-2qp7-6757-fmgc
- Unknown CGA-2rj5-jc55-r267
- Unknown CGA-3m96-cwq8-6xmx
- Unknown CGA-3qj9-973w-fh9g
Vulnerability Monitoring
Track new vulnerabilities in linux
UBUNTU-CVE-2022-50534 is rated CVSS 5.5 Medium. BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.
Set Up Free Alerts →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.
