CVE-2022-50712: 
Linux Kernel vulnerability analysis and mitigation

CVE-2022-50712 is a locking defect in the Linux kernel's devlink subsystem where the region snapshot lock (region->snapshot_lock) is not held when flushing snapshots during region destruction. The vulnerability was published on December 24, 2025, and affects Linux kernel versions starting from commit 2dec18ad826f52658f7781ee995d236cc449b678 up to the fixes introduced in kernel 6.0.16, 6.1.2, and 6.2. It carries a CVSS base score of 0.0 (no severity rating assigned at time of publication) and an EPSS score of 0.017% (Feedly, EUVD).

The root cause is a missing lock acquisition (CWE-667: Improper Locking) in the devl_region_destroy() function within net/core/devlink.c. When the netdevsim driver triggers a reload via nsim_dev_reload_down(), it calls devl_region_destroy(), which in turn calls devlink_region_snapshot_del() without first acquiring region->snapshot_lock. This triggers a kernel locking assertion (WARNING splat) at devlink_region_snapshot_del+0x12e/0x140, as the function expects the lock to be held by the caller. The fix ensures the snapshot lock is acquired before iterating and flushing pending snapshots during region teardown (Feedly, kernel.org patch 1).

Exploitation of this vulnerability can cause a kernel warning splat and potential instability or crash in the Linux networking subsystem when a devlink region with pending snapshots is destroyed during a device reload. The primary impact is on system availability — specifically for systems using the netdevsim driver or other devlink-enabled network drivers — with no direct confidentiality or integrity impact identified. The vulnerability does not appear to enable privilege escalation or remote code execution based on available information (Feedly).

The vulnerability is fixed in Linux kernel versions 6.0.16, 6.1.2, and 6.2. Administrators should update to one of these patched versions or apply the corresponding stable-tree commits: 49383d4e59bb704341aaa1d51440ccce58270e61, 6298cab4d80bfdb6fe01fe31fd9f0ba26317fdae, and b4cafb3d2c740f8d1b1234b43ac4a60e5291c960. SUSE Linux has also issued kernel security advisories (SUSE-2026:0263-1 and SUSE-2026:0317-1) addressing this CVE for affected distributions (Feedly, LinuxSecurity SUSE advisory 1, LinuxSecurity SUSE advisory 2).