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

dlm: fix plock invalid read

Linux · Linux

9.8CriticalCVSS 3.1
Recommended action
Within 72 hours

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded.

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

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 actionWithin 72 hours

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded.

Patch available
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: dlm: fix plock invalid read This patch fixes an invalid read showed by KASAN. A unlock will allocate a "struct plock_op" and a followed send_op() will append it to a global send_list data structure. In some cases a followed dev_read() moves it to recv_list and dev_write() will cast it to "struct plock_xop" and access fields which are only available in those structures. At this point an invalid read happens by accessing those fields. To fix this issue the "callback" field is moved to "struct plock_op" to indicate that a cast to "plock_xop" is allowed and does the additional "plock_xop" handling if set. Example of the KASAN output which showed the invalid read: [ 2064.296453] ================================================================== [ 2064.304852] BUG: KASAN: slab-out-of-bounds in dev_write+0x52b/0x5a0 [dlm] [ 2064.306491] Read of size 8 at addr ffff88800ef227d8 by task dlm_controld/7484 [ 2064.308168] [ 2064.308575] CPU: 0 PID: 7484 Comm: dlm_controld Kdump: loaded Not tainted 5.14.0+ #9 [ 2064.310292] Hardware name: Red Hat KVM, BIOS 0.5.1 01/01/2011 [ 2064.311618] Call Trace: [ 2064.312218] dump_stack_lvl+0x56/0x7b [ 2064.313150] print_address_description.constprop.8+0x21/0x150 [ 2064.314578] ? dev_write+0x52b/0x5a0 [dlm] [ 2064.315610] ? dev_write+0x52b/0x5a0 [dlm] [ 2064.316595] kasan_report.cold.14+0x7f/0x11b [ 2064.317674] ? dev_write+0x52b/0x5a0 [dlm] [ 2064.318687] dev_write+0x52b/0x5a0 [dlm] [ 2064.319629] ? dev_read+0x4a0/0x4a0 [dlm] [ 2064.320713] ? bpf_lsm_kernfs_init_security+0x10/0x10 [ 2064.321926] vfs_write+0x17e/0x930 [ 2064.322769] ? __fget_light+0x1aa/0x220 [ 2064.323753] ksys_write+0xf1/0x1c0 [ 2064.324548] ? __ia32_sys_read+0xb0/0xb0 [ 2064.325464] do_syscall_64+0x3a/0x80 [ 2064.326387] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 2064.327606] RIP: 0033:0x7f807e4ba96f [ 2064.328470] Code: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 39 87 f8 ff 48 8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 31 44 89 c7 48 89 44 24 08 e8 7c 87 f8 ff 48 [ 2064.332902] RSP: 002b:00007ffd50cfe6e0 EFLAGS: 00000293 ORIG_RAX: 0000000000000001 [ 2064.334658] RAX: ffffffffffffffda RBX: 000055cc3886eb30 RCX: 00007f807e4ba96f [ 2064.336275] RDX: 0000000000000040 RSI: 00007ffd50cfe7e0 RDI: 0000000000000010 [ 2064.337980] RBP: 00007ffd50cfe7e0 R08: 0000000000000000 R09: 0000000000000001 [ 2064.339560] R10: 000055cc3886eb30 R11: 0000000000000293 R12: 000055cc3886eb80 [ 2064.341237] R13: 000055cc3886eb00 R14: 000055cc3886f590 R15: 0000000000000001 [ 2064.342857] [ 2064.343226] Allocated by task 12438: [ 2064.344057] kasan_save_stack+0x1c/0x40 [ 2064.345079] __kasan_kmalloc+0x84/0xa0 [ 2064.345933] kmem_cache_alloc_trace+0x13b/0x220 [ 2064.346953] dlm_posix_unlock+0xec/0x720 [dlm] [ 2064.348811] do_lock_file_wait.part.32+0xca/0x1d0 [ 2064.351070] fcntl_setlk+0x281/0xbc0 [ 2064.352879] do_fcntl+0x5e4/0xfe0 [ 2064.354657] __x64_sys_fcntl+0x11f/0x170 [ 2064.356550] do_syscall_64+0x3a/0x80 [ 2064.358259] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 2064.360745] [ 2064.361511] Last potentially related work creation: [ 2064.363957] kasan_save_stack+0x1c/0x40 [ 2064.365811] __kasan_record_aux_stack+0xaf/0xc0 [ 2064.368100] call_rcu+0x11b/0xf70 [ 2064.369785] dlm_process_incoming_buffer+0x47d/0xfd0 [dlm] [ 2064.372404] receive_from_sock+0x290/0x770 [dlm] [ 2064.374607] process_recv_sockets+0x32/0x40 [dlm] [ 2064.377290] process_one_work+0x9a8/0x16e0 [ 2064.379357] worker_thread+0x87/0xbf0 [ 2064.381188] kthread+0x3ac/0x490 [ 2064.383460] ret_from_fork+0x22/0x30 [ 2064.385588] [ 2064.386518] Second to last potentially related work creation: [ 2064.389219] kasan_save_stack+0x1c/0x40 [ 2064.391043] __kasan_record_aux_stack+0xaf/0xc0 [ 2064.393303] call_rcu+0x11b/0xf70 [ 2064.394885] dlm_process_incoming_buffer+0x47d/0xfd0 [dlm] [ 2064.397694] receive_from_sock+0x290/0x770 ---truncated---

