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

drm/gma500: Fix BUG: sleeping function called from invalid context errors

Linux · Linux

5.3MediumCVSS 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.

1 package state
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 10 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-51329

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/gma500: Fix BUG: sleeping function called from invalid context errors gma_crtc_page_flip() was holding the event_lock spinlock while calling crtc_funcs->mode_set_base() which takes ww_mutex. The only reason to hold event_lock is to clear gma_crtc->page_flip_event on mode_set_base() errors. Instead unlock it after setting gma_crtc->page_flip_event and on errors re-take the lock and clear gma_crtc->page_flip_event it it is still set. This fixes the following WARN/stacktrace: [ 512.122953] BUG: sleeping function called from invalid context at kernel/locking/mutex.c:870 [ 512.123004] in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 1253, name: gnome-shell [ 512.123031] preempt_count: 1, expected: 0 [ 512.123048] RCU nest depth: 0, expected: 0 [ 512.123066] INFO: lockdep is turned off. [ 512.123080] irq event stamp: 0 [ 512.123094] hardirqs last enabled at (0): [<0000000000000000>] 0x0 [ 512.123134] hardirqs last disabled at (0): [<ffffffff8d0ec28c>] copy_process+0x9fc/0x1de0 [ 512.123176] softirqs last enabled at (0): [<ffffffff8d0ec28c>] copy_process+0x9fc/0x1de0 [ 512.123207] softirqs last disabled at (0): [<0000000000000000>] 0x0 [ 512.123233] Preemption disabled at: [ 512.123241] [<0000000000000000>] 0x0 [ 512.123275] CPU: 3 PID: 1253 Comm: gnome-shell Tainted: G W 5.19.0+ #1 [ 512.123304] Hardware name: Packard Bell dot s/SJE01_CT, BIOS V1.10 07/23/2013 [ 512.123323] Call Trace: [ 512.123346] <TASK> [ 512.123370] dump_stack_lvl+0x5b/0x77 [ 512.123412] __might_resched.cold+0xff/0x13a [ 512.123458] ww_mutex_lock+0x1e/0xa0 [ 512.123495] psb_gem_pin+0x2c/0x150 [gma500_gfx] [ 512.123601] gma_pipe_set_base+0x76/0x240 [gma500_gfx] [ 512.123708] gma_crtc_page_flip+0x95/0x130 [gma500_gfx] [ 512.123808] drm_mode_page_flip_ioctl+0x57d/0x5d0 [ 512.123897] ? drm_mode_cursor2_ioctl+0x10/0x10 [ 512.123936] drm_ioctl_kernel+0xa1/0x150 [ 512.123984] drm_ioctl+0x21f/0x420 [ 512.124025] ? drm_mode_cursor2_ioctl+0x10/0x10 [ 512.124070] ? rcu_read_lock_bh_held+0xb/0x60 [ 512.124104] ? lock_release+0x1ef/0x2d0 [ 512.124161] __x64_sys_ioctl+0x8d/0xd0 [ 512.124203] do_syscall_64+0x58/0x80 [ 512.124239] ? do_syscall_64+0x67/0x80 [ 512.124267] ? trace_hardirqs_on_prepare+0x55/0xe0 [ 512.124300] ? do_syscall_64+0x67/0x80 [ 512.124340] ? rcu_read_lock_sched_held+0x10/0x80 [ 512.124377] entry_SYSCALL_64_after_hwframe+0x63/0xcd [ 512.124411] RIP: 0033:0x7fcc4a70740f [ 512.124442] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00 [ 512.124470] RSP: 002b:00007ffda73f5390 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 [ 512.124503] RAX: ffffffffffffffda RBX: 000055cc9e474500 RCX: 00007fcc4a70740f [ 512.124524] RDX: 00007ffda73f5420 RSI: 00000000c01864b0 RDI: 0000000000000009 [ 512.124544] RBP: 00007ffda73f5420 R08: 000055cc9c0b0cb0 R09: 0000000000000034 [ 512.124564] R10: 0000000000000000 R11: 0000000000000246 R12: 00000000c01864b0 [ 512.124584] R13: 0000000000000009 R14: 000055cc9df484d0 R15: 000055cc9af5d0c0 [ 512.124647] </TASK>

What

