BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2022-50149High confidence

driver core: fix potential deadlock in __driver_attach

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 3 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Low, lowered one band.downgradedsince 11 May 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.14% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: No default targetRemediation target: Normal maintenance

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 3 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

7 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 3 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

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.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.0.2-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.0.2-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.0.2-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.0.2-1Debian Security Tracker ↗Source updated 6 Oct 2026
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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2022-50149 · CSAF 2.0 · revision 60 · interimSUSE Product Security TeamCVE-2022-50149
135 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • kernel-default as component of SLES-LTSS-TERADATA 15 SP2
  • kernel-source as component of SLES-LTSS-TERADATA 15 SP2
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
Summary
In the Linux kernel, the following vulnerability has been resolved: driver core: fix potential deadlock in __driver_attach In __driver_attach function, There are also AA deadlock problem, like the commit b232b02bf3c2 ("driver core: fix deadlock in __device_attach"). stack like commit b232b02bf3c2 ("driver core: fix deadlock in __device_attach"). list below: In __driver_attach function, The lock holding logic is as follows: ... __driver_attach if (driver_allows_async_probing(drv)) device_lock(dev) // get lock dev async_schedule_dev(__driver_attach_async_helper, dev); // func async_schedule_node async_schedule_node_domain(func) entry = kzalloc(sizeof(struct async_entry), GFP_ATOMIC); /* when fail or work limit, sync to execute func, but __driver_attach_async_helper will get lock dev as will, which will lead to A-A deadlock. */ if (!entry || atomic_read(&entry_count) > MAX_WORK) { func; else queue_work_node(node, system_unbound_wq, &entry->work) device_unlock(dev) As above show, when it is allowed to do async probes, because of out of memory or work limit, async work is not be allowed, to do sync execute instead. it will lead to A-A deadlock because of __driver_attach_async_helper getting lock dev. Reproduce: and it can be reproduce by make the condition (if (!entry || atomic_read(&entry_count) > MAX_WORK)) untenable, like below: [ 370.785650] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 370.787154] task:swapper/0 state:D stack: 0 pid: 1 ppid: 0 flags:0x00004000 [ 370.788865] Call Trace: [ 370.789374] [ 370.789841] __schedule+0x482/0x1050 [ 370.790613] schedule+0x92/0x1a0 [ 370.791290] schedule_preempt_disabled+0x2c/0x50 [ 370.792256] __mutex_lock.isra.0+0x757/0xec0 [ 370.793158] __mutex_lock_slowpath+0x1f/0x30 [ 370.794079] mutex_lock+0x50/0x60 [ 370.794795] __device_driver_lock+0x2f/0x70 [ 370.795677] ? driver_probe_device+0xd0/0xd0 [ 370.796576] __driver_attach_async_helper+0x1d/0xd0 [ 370.797318] ? driver_probe_device+0xd0/0xd0 [ 370.797957] async_schedule_node_domain+0xa5/0xc0 [ 370.798652] async_schedule_node+0x19/0x30 [ 370.799243] __driver_attach+0x246/0x290 [ 370.799828] ? driver_allows_async_probing+0xa0/0xa0 [ 370.800548] bus_for_each_dev+0x9d/0x130 [ 370.801132] driver_attach+0x22/0x30 [ 370.801666] bus_add_driver+0x290/0x340 [ 370.802246] driver_register+0x88/0x140 [ 370.802817] ? virtio_scsi_init+0x116/0x116 [ 370.803425] scsi_register_driver+0x1a/0x30 [ 370.804057] init_sd+0x184/0x226 [ 370.804533] do_one_initcall+0x71/0x3a0 [ 370.805107] kernel_init_freeable+0x39a/0x43a [ 370.805759] ? rest_init+0x150/0x150 [ 370.806283] kernel_init+0x26/0x230 [ 370.806799] ret_from_fork+0x1f/0x30 To fix the deadlock, move the async_schedule_dev outside device_lock, as we can see, in async_schedule_node_domain, the parameter of queue_work_node is system_unbound_wq, so it can accept concurrent operations. which will also not change the code logic, and will not lead to deadlock.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Optional official sources

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

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

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-55415

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 actionPatch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 3 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: driver core: fix potential deadlock in __driver_attach In __driver_attach function, There are also AA deadlock problem, like the commit b232b02bf3c2 ("driver core: fix deadlock in __device_attach"). stack like commit b232b02bf3c2 ("driver core: fix deadlock in __device_attach"). list below: In __driver_attach function, The lock holding logic is as follows: ... __driver_attach if (driver_allows_async_probing(drv)) device_lock(dev) // get lock dev async_schedule_dev(__driver_attach_async_helper, dev); // func async_schedule_node async_schedule_node_domain(func) entry = kzalloc(sizeof(struct async_entry), GFP_ATOMIC); /* when fail or work limit, sync to execute func, but __driver_attach_async_helper will get lock dev as will, which will lead to A-A deadlock. */ if (!entry || atomic_read(&entry_count) > MAX_WORK) { func; else queue_work_node(node, system_unbound_wq, &entry->work) device_unlock(dev) As above show, when it is allowed to do async probes, because of out of memory or work limit, async work is not be allowed, to do sync execute instead. it will lead to A-A deadlock because of __driver_attach_async_helper getting lock dev. Reproduce: and it can be reproduce by make the condition (if (!entry || atomic_read(&entry_count) > MAX_WORK)) untenable, like below: [ 370.785650] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 370.787154] task:swapper/0 state:D stack: 0 pid: 1 ppid: 0 flags:0x00004000 [ 370.788865] Call Trace: [ 370.789374] <TASK> [ 370.789841] __schedule+0x482/0x1050 [ 370.790613] schedule+0x92/0x1a0 [ 370.791290] schedule_preempt_disabled+0x2c/0x50 [ 370.792256] __mutex_lock.isra.0+0x757/0xec0 [ 370.793158] __mutex_lock_slowpath+0x1f/0x30 [ 370.794079] mutex_lock+0x50/0x60 [ 370.794795] __device_driver_lock+0x2f/0x70 [ 370.795677] ? driver_probe_device+0xd0/0xd0 [ 370.796576] __driver_attach_async_helper+0x1d/0xd0 [ 370.797318] ? driver_probe_device+0xd0/0xd0 [ 370.797957] async_schedule_node_domain+0xa5/0xc0 [ 370.798652] async_schedule_node+0x19/0x30 [ 370.799243] __driver_attach+0x246/0x290 [ 370.799828] ? driver_allows_async_probing+0xa0/0xa0 [ 370.800548] bus_for_each_dev+0x9d/0x130 [ 370.801132] driver_attach+0x22/0x30 [ 370.801666] bus_add_driver+0x290/0x340 [ 370.802246] driver_register+0x88/0x140 [ 370.802817] ? virtio_scsi_init+0x116/0x116 [ 370.803425] scsi_register_driver+0x1a/0x30 [ 370.804057] init_sd+0x184/0x226 [ 370.804533] do_one_initcall+0x71/0x3a0 [ 370.805107] kernel_init_freeable+0x39a/0x43a [ 370.805759] ? rest_init+0x150/0x150 [ 370.806283] kernel_init+0x26/0x230 [ 370.806799] ret_from_fork+0x1f/0x30 To fix the deadlock, move the async_schedule_dev outside device_lock, as we can see, in async_schedule_node_domain, the parameter of queue_work_node is system_unbound_wq, so it can accept concurrent operations. which will also not change the code logic, and will not lead to deadlock.