What

In the Linux kernel, the following vulnerability has been resolved: dlm: fix plock invalid read This patch fixes an invalid read showed by KASAN. A unlock will allocate a "struct plock_op" and a followed send_op() will append it to a global send_list data structure. In some cases a followed dev_read() moves it to recv_list and dev_write() will cast it to "struct plock_xop" and access fields which are only available in those structures. At this point an invalid read happens by accessing those fields. To fix this issue the "callback" field is moved to "struct plock_op" to indicate that a cast to "plock_xop" is allowed and does the additional "plock_xop" handling if set. Example of the KASAN output which showed the invalid read: [ 2064.296453] ================================================================== [ 2064.304852] BUG: KASAN: slab-out-of-bounds in dev_write+0x52b/0x5a0 [dlm] [ 2064.306491] Read of size 8 at addr ffff88800ef227d8 by task dlm_controld/7484 [ 2064.308168] [ 2064.308575] CPU: 0 PID: 7484 Comm: dlm_controld Kdump: loaded Not tainted 5.14.0+ #9 [ 2064.310292] Hardware name: Red Hat KVM, BIOS 0.5.1 01/01/2011 [ 2064.311618] Call Trace: [ 2064.312218] dump_stack_lvl+0x56/0x7b [ 2064.313150] print_address_description.constprop.8+0x21/0x150 [ 2064.314578] ? dev_write+0x52b/0x5a0 [dlm] [ 2064.315610] ? dev_write+0x52b/0x5a0 [dlm] [ 2064.316595] kasan_report.cold.14+0x7f/0x11b [ 2064.317674] ? dev_write+0x52b/0x5a0 [dlm] [ 2064.318687] dev_write+0x52b/0x5a0 [dlm] [ 2064.319629] ? dev_read+0x4a0/0x4a0 [dlm] [ 2064.320713] ? bpf_lsm_kernfs_init_security+0x10/0x10 [ 2064.321926] vfs_write+0x17e/0x930 [ 2064.322769] ? __fget_light+0x1aa/0x220 [ 2064.323753] ksys_write+0xf1/0x1c0 [ 2064.324548] ? __ia32_sys_read+0xb0/0xb0 [ 2064.325464] do_syscall_64+0x3a/0x80 [ 2064.326387] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 2064.327606] RIP: 0033:0x7f807e4ba96f [ 2064.328470] Code: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 39 87 f8 ff 48 8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 31 44 89 c7 48 89 44 24 08 e8 7c 87 f8 ff 48 [ 2064.332902] RSP: 002b:00007ffd50cfe6e0 EFLAGS: 00000293 ORIG_RAX: 0000000000000001 [ 2064.334658] RAX: ffffffffffffffda RBX: 000055cc3886eb30 RCX: 00007f807e4ba96f [ 2064.336275] RDX: 0000000000000040 RSI: 00007ffd50cfe7e0 RDI: 0000000000000010 [ 2064.337980] RBP: 00007ffd50cfe7e0 R08: 0000000000000000 R09: 0000000000000001 [ 2064.339560] R10: 000055cc3886eb30 R11: 0000000000000293 R12: 000055cc3886eb80 [ 2064.341237] R13: 000055cc3886eb00 R14: 000055cc3886f590 R15: 0000000000000001 [ 2064.342857] [ 2064.343226] Allocated by task 12438: [ 2064.344057] kasan_save_stack+0x1c/0x40 [ 2064.345079] __kasan_kmalloc+0x84/0xa0 [ 2064.345933] kmem_cache_alloc_trace+0x13b/0x220 [ 2064.346953] dlm_posix_unlock+0xec/0x720 [dlm] [ 2064.348811] do_lock_file_wait.part.32+0xca/0x1d0 [ 2064.351070] fcntl_setlk+0x281/0xbc0 [ 2064.352879] do_fcntl+0x5e4/0xfe0 [ 2064.354657] __x64_sys_fcntl+0x11f/0x170 [ 2064.356550] do_syscall_64+0x3a/0x80 [ 2064.358259] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 2064.360745] [ 2064.361511] Last potentially related work creation: [ 2064.363957] kasan_save_stack+0x1c/0x40 [ 2064.365811] __kasan_record_aux_stack+0xaf/0xc0 [ 2064.368100] call_rcu+0x11b/0xf70 [ 2064.369785] dlm_process_incoming_buffer+0x47d/0xfd0 [dlm] [ 2064.372404] receive_from_sock+0x290/0x770 [dlm] [ 2064.374607] process_recv_sockets+0x32/0x40 [dlm] [ 2064.377290] process_one_work+0x9a8/0x16e0 [ 2064.379357] worker_thread+0x87/0xbf0 [ 2064.381188] kthread+0x3ac/0x490 [ 2064.383460] ret_from_fork+0x22/0x30 [ 2064.385588] [ 2064.386518] Second to last potentially related work creation: [ 2064.389219] kasan_save_stack+0x1c/0x40 [ 2064.391043] __kasan_record_aux_stack+0xaf/0xc0 [ 2064.393303] call_rcu+0x11b/0xf70 [ 2064.394885] dlm_process_incoming_buffer+0x47d/0xfd0 [dlm] [ 2064.397694] receive_from_sock+0x290/0x770 ---truncated---

