BlackTreeIndependent security intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2022-50173High confidence

drm/msm/mdp5: Fix global state lock backoff

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Scheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
Distribution package intelligence

Ubuntu vendor package status

Canonical’s release and source-package findings are shown separately from local repository availability.

3 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Ubuntu releaseSource packageVendor stateFixed versionEvidence
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 8 Sept 2026
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Select the national-authority views to include. The exact source language is shown on each matched advisory. Your choice is remembered on this device and encoded in the shareable URL.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2022-55438

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: drm/msm/mdp5: Fix global state lock backoff We need to grab the lock after the early return for !hwpipe case. Otherwise, we could have hit contention yet still returned 0. Fixes an issue that the new CONFIG_DRM_DEBUG_MODESET_LOCK stuff flagged in CI: WARNING: CPU: 0 PID: 282 at drivers/gpu/drm/drm_modeset_lock.c:296 drm_modeset_lock+0xf8/0x154 Modules linked in: CPU: 0 PID: 282 Comm: kms_cursor_lega Tainted: G W 5.19.0-rc2-15930-g875cc8bc536a #1 Hardware name: Qualcomm Technologies, Inc. DB820c (DT) pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : drm_modeset_lock+0xf8/0x154 lr : drm_atomic_get_private_obj_state+0x84/0x170 sp : ffff80000cfab6a0 x29: ffff80000cfab6a0 x28: 0000000000000000 x27: ffff000083bc4d00 x26: 0000000000000038 x25: 0000000000000000 x24: ffff80000957ca58 x23: 0000000000000000 x22: ffff000081ace080 x21: 0000000000000001 x20: ffff000081acec18 x19: ffff80000cfabb80 x18: 0000000000000038 x17: 0000000000000000 x16: 0000000000000000 x15: fffffffffffea0d0 x14: 0000000000000000 x13: 284e4f5f4e524157 x12: 5f534b434f4c5f47 x11: ffff80000a386aa8 x10: 0000000000000029 x9 : ffff80000cfab610 x8 : 0000000000000029 x7 : 0000000000000014 x6 : 0000000000000000 x5 : 0000000000000001 x4 : ffff8000081ad904 x3 : 0000000000000029 x2 : ffff0000801db4c0 x1 : ffff80000cfabb80 x0 : ffff000081aceb58 Call trace: drm_modeset_lock+0xf8/0x154 drm_atomic_get_private_obj_state+0x84/0x170 mdp5_get_global_state+0x54/0x6c mdp5_pipe_release+0x2c/0xd4 mdp5_plane_atomic_check+0x2ec/0x414 drm_atomic_helper_check_planes+0xd8/0x210 drm_atomic_helper_check+0x54/0xb0 ... ---[ end trace 0000000000000000 ]--- drm_modeset_lock attempting to lock a contended lock without backoff: drm_modeset_lock+0x148/0x154 mdp5_get_global_state+0x30/0x6c mdp5_pipe_release+0x2c/0xd4 mdp5_plane_atomic_check+0x290/0x414 drm_atomic_helper_check_planes+0xd8/0x210 drm_atomic_helper_check+0x54/0xb0 drm_atomic_check_only+0x4b0/0x8f4 drm_atomic_commit+0x68/0xe0 Patchwork: https://patchwork.freedesktop.org/patch/492701/

What