In the Linux kernel, the following vulnerability has been resolved: drm/gma500: Fix BUG: sleeping function called from invalid context errors gma_crtc_page_flip() was holding the event_lock spinlock while calling crtc_funcs->mode_set_base() which takes ww_mutex. The only reason to hold event_lock is to clear gma_crtc->page_flip_event on mode_set_base() errors. Instead unlock it after setting gma_crtc->page_flip_event and on errors re-take the lock and clear gma_crtc->page_flip_event it it is still set. This fixes the following WARN/stacktrace: [ 512.122953] BUG: sleeping function called from invalid context at kernel/locking/mutex.c:870 [ 512.123004] in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 1253, name: gnome-shell [ 512.123031] preempt_count: 1, expected: 0 [ 512.123048] RCU nest depth: 0, expected: 0 [ 512.123066] INFO: lockdep is turned off. [ 512.123080] irq event stamp: 0 [ 512.123094] hardirqs last enabled at (0): [<0000000000000000>] 0x0 [ 512.123134] hardirqs last disabled at (0): [<ffffffff8d0ec28c>] copy_process+0x9fc/0x1de0 [ 512.123176] softirqs last enabled at (0): [<ffffffff8d0ec28c>] copy_process+0x9fc/0x1de0 [ 512.123207] softirqs last disabled at (0): [<0000000000000000>] 0x0 [ 512.123233] Preemption disabled at: [ 512.123241] [<0000000000000000>] 0x0 [ 512.123275] CPU: 3 PID: 1253 Comm: gnome-shell Tainted: G W 5.19.0+ #1 [ 512.123304] Hardware name: Packard Bell dot s/SJE01_CT, BIOS V1.10 07/23/2013 [ 512.123323] Call Trace: [ 512.123346] <TASK> [ 512.123370] dump_stack_lvl+0x5b/0x77 [ 512.123412] __might_resched.cold+0xff/0x13a [ 512.123458] ww_mutex_lock+0x1e/0xa0 [ 512.123495] psb_gem_pin+0x2c/0x150 [gma500_gfx] [ 512.123601] gma_pipe_set_base+0x76/0x240 [gma500_gfx] [ 512.123708] gma_crtc_page_flip+0x95/0x130 [gma500_gfx] [ 512.123808] drm_mode_page_flip_ioctl+0x57d/0x5d0 [ 512.123897] ? drm_mode_cursor2_ioctl+0x10/0x10 [ 512.123936] drm_ioctl_kernel+0xa1/0x150 [ 512.123984] drm_ioctl+0x21f/0x420 [ 512.124025] ? drm_mode_cursor2_ioctl+0x10/0x10 [ 512.124070] ? rcu_read_lock_bh_held+0xb/0x60 [ 512.124104] ? lock_release+0x1ef/0x2d0 [ 512.124161] __x64_sys_ioctl+0x8d/0xd0 [ 512.124203] do_syscall_64+0x58/0x80 [ 512.124239] ? do_syscall_64+0x67/0x80 [ 512.124267] ? trace_hardirqs_on_prepare+0x55/0xe0 [ 512.124300] ? do_syscall_64+0x67/0x80 [ 512.124340] ? rcu_read_lock_sched_held+0x10/0x80 [ 512.124377] entry_SYSCALL_64_after_hwframe+0x63/0xcd [ 512.124411] RIP: 0033:0x7fcc4a70740f [ 512.124442] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00 [ 512.124470] RSP: 002b:00007ffda73f5390 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 [ 512.124503] RAX: ffffffffffffffda RBX: 000055cc9e474500 RCX: 00007fcc4a70740f [ 512.124524] RDX: 00007ffda73f5420 RSI: 00000000c01864b0 RDI: 0000000000000009 [ 512.124544] RBP: 00007ffda73f5420 R08: 000055cc9c0b0cb0 R09: 0000000000000034 [ 512.124564] R10: 0000000000000000 R11: 0000000000000246 R12: 00000000c01864b0 [ 512.124584] R13: 0000000000000009 R14: 000055cc9df484d0 R15: 000055cc9af5d0c0 [ 512.124647] </TASK>

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/gma500: Fix BUG: sleeping function called from invalid context errors gma_crtc_page_flip() was holding the event_lock spinlock while calling crtc_funcs->mode_set_base() which takes ww_mutex. The only reason to hold event_lock is to clear gma_crtc->page_flip_event on mode_set_base() errors. Instead unlock it after setting gma_crtc->page_flip_event and on errors re-take the lock and clear gma_crtc->page_flip_event it it is still set. This fixes the following WARN/stacktrace: [ 512.122953] BUG: sleeping function called from invalid context at kernel/locking/mutex.c:870 [ 512.123004] in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 1253, name: gnome-shell [ 512.123031] preempt_count: 1, expected: 0 [ 512.123048] RCU nest depth: 0, expected: 0 [ 512.123066] INFO: lockdep is turned off. [ 512.123080] irq event stamp: 0 [ 512.123094] hardirqs last enabled at (0): [<0000000000000000>] 0x0 [ 512.123134] hardirqs last disabled at (0): [<ffffffff8d0ec28c>] copy_process+0x9fc/0x1de0 [ 512.123176] softirqs last enabled at (0): [<ffffffff8d0ec28c>] copy_process+0x9fc/0x1de0 [ 512.123207] softirqs last disabled at (0): [<0000000000000000>] 0x0 [ 512.123233] Preemption disabled at: [ 512.123241] [<0000000000000000>] 0x0 [ 512.123275] CPU: 3 PID: 1253 Comm: gnome-shell Tainted: G W 5.19.0+ #1 [ 512.123304] Hardware name: Packard Bell dot s/SJE01_CT, BIOS V1.10 07/23/2013 [ 512.123323] Call Trace: [ 512.123346] <TASK> [ 512.123370] dump_stack_lvl+0x5b/0x77 [ 512.123412] __might_resched.cold+0xff/0x13a [ 512.123458] ww_mutex_lock+0x1e/0xa0 [ 512.123495] psb_gem_pin+0x2c/0x150 [gma500_gfx] [ 512.123601] gma_pipe_set_base+0x76/0x240 [gma500_gfx] [ 512.123708] gma_crtc_page_flip+0x95/0x130 [gma500_gfx] [ 512.123808] drm_mode_page_flip_ioctl+0x57d/0x5d0 [ 512.123897] ? drm_mode_cursor2_ioctl+0x10/0x10 [ 512.123936] drm_ioctl_kernel+0xa1/0x150 [ 512.123984] drm_ioctl+0x21f/0x420 [ 512.124025] ? drm_mode_cursor2_ioctl+0x10/0x10 [ 512.124070] ? rcu_read_lock_bh_held+0xb/0x60 [ 512.124104] ? lock_release+0x1ef/0x2d0 [ 512.124161] __x64_sys_ioctl+0x8d/0xd0 [ 512.124203] do_syscall_64+0x58/0x80 [ 512.124239] ? do_syscall_64+0x67/0x80 [ 512.124267] ? trace_hardirqs_on_prepare+0x55/0xe0 [ 512.124300] ? do_syscall_64+0x67/0x80 [ 512.124340] ? rcu_read_lock_sched_held+0x10/0x80 [ 512.124377] entry_SYSCALL_64_after_hwframe+0x63/0xcd [ 512.124411] RIP: 0033:0x7fcc4a70740f [ 512.124442] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00 [ 512.124470] RSP: 002b:00007ffda73f5390 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 [ 512.124503] RAX: ffffffffffffffda RBX: 000055cc9e474500 RCX: 00007fcc4a70740f [ 512.124524] RDX: 00007ffda73f5420 RSI: 00000000c01864b0 RDI: 0000000000000009 [ 512.124544] RBP: 00007ffda73f5420 R08: 000055cc9c0b0cb0 R09: 0000000000000034 [ 512.124564] R10: 0000000000000000 R11: 0000000000000246 R12: 00000000c01864b0 [ 512.124584] R13: 0000000000000009 R14: 000055cc9df484d0 R15: 000055cc9af5d0c0 [ 512.124647] </TASK>

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:L/I:L/A:L

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.CLowConfidentiality impact: A successful attack can cause a limited loss.ILowIntegrity impact: A successful attack can cause a limited loss.ALowAvailability impact: A successful attack can cause a limited 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-2024-0984Linux Kernel: Mehrere Schwachstellen

Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen Denial-of-Service-Zustand herbeizuführen oder einen nicht spezifizierten Angriff durchzuführen.

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