Why

The product reads data past the end, or before the beginning, of the intended buffer.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. 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: dlm: fix plock invalid read This patch fixes an invalid read showed by KASAN. A unlock will allocate a "struct plock_op" and a followed send_op() will append it to a global send_list data structure. In some cases a followed dev_read() moves it to recv_list and dev_write() will cast it to "struct plock_xop" and access fields which are only available in those structures. At this point an invalid read happens by accessing those fields. To fix this issue the "callback" field is moved to "struct plock_op" to indicate that a cast to "plock_xop" is allowed and does the additional "plock_xop" handling if set. Example of the KASAN output which showed the invalid read: [ 2064.296453] ================================================================== [ 2064.304852] BUG: KASAN: slab-out-of-bounds in dev_write+0x52b/0x5a0 [dlm] [ 2064.306491] Read of size 8 at addr ffff88800ef227d8 by task dlm_controld/7484 [ 2064.308168] [ 2064.308575] CPU: 0 PID: 7484 Comm: dlm_controld Kdump: loaded Not tainted 5.14.0+ #9 [ 2064.310292] Hardware name: Red Hat KVM, BIOS 0.5.1 01/01/2011 [ 2064.311618] Call Trace: [ 2064.312218] dump_stack_lvl+0x56/0x7b [ 2064.313150] print_address_description.constprop.8+0x21/0x150 [ 2064.314578] ? dev_write+0x52b/0x5a0 [dlm] [ 2064.315610] ? dev_write+0x52b/0x5a0 [dlm] [ 2064.316595] kasan_report.cold.14+0x7f/0x11b [ 2064.317674] ? dev_write+0x52b/0x5a0 [dlm] [ 2064.318687] dev_write+0x52b/0x5a0 [dlm] [ 2064.319629] ? dev_read+0x4a0/0x4a0 [dlm] [ 2064.320713] ? bpf_lsm_kernfs_init_security+0x10/0x10 [ 2064.321926] vfs_write+0x17e/0x930 [ 2064.322769] ? __fget_light+0x1aa/0x220 [ 2064.323753] ksys_write+0xf1/0x1c0 [ 2064.324548] ? __ia32_sys_read+0xb0/0xb0 [ 2064.325464] do_syscall_64+0x3a/0x80 [ 2064.326387] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 2064.327606] RIP: 0033:0x7f807e4ba96f [ 2064.328470] Code: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 39 87 f8 ff 48 8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 31 44 89 c7 48 89 44 24 08 e8 7c 87 f8 ff 48 [ 2064.332902] RSP: 002b:00007ffd50cfe6e0 EFLAGS: 00000293 ORIG_RAX: 0000000000000001 [ 2064.334658] RAX: ffffffffffffffda RBX: 000055cc3886eb30 RCX: 00007f807e4ba96f [ 2064.336275] RDX: 0000000000000040 RSI: 00007ffd50cfe7e0 RDI: 0000000000000010 [ 2064.337980] RBP: 00007ffd50cfe7e0 R08: 0000000000000000 R09: 0000000000000001 [ 2064.339560] R10: 000055cc3886eb30 R11: 0000000000000293 R12: 000055cc3886eb80 [ 2064.341237] R13: 000055cc3886eb00 R14: 000055cc3886f590 R15: 0000000000000001 [ 2064.342857] [ 2064.343226] Allocated by task 12438: [ 2064.344057] kasan_save_stack+0x1c/0x40 [ 2064.345079] __kasan_kmalloc+0x84/0xa0 [ 2064.345933] kmem_cache_alloc_trace+0x13b/0x220 [ 2064.346953] dlm_posix_unlock+0xec/0x720 [dlm] [ 2064.348811] do_lock_file_wait.part.32+0xca/0x1d0 [ 2064.351070] fcntl_setlk+0x281/0xbc0 [ 2064.352879] do_fcntl+0x5e4/0xfe0 [ 2064.354657] __x64_sys_fcntl+0x11f/0x170 [ 2064.356550] do_syscall_64+0x3a/0x80 [ 2064.358259] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 2064.360745] [ 2064.361511] Last potentially related work creation: [ 2064.363957] kasan_save_stack+0x1c/0x40 [ 2064.365811] __kasan_record_aux_stack+0xaf/0xc0 [ 2064.368100] call_rcu+0x11b/0xf70 [ 2064.369785] dlm_process_incoming_buffer+0x47d/0xfd0 [dlm] [ 2064.372404] receive_from_sock+0x290/0x770 [dlm] [ 2064.374607] process_recv_sockets+0x32/0x40 [dlm] [ 2064.377290] process_one_work+0x9a8/0x16e0 [ 2064.379357] worker_thread+0x87/0xbf0 [ 2064.381188] kthread+0x3ac/0x490 [ 2064.383460] ret_from_fork+0x22/0x30 [ 2064.385588] [ 2064.386518] Second to last potentially related work creation: [ 2064.389219] kasan_save_stack+0x1c/0x40 [ 2064.391043] __kasan_record_aux_stack+0xaf/0xc0 [ 2064.393303] call_rcu+0x11b/0xf70 [ 2064.394885] dlm_process_incoming_buffer+0x47d/0xfd0 [dlm] [ 2064.397694] receive_from_sock+0x290/0x770 ---truncated---