What

In the Linux kernel, the following vulnerability has been resolved: driver core: fix potential deadlock in __driver_attach In __driver_attach function, There are also AA deadlock problem, like the commit b232b02bf3c2 ("driver core: fix deadlock in __device_attach"). stack like commit b232b02bf3c2 ("driver core: fix deadlock in __device_attach"). list below: In __driver_attach function, The lock holding logic is as follows: ... __driver_attach if (driver_allows_async_probing(drv)) device_lock(dev) // get lock dev async_schedule_dev(__driver_attach_async_helper, dev); // func async_schedule_node async_schedule_node_domain(func) entry = kzalloc(sizeof(struct async_entry), GFP_ATOMIC); /* when fail or work limit, sync to execute func, but __driver_attach_async_helper will get lock dev as will, which will lead to A-A deadlock. */ if (!entry || atomic_read(&entry_count) > MAX_WORK) { func; else queue_work_node(node, system_unbound_wq, &entry->work) device_unlock(dev) As above show, when it is allowed to do async probes, because of out of memory or work limit, async work is not be allowed, to do sync execute instead. it will lead to A-A deadlock because of __driver_attach_async_helper getting lock dev. Reproduce: and it can be reproduce by make the condition (if (!entry || atomic_read(&entry_count) > MAX_WORK)) untenable, like below: [ 370.785650] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 370.787154] task:swapper/0 state:D stack: 0 pid: 1 ppid: 0 flags:0x00004000 [ 370.788865] Call Trace: [ 370.789374] <TASK> [ 370.789841] __schedule+0x482/0x1050 [ 370.790613] schedule+0x92/0x1a0 [ 370.791290] schedule_preempt_disabled+0x2c/0x50 [ 370.792256] __mutex_lock.isra.0+0x757/0xec0 [ 370.793158] __mutex_lock_slowpath+0x1f/0x30 [ 370.794079] mutex_lock+0x50/0x60 [ 370.794795] __device_driver_lock+0x2f/0x70 [ 370.795677] ? driver_probe_device+0xd0/0xd0 [ 370.796576] __driver_attach_async_helper+0x1d/0xd0 [ 370.797318] ? driver_probe_device+0xd0/0xd0 [ 370.797957] async_schedule_node_domain+0xa5/0xc0 [ 370.798652] async_schedule_node+0x19/0x30 [ 370.799243] __driver_attach+0x246/0x290 [ 370.799828] ? driver_allows_async_probing+0xa0/0xa0 [ 370.800548] bus_for_each_dev+0x9d/0x130 [ 370.801132] driver_attach+0x22/0x30 [ 370.801666] bus_add_driver+0x290/0x340 [ 370.802246] driver_register+0x88/0x140 [ 370.802817] ? virtio_scsi_init+0x116/0x116 [ 370.803425] scsi_register_driver+0x1a/0x30 [ 370.804057] init_sd+0x184/0x226 [ 370.804533] do_one_initcall+0x71/0x3a0 [ 370.805107] kernel_init_freeable+0x39a/0x43a [ 370.805759] ? rest_init+0x150/0x150 [ 370.806283] kernel_init+0x26/0x230 [ 370.806799] ret_from_fork+0x1f/0x30 To fix the deadlock, move the async_schedule_dev outside device_lock, as we can see, in async_schedule_node_domain, the parameter of queue_work_node is system_unbound_wq, so it can accept concurrent operations. which will also not change the code logic, and will not lead to deadlock.

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: driver core: fix potential deadlock in __driver_attach In __driver_attach function, There are also AA deadlock problem, like the commit b232b02bf3c2 ("driver core: fix deadlock in __device_attach"). stack like commit b232b02bf3c2 ("driver core: fix deadlock in __device_attach"). list below: In __driver_attach function, The lock holding logic is as follows: ... __driver_attach if (driver_allows_async_probing(drv)) device_lock(dev) // get lock dev async_schedule_dev(__driver_attach_async_helper, dev); // func async_schedule_node async_schedule_node_domain(func) entry = kzalloc(sizeof(struct async_entry), GFP_ATOMIC); /* when fail or work limit, sync to execute func, but __driver_attach_async_helper will get lock dev as will, which will lead to A-A deadlock. */ if (!entry || atomic_read(&entry_count) > MAX_WORK) { func; else queue_work_node(node, system_unbound_wq, &entry->work) device_unlock(dev) As above show, when it is allowed to do async probes, because of out of memory or work limit, async work is not be allowed, to do sync execute instead. it will lead to A-A deadlock because of __driver_attach_async_helper getting lock dev. Reproduce: and it can be reproduce by make the condition (if (!entry || atomic_read(&entry_count) > MAX_WORK)) untenable, like below: [ 370.785650] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 370.787154] task:swapper/0 state:D stack: 0 pid: 1 ppid: 0 flags:0x00004000 [ 370.788865] Call Trace: [ 370.789374] <TASK> [ 370.789841] __schedule+0x482/0x1050 [ 370.790613] schedule+0x92/0x1a0 [ 370.791290] schedule_preempt_disabled+0x2c/0x50 [ 370.792256] __mutex_lock.isra.0+0x757/0xec0 [ 370.793158] __mutex_lock_slowpath+0x1f/0x30 [ 370.794079] mutex_lock+0x50/0x60 [ 370.794795] __device_driver_lock+0x2f/0x70 [ 370.795677] ? driver_probe_device+0xd0/0xd0 [ 370.796576] __driver_attach_async_helper+0x1d/0xd0 [ 370.797318] ? driver_probe_device+0xd0/0xd0 [ 370.797957] async_schedule_node_domain+0xa5/0xc0 [ 370.798652] async_schedule_node+0x19/0x30 [ 370.799243] __driver_attach+0x246/0x290 [ 370.799828] ? driver_allows_async_probing+0xa0/0xa0 [ 370.800548] bus_for_each_dev+0x9d/0x130 [ 370.801132] driver_attach+0x22/0x30 [ 370.801666] bus_add_driver+0x290/0x340 [ 370.802246] driver_register+0x88/0x140 [ 370.802817] ? virtio_scsi_init+0x116/0x116 [ 370.803425] scsi_register_driver+0x1a/0x30 [ 370.804057] init_sd+0x184/0x226 [ 370.804533] do_one_initcall+0x71/0x3a0 [ 370.805107] kernel_init_freeable+0x39a/0x43a [ 370.805759] ? rest_init+0x150/0x150 [ 370.806283] kernel_init+0x26/0x230 [ 370.806799] ret_from_fork+0x1f/0x30 To fix the deadlock, move the async_schedule_dev outside device_lock, as we can see, in async_schedule_node_domain, the parameter of queue_work_node is system_unbound_wq, so it can accept concurrent operations. which will also not change the code logic, and will not lead to deadlock.

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-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 ↗
Cyber Security Agency of Singapore · English · CSA-SB-20250625Security Bulletin 25 Jun 2025

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 25 Jun 2025, published on 25 June 2025. Open the linked bulletin for the product, severity and reference information published in that issue.

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