In the Linux kernel, the following vulnerability has been resolved: drm/msm/mdp5: Fix global state lock backoff We need to grab the lock after the early return for !hwpipe case. Otherwise, we could have hit contention yet still returned 0. Fixes an issue that the new CONFIG_DRM_DEBUG_MODESET_LOCK stuff flagged in CI: WARNING: CPU: 0 PID: 282 at drivers/gpu/drm/drm_modeset_lock.c:296 drm_modeset_lock+0xf8/0x154 Modules linked in: CPU: 0 PID: 282 Comm: kms_cursor_lega Tainted: G W 5.19.0-rc2-15930-g875cc8bc536a #1 Hardware name: Qualcomm Technologies, Inc. DB820c (DT) pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : drm_modeset_lock+0xf8/0x154 lr : drm_atomic_get_private_obj_state+0x84/0x170 sp : ffff80000cfab6a0 x29: ffff80000cfab6a0 x28: 0000000000000000 x27: ffff000083bc4d00 x26: 0000000000000038 x25: 0000000000000000 x24: ffff80000957ca58 x23: 0000000000000000 x22: ffff000081ace080 x21: 0000000000000001 x20: ffff000081acec18 x19: ffff80000cfabb80 x18: 0000000000000038 x17: 0000000000000000 x16: 0000000000000000 x15: fffffffffffea0d0 x14: 0000000000000000 x13: 284e4f5f4e524157 x12: 5f534b434f4c5f47 x11: ffff80000a386aa8 x10: 0000000000000029 x9 : ffff80000cfab610 x8 : 0000000000000029 x7 : 0000000000000014 x6 : 0000000000000000 x5 : 0000000000000001 x4 : ffff8000081ad904 x3 : 0000000000000029 x2 : ffff0000801db4c0 x1 : ffff80000cfabb80 x0 : ffff000081aceb58 Call trace: drm_modeset_lock+0xf8/0x154 drm_atomic_get_private_obj_state+0x84/0x170 mdp5_get_global_state+0x54/0x6c mdp5_pipe_release+0x2c/0xd4 mdp5_plane_atomic_check+0x2ec/0x414 drm_atomic_helper_check_planes+0xd8/0x210 drm_atomic_helper_check+0x54/0xb0 ... ---[ end trace 0000000000000000 ]--- drm_modeset_lock attempting to lock a contended lock without backoff: drm_modeset_lock+0x148/0x154 mdp5_get_global_state+0x30/0x6c mdp5_pipe_release+0x2c/0xd4 mdp5_plane_atomic_check+0x290/0x414 drm_atomic_helper_check_planes+0xd8/0x210 drm_atomic_helper_check+0x54/0xb0 drm_atomic_check_only+0x4b0/0x8f4 drm_atomic_commit+0x68/0xe0 Patchwork: https://patchwork.freedesktop.org/patch/492701/

Why

The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In the Linux kernel, the following vulnerability has been resolved: drm/msm/mdp5: Fix global state lock backoff We need to grab the lock after the early return for !hwpipe case. Otherwise, we could have hit contention yet still returned 0. Fixes an issue that the new CONFIG_DRM_DEBUG_MODESET_LOCK stuff flagged in CI: WARNING: CPU: 0 PID: 282 at drivers/gpu/drm/drm_modeset_lock.c:296 drm_modeset_lock+0xf8/0x154 Modules linked in: CPU: 0 PID: 282 Comm: kms_cursor_lega Tainted: G W 5.19.0-rc2-15930-g875cc8bc536a #1 Hardware name: Qualcomm Technologies, Inc. DB820c (DT) pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : drm_modeset_lock+0xf8/0x154 lr : drm_atomic_get_private_obj_state+0x84/0x170 sp : ffff80000cfab6a0 x29: ffff80000cfab6a0 x28: 0000000000000000 x27: ffff000083bc4d00 x26: 0000000000000038 x25: 0000000000000000 x24: ffff80000957ca58 x23: 0000000000000000 x22: ffff000081ace080 x21: 0000000000000001 x20: ffff000081acec18 x19: ffff80000cfabb80 x18: 0000000000000038 x17: 0000000000000000 x16: 0000000000000000 x15: fffffffffffea0d0 x14: 0000000000000000 x13: 284e4f5f4e524157 x12: 5f534b434f4c5f47 x11: ffff80000a386aa8 x10: 0000000000000029 x9 : ffff80000cfab610 x8 : 0000000000000029 x7 : 0000000000000014 x6 : 0000000000000000 x5 : 0000000000000001 x4 : ffff8000081ad904 x3 : 0000000000000029 x2 : ffff0000801db4c0 x1 : ffff80000cfabb80 x0 : ffff000081aceb58 Call trace: drm_modeset_lock+0xf8/0x154 drm_atomic_get_private_obj_state+0x84/0x170 mdp5_get_global_state+0x54/0x6c mdp5_pipe_release+0x2c/0xd4 mdp5_plane_atomic_check+0x2ec/0x414 drm_atomic_helper_check_planes+0xd8/0x210 drm_atomic_helper_check+0x54/0xb0 ... ---[ end trace 0000000000000000 ]--- drm_modeset_lock attempting to lock a contended lock without backoff: drm_modeset_lock+0x148/0x154 mdp5_get_global_state+0x30/0x6c mdp5_pipe_release+0x2c/0xd4 mdp5_plane_atomic_check+0x290/0x414 drm_atomic_helper_check_planes+0xd8/0x210 drm_atomic_helper_check+0x54/0xb0 drm_atomic_check_only+0x4b0/0x8f4 drm_atomic_commit+0x68/0xe0 Patchwork: https://patchwork.freedesktop.org/patch/492701/