Why

The product reads data past the end, or before the beginning, of the intended buffer.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. 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
a network path → Out-of-bounds Read → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
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-125 ↗

CWE-125: Out-of-bounds Read. The product reads data past the end, or before the beginning, of the intended buffer.

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

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

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-125
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-2107Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht näher beschriebene Auswirkungen zu erzielen.

Official advisory
CERT-FR · French · CERTFR-2025-AVI-1057Multiples vulnérabilités dans les produits VMware

d?id=CVE-2022-49379 Référence CVE CVE-2022-49384 https://www.cve.org/CVERecord?id=CVE-2022-49384 Référence CVE CVE-2022-49394 https://www.cve.org/CVERecord?id=CVE-2022-49394 Référence CVE CVE-2022-49400 https://www.cve.org/CVERecord?id=CVE-2022-49400 Référence CVE CVE-2022-49401 https://www.cve.org/CVERecord?id=CVE-2022-49401 Référence CVE CVE-2022-49402 https://www.cve.org/CVERecord?id=CVE-2022-49402 Référence CVE CVE-2022-49403 https://www.cve.org/CVERecord?id=CVE-2022-49403 Référence CVE CVE-2022-49404 https://www.cve.org/CVERecord?id=CVE-2022-49404 Référence CVE CVE-2022-49406 https://www.cve.org/CVERecord?id=CVE-2022-49406 Référence CVE CVE-2022-49407 https://www.cve.org/CVERecord?id=CVE-2022-49407 Référence CVE CVE-2022-49409 https://www.cve.org/CVERecord?id=CVE-2022-49409 Référence CVE CVE-2022-49422 https://www.cve.org/CVERecord?id=CVE-2022-49422 Référence CVE CVE-2022-49432 https://www.cve.org/CVERecord?id=CVE-2022-49432 Référence CVE CVE-2022-49433 https://www.cve.org/CVERecord?id=CVE-2022-49433 Référence CVE CVE-2022-49434 https://www.cve.org/CVERecord?id=CVE-2022-49434 Référence CVE CVE-2022-49436 https://www.cve.org/CVERecord?id=CVE-2022-49436 Référence CVE CVE-2022-49441 https://www.cve.org/CVERecord?id=CVE-2022-49441 Référence CVE CVE-2022-49446 https://www.cve.org/CVERecord?id=

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