d?id=CVE-2022-50137 Référence CVE CVE-2022-50138 https://www.cve.org/CVERecord?id=CVE-2022-50138 Référence CVE CVE-2022-50139 https://www.cve.org/CVERecord?id=CVE-2022-50139 Référence CVE CVE-2022-50140 https://www.cve.org/CVERecord?id=CVE-2022-50140 Référence CVE CVE-2022-50141 https://www.cve.org/CVERecord?id=CVE-2022-50141 Référence CVE CVE-2022-50142 https://www.cve.org/CVERecord?id=CVE-2022-50142 Référence CVE CVE-2022-50143 https://www.cve.org/CVERecord?id=CVE-2022-50143 Référence CVE CVE-2022-50145 https://www.cve.org/CVERecord?id=CVE-2022-50145 Référence CVE CVE-2022-50146 https://www.cve.org/CVERecord?id=CVE-2022-50146 Référence CVE CVE-2022-50149 https://www.cve.org/CVERecord?id=CVE-2022-50149 Référence CVE CVE-2022-50151 https://www.cve.org/CVERecord?id=CVE-2022-50151 Référence CVE CVE-2022-50152 https://www.cve.org/CVERecord?id=CVE-2022-50152 Référence CVE CVE-2022-50153 https://www.cve.org/CVERecord?id=CVE-2022-50153 Référence CVE CVE-2022-50154 https://www.cve.org/CVERecord?id=CVE-2022-50154 Référence CVE CVE-2022-50155 https://www.cve.org/CVERecord?id=CVE-2022-50155 Référence CVE CVE-2022-50156 https://www.cve.org/CVERecord?id=CVE-2022-50156 Référence CVE CVE-2022-50157 https://www.cve.org/CVERecord?id=CVE-2022-50157 Référence CVE CVE-2022-50158 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-50138 Référence CVE CVE-2022-50139 https://www.cve.org/CVERecord?id=CVE-2022-50139 Référence CVE CVE-2022-50140 https://www.cve.org/CVERecord?id=CVE-2022-50140 Référence CVE CVE-2022-50141 https://www.cve.org/CVERecord?id=CVE-2022-50141 Référence CVE CVE-2022-50142 https://www.cve.org/CVERecord?id=CVE-2022-50142 Référence CVE CVE-2022-50143 https://www.cve.org/CVERecord?id=CVE-2022-50143 Référence CVE CVE-2022-50144 https://www.cve.org/CVERecord?id=CVE-2022-50144 Référence CVE CVE-2022-50145 https://www.cve.org/CVERecord?id=CVE-2022-50145 Référence CVE CVE-2022-50146 https://www.cve.org/CVERecord?id=CVE-2022-50146 Référence CVE CVE-2022-50149 https://www.cve.org/CVERecord?id=CVE-2022-50149 Référence CVE CVE-2022-50151 https://www.cve.org/CVERecord?id=CVE-2022-50151 Référence CVE CVE-2022-50152 https://www.cve.org/CVERecord?id=CVE-2022-50152 Référence CVE CVE-2022-50153 https://www.cve.org/CVERecord?id=CVE-2022-50153 Référence CVE CVE-2022-50154 https://www.cve.org/CVERecord?id=CVE-2022-50154 Référence CVE CVE-2022-50155 https://www.cve.org/CVERecord?id=CVE-2022-50155 Référence CVE CVE-2022-50156 https://www.cve.org/CVERecord?id=CVE-2022-50156 Référence CVE CVE-2022-50157 https://www.cve.org/CVERecord?id=CVE-2022-50157 Référence CVE CVE-2022-50158 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2022-49934 Référence CVE CVE-2022-49948 https://www.cve.org/CVERecord?id=CVE-2022-49948 Référence CVE CVE-2022-49969 https://www.cve.org/CVERecord?id=CVE-2022-49969 Référence CVE CVE-2022-49993 https://www.cve.org/CVERecord?id=CVE-2022-49993 Référence CVE CVE-2022-50025 https://www.cve.org/CVERecord?id=CVE-2022-50025 Référence CVE CVE-2022-50027 https://www.cve.org/CVERecord?id=CVE-2022-50027 Référence CVE CVE-2022-50030 https://www.cve.org/CVERecord?id=CVE-2022-50030 Référence CVE CVE-2022-50033 https://www.cve.org/CVERecord?id=CVE-2022-50033 Référence CVE CVE-2022-50103 https://www.cve.org/CVERecord?id=CVE-2022-50103 Référence CVE CVE-2022-50149 https://www.cve.org/CVERecord?id=CVE-2022-50149 Référence CVE CVE-2022-50211 https://www.cve.org/CVERecord?id=CVE-2022-50211 Référence CVE CVE-2022-50226 https://www.cve.org/CVERecord?id=CVE-2022-50226 Référence CVE CVE-2023-2176 https://www.cve.org/CVERecord?id=CVE-2023-2176 Référence CVE CVE-2023-52878 https://www.cve.org/CVERecord?id=CVE-2023-52878 Référence CVE CVE-2023-52888 https://www.cve.org/CVERecord?id=CVE-2023-52888 Référence CVE CVE-2023-52923 https://www.cve.org/CVERecord?id=CVE-2023-52923 Référence CVE CVE-2023-52927 https://www.cve.org/CVERecord?id=CVE-2023-52927 Référence CVE CVE-2023-53020 https://www.cve.org/CVERecord?id=CV

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