d?id=CVE-2021-47383 Référence CVE CVE-2021-47402 https://www.cve.org/CVERecord?id=CVE-2021-47402 Référence CVE CVE-2021-47489 https://www.cve.org/CVERecord?id=CVE-2021-47489 Référence CVE CVE-2021-47491 https://www.cve.org/CVERecord?id=CVE-2021-47491 Référence CVE CVE-2021-47492 https://www.cve.org/CVERecord?id=CVE-2021-47492 Référence CVE CVE-2021-47517 https://www.cve.org/CVERecord?id=CVE-2021-47517 Référence CVE CVE-2021-47598 https://www.cve.org/CVERecord?id=CVE-2021-47598 Référence CVE CVE-2022-36280 https://www.cve.org/CVERecord?id=CVE-2022-36280 Référence CVE CVE-2022-48632 https://www.cve.org/CVERecord?id=CVE-2022-48632 Référence CVE CVE-2022-48634 https://www.cve.org/CVERecord?id=CVE-2022-48634 Référence CVE CVE-2022-48636 https://www.cve.org/CVERecord?id=CVE-2022-48636 Référence CVE CVE-2022-48651 https://www.cve.org/CVERecord?id=CVE-2022-48651 Référence CVE CVE-2022-48652 https://www.cve.org/CVERecord?id=CVE-2022-48652 Référence CVE CVE-2022-48662 https://www.cve.org/CVERecord?id=CVE-2022-48662 Référence CVE CVE-2022-48671 https://www.cve.org/CVERecord?id=CVE-2022-48671 Référence CVE CVE-2022-48672 https://www.cve.org/CVERecord?id=CVE-2022-48672 Référence CVE CVE-2022-48673 https://www.cve.org/CVERecord?id=CVE-2022-48673 Référence CVE CVE-2022-48675 https://www.cve.org/CVERecord?id=

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