Why

The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → Improper Locking → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-667 ↗

CWE-667: Improper Locking. The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
CWE-667
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-W-2025-1350Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service

Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.

Official advisory
CERT-FR · French · CERTFR-2026-AVI-0081Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2022-50158 Référence CVE CVE-2022-50160 https://www.cve.org/CVERecord?id=CVE-2022-50160 Référence CVE CVE-2022-50161 https://www.cve.org/CVERecord?id=CVE-2022-50161 Référence CVE CVE-2022-50162 https://www.cve.org/CVERecord?id=CVE-2022-50162 Référence CVE CVE-2022-50164 https://www.cve.org/CVERecord?id=CVE-2022-50164 Référence CVE CVE-2022-50165 https://www.cve.org/CVERecord?id=CVE-2022-50165 Référence CVE CVE-2022-50169 https://www.cve.org/CVERecord?id=CVE-2022-50169 Référence CVE CVE-2022-50171 https://www.cve.org/CVERecord?id=CVE-2022-50171 Référence CVE CVE-2022-50172 https://www.cve.org/CVERecord?id=CVE-2022-50172 Référence CVE CVE-2022-50173 https://www.cve.org/CVERecord?id=CVE-2022-50173 Référence CVE CVE-2022-50175 https://www.cve.org/CVERecord?id=CVE-2022-50175 Référence CVE CVE-2022-50176 https://www.cve.org/CVERecord?id=CVE-2022-50176 Référence CVE CVE-2022-50178 https://www.cve.org/CVERecord?id=CVE-2022-50178 Référence CVE CVE-2022-50179 https://www.cve.org/CVERecord?id=CVE-2022-50179 Référence CVE CVE-2022-50181 https://www.cve.org/CVERecord?id=CVE-2022-50181 Référence CVE CVE-2022-50185 https://www.cve.org/CVERecord?id=CVE-2022-50185 Référence CVE CVE-2022-50187 https://www.cve.org/CVERecord?id=CVE-2022-50187 Référence CVE CVE-2022-50190 https://www.cve.org/CVERecord?id=

Official advisory
CERT-FR · French · CERTFR-2025-AVI-1009Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2022-50160 Référence CVE CVE-2022-50161 https://www.cve.org/CVERecord?id=CVE-2022-50161 Référence CVE CVE-2022-50162 https://www.cve.org/CVERecord?id=CVE-2022-50162 Référence CVE CVE-2022-50164 https://www.cve.org/CVERecord?id=CVE-2022-50164 Référence CVE CVE-2022-50165 https://www.cve.org/CVERecord?id=CVE-2022-50165 Référence CVE CVE-2022-50166 https://www.cve.org/CVERecord?id=CVE-2022-50166 Référence CVE CVE-2022-50169 https://www.cve.org/CVERecord?id=CVE-2022-50169 Référence CVE CVE-2022-50171 https://www.cve.org/CVERecord?id=CVE-2022-50171 Référence CVE CVE-2022-50172 https://www.cve.org/CVERecord?id=CVE-2022-50172 Référence CVE CVE-2022-50173 https://www.cve.org/CVERecord?id=CVE-2022-50173 Référence CVE CVE-2022-50175 https://www.cve.org/CVERecord?id=CVE-2022-50175 Référence CVE CVE-2022-50176 https://www.cve.org/CVERecord?id=CVE-2022-50176 Référence CVE CVE-2022-50178 https://www.cve.org/CVERecord?id=CVE-2022-50178 Référence CVE CVE-2022-50179 https://www.cve.org/CVERecord?id=CVE-2022-50179 Référence CVE CVE-2022-50181 https://www.cve.org/CVERecord?id=CVE-2022-50181 Référence CVE CVE-2022-50183 https://www.cve.org/CVERecord?id=CVE-2022-50183 Référence CVE CVE-2022-50184 https://www.cve.org/CVERecord?id=CVE-2022-50184 Référence CVE CVE-2022-50185 https://www.cve.org/CVERecord?id=