rité Red Hat RHSA-2025:10211 du 02 juillet 2025 https://access.redhat.com/errata/RHSA-2025:10211 Référence CVE CVE-2022-48919 https://www.cve.org/CVERecord?id=CVE-2022-48919 Référence CVE CVE-2022-49111 https://www.cve.org/CVERecord?id=CVE-2022-49111 Référence CVE CVE-2022-49114 https://www.cve.org/CVERecord?id=CVE-2022-49114 Référence CVE CVE-2022-49122 https://www.cve.org/CVERecord?id=CVE-2022-49122 Référence CVE CVE-2022-49328 https://www.cve.org/CVERecord?id=CVE-2022-49328 Référence CVE CVE-2022-49377 https://www.cve.org/CVERecord?id=CVE-2022-49377 Référence CVE CVE-2022-49395 https://www.cve.org/CVERecord?id=CVE-2022-49395 Référence CVE CVE-2022-49407 https://www.cve.org/CVERecord?id=CVE-2022-49407 Référence CVE CVE-2023-1652 https://www.cve.org/CVERecord?id=CVE-2023-1652 Référence CVE CVE-2023-52623 https://www.cve.org/CVERecord?id=CVE-2023-52623 Référence CVE CVE-2023-52662 https://www.cve.org/CVERecord?id=CVE-2023-52662 Référence CVE CVE-2023-52933 https://www.cve.org/CVERecord?id=CVE-2023-52933 Référence CVE CVE-2024-26638 https://www.cve.org/CVERecord?id=CVE-2024-26638 Référence CVE CVE-2024-26669 https://www.cve.org/CVERecord?id=CVE-2024-26669 Référence CVE CVE-2024-26939 https://www.cve.org/CVERecord?id=CVE-2024-26939 Référence CVE CVE-2024-35838 https://www.cve.org/CVERecord?id=CV

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

