Linux Kernel up to 6.1.3 __open_metadata infinite loop

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.
5.0$0-$5k0.00

Summaryinfo

A vulnerability identified as critical has been detected in Linux Kernel up to 6.1.3. This impacts the function __open_metadata. The manipulation leads to infinite loop. This vulnerability is listed as CVE-2022-50534. There is no available exploit. You should upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as critical, has been found in Linux Kernel up to 6.1.3. This issue affects the function __open_metadata. The manipulation with an unknown input leads to a infinite loop vulnerability. Using CWE to declare the problem leads to CWE-835. The product contains an iteration or loop with an exit condition that cannot be reached, i.e., an infinite loop. Impacted is availability. The summary by CVE is:

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

The advisory is shared at git.kernel.org. The identification of this vulnerability is CVE-2022-50534 since 10/07/2025. The exploitation is known to be difficult. Technical details are known, but no exploit is available.

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 b35a22760aa5008d82533e59b0f0b5eb1b02d4e5/87d69b8824ca9b090f5a8ed47f758e8f6eecb871/3db757ffdd87ed8d7118b2250236a496502a660f/f758987ff0af3a4b5ee69e95cab6a5294e4367b0/94f01ecc2aa0be992865acc80ebb6701f731f955/4b710e8481ade7c9200e94d3018e99dc42a0a0e8/a63ce4eca86fd207e3db07c00fb7ccf4adf1b230/b91f481300e3a10eaf66b94fc39b740928762aaf/7991dbff6849f67e823b7cc0c15e5a90b0549b9f 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-2229). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Affected

  • Debian Linux
  • Amazon Linux 2
  • Red Hat Enterprise Linux
  • Ubuntu Linux
  • SUSE Linux
  • Oracle Linux
  • RESF Rocky Linux
  • Open Source Linux Kernel
  • IBM QRadar SIEM
  • 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: 5.1
VulDB Meta Temp Score: 5.0

VulDB Base Score: 4.8
VulDB Temp Score: 4.6
VulDB Vector: 🔒
VulDB Reliability: 🔍

NVD Base Score: 5.5
NVD Vector: 🔒

CVSSv2info

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

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

Exploitinginfo

Class: Infinite loop
CWE: CWE-835 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
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: b35a22760aa5008d82533e59b0f0b5eb1b02d4e5/87d69b8824ca9b090f5a8ed47f758e8f6eecb871/3db757ffdd87ed8d7118b2250236a496502a660f/f758987ff0af3a4b5ee69e95cab6a5294e4367b0/94f01ecc2aa0be992865acc80ebb6701f731f955/4b710e8481ade7c9200e94d3018e99dc42a0a0e8/a63ce4eca86fd207e3db07c00fb7ccf4adf1b230/b91f481300e3a10eaf66b94fc39b740928762aaf/7991dbff6849f67e823b7cc0c15e5a90b0549b9f

Timelineinfo

10/07/2025 Advisory disclosed
10/07/2025 +0 days CVE reserved
10/07/2025 +0 days VulDB entry created
04/19/2026 +194 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2022-50534 (🔒)
GCVE (CVE): GCVE-0-2022-50534
GCVE (VulDB): GCVE-100-327413
CERT Bund: WID-SEC-2025-2229 - Linux Kernel: Mehrere Schwachstellen

Entryinfo

Created: 10/07/2025 19:13
Updated: 04/19/2026 06:01
Changes: 10/07/2025 19:13 (58), 11/22/2025 21:33 (7), 12/22/2025 06:23 (1), 02/05/2026 19:47 (12), 03/01/2026 02:14 (1), 03/21/2026 06:16 (2), 04/19/2026 06:01 (1)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you need the next level of professionalism?

Upgrade your account now!