Official advisory
CERT-FR · French · CERTFR-2025-AVI-0649Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2022-50158 Référence CVE CVE-2022-50160 https://www.cve.org/CVERecord?id=CVE-2022-50160 Référence CVE CVE-2022-50161 https://www.cve.org/CVERecord?id=CVE-2022-50161 Référence CVE CVE-2022-50162 https://www.cve.org/CVERecord?id=CVE-2022-50162 Référence CVE CVE-2022-50164 https://www.cve.org/CVERecord?id=CVE-2022-50164 Référence CVE CVE-2022-50165 https://www.cve.org/CVERecord?id=CVE-2022-50165 Référence CVE CVE-2022-50169 https://www.cve.org/CVERecord?id=CVE-2022-50169 Référence CVE CVE-2022-50171 https://www.cve.org/CVERecord?id=CVE-2022-50171 Référence CVE CVE-2022-50172 https://www.cve.org/CVERecord?id=CVE-2022-50172 Référence CVE CVE-2022-50173 https://www.cve.org/CVERecord?id=CVE-2022-50173 Référence CVE CVE-2022-50175 https://www.cve.org/CVERecord?id=CVE-2022-50175 Référence CVE CVE-2022-50176 https://www.cve.org/CVERecord?id=CVE-2022-50176 Référence CVE CVE-2022-50178 https://www.cve.org/CVERecord?id=CVE-2022-50178 Référence CVE CVE-2022-50179 https://www.cve.org/CVERecord?id=CVE-2022-50179 Référence CVE CVE-2022-50181 https://www.cve.org/CVERecord?id=CVE-2022-50181 Référence CVE CVE-2022-50185 https://www.cve.org/CVERecord?id=CVE-2022-50185 Référence CVE CVE-2022-50187 https://www.cve.org/CVERecord?id=CVE-2022-50187 Référence CVE CVE-2022-50190 https://www.cve.org/CVERecord?id=

Official advisory
CERT-FR · French · CERTFR-2025-AVI-0607Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2022-50160 Référence CVE CVE-2022-50161 https://www.cve.org/CVERecord?id=CVE-2022-50161 Référence CVE CVE-2022-50162 https://www.cve.org/CVERecord?id=CVE-2022-50162 Référence CVE CVE-2022-50164 https://www.cve.org/CVERecord?id=CVE-2022-50164 Référence CVE CVE-2022-50165 https://www.cve.org/CVERecord?id=CVE-2022-50165 Référence CVE CVE-2022-50166 https://www.cve.org/CVERecord?id=CVE-2022-50166 Référence CVE CVE-2022-50169 https://www.cve.org/CVERecord?id=CVE-2022-50169 Référence CVE CVE-2022-50171 https://www.cve.org/CVERecord?id=CVE-2022-50171 Référence CVE CVE-2022-50172 https://www.cve.org/CVERecord?id=CVE-2022-50172 Référence CVE CVE-2022-50173 https://www.cve.org/CVERecord?id=CVE-2022-50173 Référence CVE CVE-2022-50175 https://www.cve.org/CVERecord?id=CVE-2022-50175 Référence CVE CVE-2022-50176 https://www.cve.org/CVERecord?id=CVE-2022-50176 Référence CVE CVE-2022-50178 https://www.cve.org/CVERecord?id=CVE-2022-50178 Référence CVE CVE-2022-50179 https://www.cve.org/CVERecord?id=CVE-2022-50179 Référence CVE CVE-2022-50181 https://www.cve.org/CVERecord?id=CVE-2022-50181 Référence CVE CVE-2022-50183 https://www.cve.org/CVERecord?id=CVE-2022-50183 Référence CVE CVE-2022-50184 https://www.cve.org/CVERecord?id=CVE-2022-50184 Référence CVE CVE-2022-50185 https://www.cve.org/CVERecord?id=