d?id=CVE-2022-50137 Référence CVE CVE-2022-50138 https://www.cve.org/CVERecord?id=CVE-2022-50138 Référence CVE CVE-2022-50139 https://www.cve.org/CVERecord?id=CVE-2022-50139 Référence CVE CVE-2022-50140 https://www.cve.org/CVERecord?id=CVE-2022-50140 Référence CVE CVE-2022-50141 https://www.cve.org/CVERecord?id=CVE-2022-50141 Référence CVE CVE-2022-50142 https://www.cve.org/CVERecord?id=CVE-2022-50142 Référence CVE CVE-2022-50143 https://www.cve.org/CVERecord?id=CVE-2022-50143 Référence CVE CVE-2022-50145 https://www.cve.org/CVERecord?id=CVE-2022-50145 Référence CVE CVE-2022-50146 https://www.cve.org/CVERecord?id=CVE-2022-50146 Référence CVE CVE-2022-50149 https://www.cve.org/CVERecord?id=CVE-2022-50149 Référence CVE CVE-2022-50151 https://www.cve.org/CVERecord?id=CVE-2022-50151 Référence CVE CVE-2022-50152 https://www.cve.org/CVERecord?id=CVE-2022-50152 Référence CVE CVE-2022-50153 https://www.cve.org/CVERecord?id=CVE-2022-50153 Référence CVE CVE-2022-50154 https://www.cve.org/CVERecord?id=CVE-2022-50154 Référence CVE CVE-2022-50155 https://www.cve.org/CVERecord?id=CVE-2022-50155 Référence CVE CVE-2022-50156 https://www.cve.org/CVERecord?id=CVE-2022-50156 Référence CVE CVE-2022-50157 https://www.cve.org/CVERecord?id=CVE-2022-50157 Référence CVE CVE-2022-50158 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-50138 Référence CVE CVE-2022-50139 https://www.cve.org/CVERecord?id=CVE-2022-50139 Référence CVE CVE-2022-50140 https://www.cve.org/CVERecord?id=CVE-2022-50140 Référence CVE CVE-2022-50141 https://www.cve.org/CVERecord?id=CVE-2022-50141 Référence CVE CVE-2022-50142 https://www.cve.org/CVERecord?id=CVE-2022-50142 Référence CVE CVE-2022-50143 https://www.cve.org/CVERecord?id=CVE-2022-50143 Référence CVE CVE-2022-50144 https://www.cve.org/CVERecord?id=CVE-2022-50144 Référence CVE CVE-2022-50145 https://www.cve.org/CVERecord?id=CVE-2022-50145 Référence CVE CVE-2022-50146 https://www.cve.org/CVERecord?id=CVE-2022-50146 Référence CVE CVE-2022-50149 https://www.cve.org/CVERecord?id=CVE-2022-50149 Référence CVE CVE-2022-50151 https://www.cve.org/CVERecord?id=CVE-2022-50151 Référence CVE CVE-2022-50152 https://www.cve.org/CVERecord?id=CVE-2022-50152 Référence CVE CVE-2022-50153 https://www.cve.org/CVERecord?id=CVE-2022-50153 Référence CVE CVE-2022-50154 https://www.cve.org/CVERecord?id=CVE-2022-50154 Référence CVE CVE-2022-50155 https://www.cve.org/CVERecord?id=CVE-2022-50155 Référence CVE CVE-2022-50156 https://www.cve.org/CVERecord?id=CVE-2022-50156 Référence CVE CVE-2022-50157 https://www.cve.org/CVERecord?id=CVE-2022-50157 Référence CVE CVE-2022-50158 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-50138 Référence CVE CVE-2022-50139 https://www.cve.org/CVERecord?id=CVE-2022-50139 Référence CVE CVE-2022-50140 https://www.cve.org/CVERecord?id=CVE-2022-50140 Référence CVE CVE-2022-50141 https://www.cve.org/CVERecord?id=CVE-2022-50141 Référence CVE CVE-2022-50142 https://www.cve.org/CVERecord?id=CVE-2022-50142 Référence CVE CVE-2022-50143 https://www.cve.org/CVERecord?id=CVE-2022-50143 Référence CVE CVE-2022-50144 https://www.cve.org/CVERecord?id=CVE-2022-50144 Référence CVE CVE-2022-50145 https://www.cve.org/CVERecord?id=CVE-2022-50145 Référence CVE CVE-2022-50146 https://www.cve.org/CVERecord?id=CVE-2022-50146 Référence CVE CVE-2022-50149 https://www.cve.org/CVERecord?id=CVE-2022-50149 Référence CVE CVE-2022-50151 https://www.cve.org/CVERecord?id=CVE-2022-50151 Référence CVE CVE-2022-50152 https://www.cve.org/CVERecord?id=CVE-2022-50152 Référence CVE CVE-2022-50153 https://www.cve.org/CVERecord?id=CVE-2022-50153 Référence CVE CVE-2022-50154 https://www.cve.org/CVERecord?id=CVE-2022-50154 Référence CVE CVE-2022-50155 https://www.cve.org/CVERecord?id=CVE-2022-50155 Référence CVE CVE-2022-50156 https://www.cve.org/CVERecord?id=CVE-2022-50156 Référence CVE CVE-2022-50157 https://www.cve.org/CVERecord?id=CVE-2022-50157 Référence CVE CVE-2022-50158 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2022-026938Linux の Linux Kernel におけるリソースのロックに関する脆弱性

Linux の Linux Kernel には、リソースのロックに関する脆弱性が存在します。

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.
Fix availability varies by product
Affected
Fixed
Linux: < 5.1, 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
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
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 11 May 2026, 19:13 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-55415
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
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-55415↗Vendor CSAF · SUSE Product Security Team↗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-50149 · cve.blacktree.nl