ord?id=CVE-2021-47562 Référence CVE CVE-2021-47563 https://www.cve.org/CVERecord?id=CVE-2021-47563 Référence CVE CVE-2021-47564 https://www.cve.org/CVERecord?id=CVE-2021-47564 Référence CVE CVE-2021-47565 https://www.cve.org/CVERecord?id=CVE-2021-47565 Référence CVE CVE-2021-47569 https://www.cve.org/CVERecord?id=CVE-2021-47569 Référence CVE CVE-2022-1195 https://www.cve.org/CVERecord?id=CVE-2022-1195 Référence CVE CVE-2022-20132 https://www.cve.org/CVERecord?id=CVE-2022-20132 Référence CVE CVE-2022-48632 https://www.cve.org/CVERecord?id=CVE-2022-48632 Référence CVE CVE-2022-48633 https://www.cve.org/CVERecord?id=CVE-2022-48633 Référence CVE CVE-2022-48634 https://www.cve.org/CVERecord?id=CVE-2022-48634 Référence CVE CVE-2022-48636 https://www.cve.org/CVERecord?id=CVE-2022-48636 Référence CVE CVE-2022-48650 https://www.cve.org/CVERecord?id=CVE-2022-48650 Référence CVE CVE-2022-48651 https://www.cve.org/CVERecord?id=CVE-2022-48651 Référence CVE CVE-2022-48652 https://www.cve.org/CVERecord?id=CVE-2022-48652 Référence CVE CVE-2022-48662 https://www.cve.org/CVERecord?id=CVE-2022-48662 Référence CVE CVE-2022-48669 https://www.cve.org/CVERecord?id=CVE-2022-48669 Référence CVE CVE-2022-48671 https://www.cve.org/CVERecord?id=CVE-2022-48671 Référence CVE CVE-2022-48672 https://www.cve.org/CVERecord?id=

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