Official advisory
CERT-FR · French · CERTFR-2025-AVI-0587Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2022-50160 Référence CVE CVE-2022-50161 https://www.cve.org/CVERecord?id=CVE-2022-50161 Référence CVE CVE-2022-50162 https://www.cve.org/CVERecord?id=CVE-2022-50162 Référence CVE CVE-2022-50164 https://www.cve.org/CVERecord?id=CVE-2022-50164 Référence CVE CVE-2022-50165 https://www.cve.org/CVERecord?id=CVE-2022-50165 Référence CVE CVE-2022-50166 https://www.cve.org/CVERecord?id=CVE-2022-50166 Référence CVE CVE-2022-50169 https://www.cve.org/CVERecord?id=CVE-2022-50169 Référence CVE CVE-2022-50171 https://www.cve.org/CVERecord?id=CVE-2022-50171 Référence CVE CVE-2022-50172 https://www.cve.org/CVERecord?id=CVE-2022-50172 Référence CVE CVE-2022-50173 https://www.cve.org/CVERecord?id=CVE-2022-50173 Référence CVE CVE-2022-50175 https://www.cve.org/CVERecord?id=CVE-2022-50175 Référence CVE CVE-2022-50176 https://www.cve.org/CVERecord?id=CVE-2022-50176 Référence CVE CVE-2022-50178 https://www.cve.org/CVERecord?id=CVE-2022-50178 Référence CVE CVE-2022-50179 https://www.cve.org/CVERecord?id=CVE-2022-50179 Référence CVE CVE-2022-50181 https://www.cve.org/CVERecord?id=CVE-2022-50181 Référence CVE CVE-2022-50183 https://www.cve.org/CVERecord?id=CVE-2022-50183 Référence CVE CVE-2022-50184 https://www.cve.org/CVERecord?id=CVE-2022-50184 Référence CVE CVE-2022-50185 https://www.cve.org/CVERecord?id=

Official advisory
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
776f5c58bfe16cf322d71eeed3c5dda1eeac7e6b < 247f2934324f9a18d18df24ea4bfcc7d4631d0ef; b2aa2c4efe93e2580d6a8774b04fe2b99756a322 < 2e34d6c8180a398de6448a93df25068bf3062042; 49dc28b4b2e28ef7564e355c91487996c1cbebd7 < bf386c955f35a0a01bef482b6035d40ff2f6cc75; 04bef5f1ba8ea6d7c1c8f5f65e0395c62db59cb8 < f4e3a8c7e890049e7ba2b49ad0315dae841dfa55; 33dc5aac46e0fad8f5eb193e5906ed0eb6b66ceb < 2fdf5a54ef9376ff69149a48c5616f1141008c9f; d59be579fa932c46b908f37509f319cbd4ca9a68 < 0b07f28c23ff50a7fa5dbc3f6b3b6bd53ac9fc70; d59be579fa932c46b908f37509f319cbd4ca9a68 < 92ef86ab513593c6329d04146e61f9a670e72fc5; 19964dfb39bda4d7716a71009488f0668ecbcf52
Fixed
< 5.19; 4.19.256 ≤ 4.19.*; 5.4.211 ≤ 5.4.*; 5.10.137 ≤ 5.10.*; 5.15.61 ≤ 5.15.*; 5.18.18 ≤ 5.18.*; 5.19.2 ≤ 5.19.*; 6.0 ≤ *
Action
Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 18 Jun 2025 · Last source change 23 May 2026, 15:23 UTC · CWE-667 · Improper Locking

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2022-55438
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceNIST NVD
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates →

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2022-55438↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2022-50173 · cve.blacktree.nl