d?id=CVE-2022-49395 Référence CVE CVE-2022-49396 https://www.cve.org/CVERecord?id=CVE-2022-49396 Référence CVE CVE-2022-49397 https://www.cve.org/CVERecord?id=CVE-2022-49397 Référence CVE CVE-2022-49398 https://www.cve.org/CVERecord?id=CVE-2022-49398 Référence CVE CVE-2022-49399 https://www.cve.org/CVERecord?id=CVE-2022-49399 Référence CVE CVE-2022-49400 https://www.cve.org/CVERecord?id=CVE-2022-49400 Référence CVE CVE-2022-49402 https://www.cve.org/CVERecord?id=CVE-2022-49402 Référence CVE CVE-2022-49404 https://www.cve.org/CVERecord?id=CVE-2022-49404 Référence CVE CVE-2022-49406 https://www.cve.org/CVERecord?id=CVE-2022-49406 Référence CVE CVE-2022-49407 https://www.cve.org/CVERecord?id=CVE-2022-49407 Référence CVE CVE-2022-49409 https://www.cve.org/CVERecord?id=CVE-2022-49409 Référence CVE CVE-2022-49410 https://www.cve.org/CVERecord?id=CVE-2022-49410 Référence CVE CVE-2022-49411 https://www.cve.org/CVERecord?id=CVE-2022-49411 Référence CVE CVE-2022-49412 https://www.cve.org/CVERecord?id=CVE-2022-49412 Référence CVE CVE-2022-49413 https://www.cve.org/CVERecord?id=CVE-2022-49413 Référence CVE CVE-2022-49414 https://www.cve.org/CVERecord?id=CVE-2022-49414 Référence CVE CVE-2022-49416 https://www.cve.org/CVERecord?id=CVE-2022-49416 Référence CVE CVE-2022-49418 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2022-49394 Référence CVE CVE-2022-49396 https://www.cve.org/CVERecord?id=CVE-2022-49396 Référence CVE CVE-2022-49397 https://www.cve.org/CVERecord?id=CVE-2022-49397 Référence CVE CVE-2022-49398 https://www.cve.org/CVERecord?id=CVE-2022-49398 Référence CVE CVE-2022-49399 https://www.cve.org/CVERecord?id=CVE-2022-49399 Référence CVE CVE-2022-49400 https://www.cve.org/CVERecord?id=CVE-2022-49400 Référence CVE CVE-2022-49402 https://www.cve.org/CVERecord?id=CVE-2022-49402 Référence CVE CVE-2022-49404 https://www.cve.org/CVERecord?id=CVE-2022-49404 Référence CVE CVE-2022-49406 https://www.cve.org/CVERecord?id=CVE-2022-49406 Référence CVE CVE-2022-49407 https://www.cve.org/CVERecord?id=CVE-2022-49407 Référence CVE CVE-2022-49409 https://www.cve.org/CVERecord?id=CVE-2022-49409 Référence CVE CVE-2022-49410 https://www.cve.org/CVERecord?id=CVE-2022-49410 Référence CVE CVE-2022-49411 https://www.cve.org/CVERecord?id=CVE-2022-49411 Référence CVE CVE-2022-49412 https://www.cve.org/CVERecord?id=CVE-2022-49412 Référence CVE CVE-2022-49413 https://www.cve.org/CVERecord?id=CVE-2022-49413 Référence CVE CVE-2022-49414 https://www.cve.org/CVERecord?id=CVE-2022-49414 Référence CVE CVE-2022-49416 https://www.cve.org/CVERecord?id=CVE-2022-49416 Référence CVE CVE-2022-49418 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2022-49392 Référence CVE CVE-2022-49394 https://www.cve.org/CVERecord?id=CVE-2022-49394 Référence CVE CVE-2022-49396 https://www.cve.org/CVERecord?id=CVE-2022-49396 Référence CVE CVE-2022-49397 https://www.cve.org/CVERecord?id=CVE-2022-49397 Référence CVE CVE-2022-49398 https://www.cve.org/CVERecord?id=CVE-2022-49398 Référence CVE CVE-2022-49399 https://www.cve.org/CVERecord?id=CVE-2022-49399 Référence CVE CVE-2022-49400 https://www.cve.org/CVERecord?id=CVE-2022-49400 Référence CVE CVE-2022-49402 https://www.cve.org/CVERecord?id=CVE-2022-49402 Référence CVE CVE-2022-49404 https://www.cve.org/CVERecord?id=CVE-2022-49404 Référence CVE CVE-2022-49407 https://www.cve.org/CVERecord?id=CVE-2022-49407 Référence CVE CVE-2022-49409 https://www.cve.org/CVERecord?id=CVE-2022-49409 Référence CVE CVE-2022-49410 https://www.cve.org/CVERecord?id=CVE-2022-49410 Référence CVE CVE-2022-49411 https://www.cve.org/CVERecord?id=CVE-2022-49411 Référence CVE CVE-2022-49412 https://www.cve.org/CVERecord?id=CVE-2022-49412 Référence CVE CVE-2022-49413 https://www.cve.org/CVERecord?id=CVE-2022-49413 Référence CVE CVE-2022-49414 https://www.cve.org/CVERecord?id=CVE-2022-49414 Référence CVE CVE-2022-49416 https://www.cve.org/CVERecord?id=CVE-2022-49416 Référence CVE CVE-2022-49418 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
586759f03e2e9031ac5589912a51a909ed53c30a < 2c55155cc365861044d9e6e80e342693e8805e33; 586759f03e2e9031ac5589912a51a909ed53c30a < 72f2f68970f9bdc252d59e119b385a6441b0b155; 586759f03e2e9031ac5589912a51a909ed53c30a < 5a1765adf9855cf0f6d3f7e0eb4b78ca66f70dee; 586759f03e2e9031ac5589912a51a909ed53c30a < 49cd9eb7b9a7b88124b31e31f8e539acaf1b3a6d; 586759f03e2e9031ac5589912a51a909ed53c30a < 899bc4429174861122f0c236588700a4710c1fec; 586759f03e2e9031ac5589912a51a909ed53c30a < acdad5bc9827922ec2f2e84fd198718aa8e8ab92; 586759f03e2e9031ac5589912a51a909ed53c30a < 56aa8d1fbd02357f3bf81bdfba1cde87ce8402fc; 586759f03e2e9031ac5589912a51a909ed53c30a < e421872fa17542cf33747071fb141b0130ce9ef7
Fixed
< 2.6.22; 4.9.318 ≤ 4.9.*; 4.14.283 ≤ 4.14.*; 4.19.247 ≤ 4.19.*; 5.4.198 ≤ 5.4.*; 5.10.121 ≤ 5.10.*; 5.15.46 ≤ 5.15.*; 5.17.14 ≤ 5.17.*
Action
Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 26 Feb 2025 · Last source change 5 Aug 2026, 08:55 UTC · CWE-125 · Out-of-bounds Read

CVE recordCVE.org · 5.2
CVSS sourceCNA
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-54822
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

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-54822↗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-49407 · cve.blacktree.nl