ord?id=CVE-2021-47562 Référence CVE CVE-2021-47563 https://www.cve.org/CVERecord?id=CVE-2021-47563 Référence CVE CVE-2021-47564 https://www.cve.org/CVERecord?id=CVE-2021-47564 Référence CVE CVE-2021-47565 https://www.cve.org/CVERecord?id=CVE-2021-47565 Référence CVE CVE-2021-47569 https://www.cve.org/CVERecord?id=CVE-2021-47569 Référence CVE CVE-2022-1195 https://www.cve.org/CVERecord?id=CVE-2022-1195 Référence CVE CVE-2022-20132 https://www.cve.org/CVERecord?id=CVE-2022-20132 Référence CVE CVE-2022-48632 https://www.cve.org/CVERecord?id=CVE-2022-48632 Référence CVE CVE-2022-48633 https://www.cve.org/CVERecord?id=CVE-2022-48633 Référence CVE CVE-2022-48634 https://www.cve.org/CVERecord?id=CVE-2022-48634 Référence CVE CVE-2022-48636 https://www.cve.org/CVERecord?id=CVE-2022-48636 Référence CVE CVE-2022-48650 https://www.cve.org/CVERecord?id=CVE-2022-48650 Référence CVE CVE-2022-48652 https://www.cve.org/CVERecord?id=CVE-2022-48652 Référence CVE CVE-2022-48662 https://www.cve.org/CVERecord?id=CVE-2022-48662 Référence CVE CVE-2022-48669 https://www.cve.org/CVERecord?id=CVE-2022-48669 Référence CVE CVE-2022-48671 https://www.cve.org/CVERecord?id=CVE-2022-48671 Référence CVE CVE-2022-48672 https://www.cve.org/CVERecord?id=CVE-2022-48672 Référence CVE CVE-2022-48673 https://www.cve.org/CVERecord?id=

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

ord?id=CVE-2021-47216 Référence CVE CVE-2021-47217 https://www.cve.org/CVERecord?id=CVE-2021-47217 Référence CVE CVE-2021-47218 https://www.cve.org/CVERecord?id=CVE-2021-47218 Référence CVE CVE-2021-47219 https://www.cve.org/CVERecord?id=CVE-2021-47219 Référence CVE CVE-2022-0487 https://www.cve.org/CVERecord?id=CVE-2022-0487 Référence CVE CVE-2022-48619 https://www.cve.org/CVERecord?id=CVE-2022-48619 Référence CVE CVE-2022-48626 https://www.cve.org/CVERecord?id=CVE-2022-48626 Référence CVE CVE-2022-48631 https://www.cve.org/CVERecord?id=CVE-2022-48631 Référence CVE CVE-2022-48632 https://www.cve.org/CVERecord?id=CVE-2022-48632 Référence CVE CVE-2022-48634 https://www.cve.org/CVERecord?id=CVE-2022-48634 Référence CVE CVE-2022-48636 https://www.cve.org/CVERecord?id=CVE-2022-48636 Référence CVE CVE-2022-48637 https://www.cve.org/CVERecord?id=CVE-2022-48637 Référence CVE CVE-2022-48638 https://www.cve.org/CVERecord?id=CVE-2022-48638 Référence CVE CVE-2022-48639 https://www.cve.org/CVERecord?id=CVE-2022-48639 Référence CVE CVE-2022-48640 https://www.cve.org/CVERecord?id=CVE-2022-48640 Référence CVE CVE-2022-48642 https://www.cve.org/CVERecord?id=CVE-2022-48642 Référence CVE CVE-2022-48644 https://www.cve.org/CVERecord?id=CVE-2022-48644 Référence CVE CVE-2022-48646 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
f76c22ce8fbbd03394eb9e2cd8c490d9ad2a116c < c5812807e416618477d1bb0049727ce8bb8292fd; f76c22ce8fbbd03394eb9e2cd8c490d9ad2a116c < e5ae504c8623476e13032670f1a6d6344d53ec9b; f76c22ce8fbbd03394eb9e2cd8c490d9ad2a116c < a6ed7624bf4d0a32f2631e74828bca7b7bf15afd; f76c22ce8fbbd03394eb9e2cd8c490d9ad2a116c < 63e37a79f7bd939314997e29c2f5a9f0ef184281; 5.6
Fixed
< 5.6; 5.10.146 ≤ 5.10.*; 5.15.71 ≤ 5.15.*; 5.19.12 ≤ 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 28 Apr 2024 · Last source change 11 May 2026, 18:44 UTC · CWE-667 · Improper Locking

CVE recordCVE.org · 5.2
CVSS sourceCISA ADP
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-51329
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-51329↗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-48634 · cve.blacktree.nl