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

md-raid10: fix KASAN warning

Linux · Linux

7.1HighCVSS 3.1
Recommended action
Within 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

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 9 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 9 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 9 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-55473

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

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: md-raid10: fix KASAN warning There's a KASAN warning in raid10_remove_disk when running the lvm test lvconvert-raid-reshape.sh. We fix this warning by verifying that the value "number" is valid. BUG: KASAN: slab-out-of-bounds in raid10_remove_disk+0x61/0x2a0 [raid10] Read of size 8 at addr ffff889108f3d300 by task mdX_raid10/124682 CPU: 3 PID: 124682 Comm: mdX_raid10 Not tainted 5.19.0-rc6 #1 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-2 04/01/2014 Call Trace: <TASK> dump_stack_lvl+0x34/0x44 print_report.cold+0x45/0x57a ? __lock_text_start+0x18/0x18 ? raid10_remove_disk+0x61/0x2a0 [raid10] kasan_report+0xa8/0xe0 ? raid10_remove_disk+0x61/0x2a0 [raid10] raid10_remove_disk+0x61/0x2a0 [raid10] Buffer I/O error on dev dm-76, logical block 15344, async page read ? __mutex_unlock_slowpath.constprop.0+0x1e0/0x1e0 remove_and_add_spares+0x367/0x8a0 [md_mod] ? super_written+0x1c0/0x1c0 [md_mod] ? mutex_trylock+0xac/0x120 ? _raw_spin_lock+0x72/0xc0 ? _raw_spin_lock_bh+0xc0/0xc0 md_check_recovery+0x848/0x960 [md_mod] raid10d+0xcf/0x3360 [raid10] ? sched_clock_cpu+0x185/0x1a0 ? rb_erase+0x4d4/0x620 ? var_wake_function+0xe0/0xe0 ? psi_group_change+0x411/0x500 ? preempt_count_sub+0xf/0xc0 ? _raw_spin_lock_irqsave+0x78/0xc0 ? __lock_text_start+0x18/0x18 ? raid10_sync_request+0x36c0/0x36c0 [raid10] ? preempt_count_sub+0xf/0xc0 ? _raw_spin_unlock_irqrestore+0x19/0x40 ? del_timer_sync+0xa9/0x100 ? try_to_del_timer_sync+0xc0/0xc0 ? _raw_spin_lock_irqsave+0x78/0xc0 ? __lock_text_start+0x18/0x18 ? _raw_spin_unlock_irq+0x11/0x24 ? __list_del_entry_valid+0x68/0xa0 ? finish_wait+0xa3/0x100 md_thread+0x161/0x260 [md_mod] ? unregister_md_personality+0xa0/0xa0 [md_mod] ? _raw_spin_lock_irqsave+0x78/0xc0 ? prepare_to_wait_event+0x2c0/0x2c0 ? unregister_md_personality+0xa0/0xa0 [md_mod] kthread+0x148/0x180 ? kthread_complete_and_exit+0x20/0x20 ret_from_fork+0x1f/0x30 </TASK> Allocated by task 124495: kasan_save_stack+0x1e/0x40 __kasan_kmalloc+0x80/0xa0 setup_conf+0x140/0x5c0 [raid10] raid10_run+0x4cd/0x740 [raid10] md_run+0x6f9/0x1300 [md_mod] raid_ctr+0x2531/0x4ac0 [dm_raid] dm_table_add_target+0x2b0/0x620 [dm_mod] table_load+0x1c8/0x400 [dm_mod] ctl_ioctl+0x29e/0x560 [dm_mod] dm_compat_ctl_ioctl+0x7/0x20 [dm_mod] __do_compat_sys_ioctl+0xfa/0x160 do_syscall_64+0x90/0xc0 entry_SYSCALL_64_after_hwframe+0x46/0xb0 Last potentially related work creation: kasan_save_stack+0x1e/0x40 __kasan_record_aux_stack+0x9e/0xc0 kvfree_call_rcu+0x84/0x480 timerfd_release+0x82/0x140 L __fput+0xfa/0x400 task_work_run+0x80/0xc0 exit_to_user_mode_prepare+0x155/0x160 syscall_exit_to_user_mode+0x12/0x40 do_syscall_64+0x42/0xc0 entry_SYSCALL_64_after_hwframe+0x46/0xb0 Second to last potentially related work creation: kasan_save_stack+0x1e/0x40 __kasan_record_aux_stack+0x9e/0xc0 kvfree_call_rcu+0x84/0x480 timerfd_release+0x82/0x140 __fput+0xfa/0x400 task_work_run+0x80/0xc0 exit_to_user_mode_prepare+0x155/0x160 syscall_exit_to_user_mode+0x12/0x40 do_syscall_64+0x42/0xc0 entry_SYSCALL_64_after_hwframe+0x46/0xb0 The buggy address belongs to the object at ffff889108f3d200 which belongs to the cache kmalloc-256 of size 256 The buggy address is located 0 bytes to the right of 256-byte region [ffff889108f3d200, ffff889108f3d300) The buggy address belongs to the physical page: page:000000007ef2a34c refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x1108f3c head:000000007ef2a34c order:2 compound_mapcount:0 compound_pincount:0 flags: 0x4000000000010200(slab|head|zone=2) raw: 4000000000010200 0000000000000000 dead000000000001 ffff889100042b40 raw: 0000000000000000 0000000080200020 00000001ffffffff 0000000000000000 page dumped because: kasan: bad access detected Memory state around the buggy address: ffff889108f3d200: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffff889108f3d280: 00 00 ---truncated---

What

In the Linux kernel, the following vulnerability has been resolved: md-raid10: fix KASAN warning There's a KASAN warning in raid10_remove_disk when running the lvm test lvconvert-raid-reshape.sh. We fix this warning by verifying that the value "number" is valid. BUG: KASAN: slab-out-of-bounds in raid10_remove_disk+0x61/0x2a0 [raid10] Read of size 8 at addr ffff889108f3d300 by task mdX_raid10/124682 CPU: 3 PID: 124682 Comm: mdX_raid10 Not tainted 5.19.0-rc6 #1 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-2 04/01/2014 Call Trace: <TASK> dump_stack_lvl+0x34/0x44 print_report.cold+0x45/0x57a ? __lock_text_start+0x18/0x18 ? raid10_remove_disk+0x61/0x2a0 [raid10] kasan_report+0xa8/0xe0 ? raid10_remove_disk+0x61/0x2a0 [raid10] raid10_remove_disk+0x61/0x2a0 [raid10] Buffer I/O error on dev dm-76, logical block 15344, async page read ? __mutex_unlock_slowpath.constprop.0+0x1e0/0x1e0 remove_and_add_spares+0x367/0x8a0 [md_mod] ? super_written+0x1c0/0x1c0 [md_mod] ? mutex_trylock+0xac/0x120 ? _raw_spin_lock+0x72/0xc0 ? _raw_spin_lock_bh+0xc0/0xc0 md_check_recovery+0x848/0x960 [md_mod] raid10d+0xcf/0x3360 [raid10] ? sched_clock_cpu+0x185/0x1a0 ? rb_erase+0x4d4/0x620 ? var_wake_function+0xe0/0xe0 ? psi_group_change+0x411/0x500 ? preempt_count_sub+0xf/0xc0 ? _raw_spin_lock_irqsave+0x78/0xc0 ? __lock_text_start+0x18/0x18 ? raid10_sync_request+0x36c0/0x36c0 [raid10] ? preempt_count_sub+0xf/0xc0 ? _raw_spin_unlock_irqrestore+0x19/0x40 ? del_timer_sync+0xa9/0x100 ? try_to_del_timer_sync+0xc0/0xc0 ? _raw_spin_lock_irqsave+0x78/0xc0 ? __lock_text_start+0x18/0x18 ? _raw_spin_unlock_irq+0x11/0x24 ? __list_del_entry_valid+0x68/0xa0 ? finish_wait+0xa3/0x100 md_thread+0x161/0x260 [md_mod] ? unregister_md_personality+0xa0/0xa0 [md_mod] ? _raw_spin_lock_irqsave+0x78/0xc0 ? prepare_to_wait_event+0x2c0/0x2c0 ? unregister_md_personality+0xa0/0xa0 [md_mod] kthread+0x148/0x180 ? kthread_complete_and_exit+0x20/0x20 ret_from_fork+0x1f/0x30 </TASK> Allocated by task 124495: kasan_save_stack+0x1e/0x40 __kasan_kmalloc+0x80/0xa0 setup_conf+0x140/0x5c0 [raid10] raid10_run+0x4cd/0x740 [raid10] md_run+0x6f9/0x1300 [md_mod] raid_ctr+0x2531/0x4ac0 [dm_raid] dm_table_add_target+0x2b0/0x620 [dm_mod] table_load+0x1c8/0x400 [dm_mod] ctl_ioctl+0x29e/0x560 [dm_mod] dm_compat_ctl_ioctl+0x7/0x20 [dm_mod] __do_compat_sys_ioctl+0xfa/0x160 do_syscall_64+0x90/0xc0 entry_SYSCALL_64_after_hwframe+0x46/0xb0 Last potentially related work creation: kasan_save_stack+0x1e/0x40 __kasan_record_aux_stack+0x9e/0xc0 kvfree_call_rcu+0x84/0x480 timerfd_release+0x82/0x140 L __fput+0xfa/0x400 task_work_run+0x80/0xc0 exit_to_user_mode_prepare+0x155/0x160 syscall_exit_to_user_mode+0x12/0x40 do_syscall_64+0x42/0xc0 entry_SYSCALL_64_after_hwframe+0x46/0xb0 Second to last potentially related work creation: kasan_save_stack+0x1e/0x40 __kasan_record_aux_stack+0x9e/0xc0 kvfree_call_rcu+0x84/0x480 timerfd_release+0x82/0x140 __fput+0xfa/0x400 task_work_run+0x80/0xc0 exit_to_user_mode_prepare+0x155/0x160 syscall_exit_to_user_mode+0x12/0x40 do_syscall_64+0x42/0xc0 entry_SYSCALL_64_after_hwframe+0x46/0xb0 The buggy address belongs to the object at ffff889108f3d200 which belongs to the cache kmalloc-256 of size 256 The buggy address is located 0 bytes to the right of 256-byte region [ffff889108f3d200, ffff889108f3d300) The buggy address belongs to the physical page: page:000000007ef2a34c refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x1108f3c head:000000007ef2a34c order:2 compound_mapcount:0 compound_pincount:0 flags: 0x4000000000010200(slab|head|zone=2) raw: 4000000000010200 0000000000000000 dead000000000001 ffff889100042b40 raw: 0000000000000000 0000000080200020 00000001ffffffff 0000000000000000 page dumped because: kasan: bad access detected Memory state around the buggy address: ffff889108f3d200: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffff889108f3d280: 00 00 ---truncated---

Why

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

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: md-raid10: fix KASAN warning There's a KASAN warning in raid10_remove_disk when running the lvm test lvconvert-raid-reshape.sh. We fix this warning by verifying that the value "number" is valid. BUG: KASAN: slab-out-of-bounds in raid10_remove_disk+0x61/0x2a0 [raid10] Read of size 8 at addr ffff889108f3d300 by task mdX_raid10/124682 CPU: 3 PID: 124682 Comm: mdX_raid10 Not tainted 5.19.0-rc6 #1 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-2 04/01/2014 Call Trace: <TASK> dump_stack_lvl+0x34/0x44 print_report.cold+0x45/0x57a ? __lock_text_start+0x18/0x18 ? raid10_remove_disk+0x61/0x2a0 [raid10] kasan_report+0xa8/0xe0 ? raid10_remove_disk+0x61/0x2a0 [raid10] raid10_remove_disk+0x61/0x2a0 [raid10] Buffer I/O error on dev dm-76, logical block 15344, async page read ? __mutex_unlock_slowpath.constprop.0+0x1e0/0x1e0 remove_and_add_spares+0x367/0x8a0 [md_mod] ? super_written+0x1c0/0x1c0 [md_mod] ? mutex_trylock+0xac/0x120 ? _raw_spin_lock+0x72/0xc0 ? _raw_spin_lock_bh+0xc0/0xc0 md_check_recovery+0x848/0x960 [md_mod] raid10d+0xcf/0x3360 [raid10] ? sched_clock_cpu+0x185/0x1a0 ? rb_erase+0x4d4/0x620 ? var_wake_function+0xe0/0xe0 ? psi_group_change+0x411/0x500 ? preempt_count_sub+0xf/0xc0 ? _raw_spin_lock_irqsave+0x78/0xc0 ? __lock_text_start+0x18/0x18 ? raid10_sync_request+0x36c0/0x36c0 [raid10] ? preempt_count_sub+0xf/0xc0 ? _raw_spin_unlock_irqrestore+0x19/0x40 ? del_timer_sync+0xa9/0x100 ? try_to_del_timer_sync+0xc0/0xc0 ? _raw_spin_lock_irqsave+0x78/0xc0 ? __lock_text_start+0x18/0x18 ? _raw_spin_unlock_irq+0x11/0x24 ? __list_del_entry_valid+0x68/0xa0 ? finish_wait+0xa3/0x100 md_thread+0x161/0x260 [md_mod] ? unregister_md_personality+0xa0/0xa0 [md_mod] ? _raw_spin_lock_irqsave+0x78/0xc0 ? prepare_to_wait_event+0x2c0/0x2c0 ? unregister_md_personality+0xa0/0xa0 [md_mod] kthread+0x148/0x180 ? kthread_complete_and_exit+0x20/0x20 ret_from_fork+0x1f/0x30 </TASK> Allocated by task 124495: kasan_save_stack+0x1e/0x40 __kasan_kmalloc+0x80/0xa0 setup_conf+0x140/0x5c0 [raid10] raid10_run+0x4cd/0x740 [raid10] md_run+0x6f9/0x1300 [md_mod] raid_ctr+0x2531/0x4ac0 [dm_raid] dm_table_add_target+0x2b0/0x620 [dm_mod] table_load+0x1c8/0x400 [dm_mod] ctl_ioctl+0x29e/0x560 [dm_mod] dm_compat_ctl_ioctl+0x7/0x20 [dm_mod] __do_compat_sys_ioctl+0xfa/0x160 do_syscall_64+0x90/0xc0 entry_SYSCALL_64_after_hwframe+0x46/0xb0 Last potentially related work creation: kasan_save_stack+0x1e/0x40 __kasan_record_aux_stack+0x9e/0xc0 kvfree_call_rcu+0x84/0x480 timerfd_release+0x82/0x140 L __fput+0xfa/0x400 task_work_run+0x80/0xc0 exit_to_user_mode_prepare+0x155/0x160 syscall_exit_to_user_mode+0x12/0x40 do_syscall_64+0x42/0xc0 entry_SYSCALL_64_after_hwframe+0x46/0xb0 Second to last potentially related work creation: kasan_save_stack+0x1e/0x40 __kasan_record_aux_stack+0x9e/0xc0 kvfree_call_rcu+0x84/0x480 timerfd_release+0x82/0x140 __fput+0xfa/0x400 task_work_run+0x80/0xc0 exit_to_user_mode_prepare+0x155/0x160 syscall_exit_to_user_mode+0x12/0x40 do_syscall_64+0x42/0xc0 entry_SYSCALL_64_after_hwframe+0x46/0xb0 The buggy address belongs to the object at ffff889108f3d200 which belongs to the cache kmalloc-256 of size 256 The buggy address is located 0 bytes to the right of 256-byte region [ffff889108f3d200, ffff889108f3d300) The buggy address belongs to the physical page: page:000000007ef2a34c refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x1108f3c head:000000007ef2a34c order:2 compound_mapcount:0 compound_pincount:0 flags: 0x4000000000010200(slab|head|zone=2) raw: 4000000000010200 0000000000000000 dead000000000001 ffff889100042b40 raw: 0000000000000000 0000000080200020 00000001ffffffff 0000000000000000 page dumped because: kasan: bad access detected Memory state around the buggy address: ffff889108f3d200: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffff889108f3d280: 00 00 ---truncated---

Why

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

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 → Out-of-bounds Read → 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-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:L/AC:L/PR:L/UI:N/S:U/C:H/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.CHighConfidentiality impact: A successful attack can cause a major loss.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-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-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-50200 Référence CVE CVE-2022-50201 https://www.cve.org/CVERecord?id=CVE-2022-50201 Référence CVE CVE-2022-50202 https://www.cve.org/CVERecord?id=CVE-2022-50202 Référence CVE CVE-2022-50203 https://www.cve.org/CVERecord?id=CVE-2022-50203 Référence CVE CVE-2022-50204 https://www.cve.org/CVERecord?id=CVE-2022-50204 Référence CVE CVE-2022-50206 https://www.cve.org/CVERecord?id=CVE-2022-50206 Référence CVE CVE-2022-50207 https://www.cve.org/CVERecord?id=CVE-2022-50207 Référence CVE CVE-2022-50208 https://www.cve.org/CVERecord?id=CVE-2022-50208 Référence CVE CVE-2022-50209 https://www.cve.org/CVERecord?id=CVE-2022-50209 Référence CVE CVE-2022-50211 https://www.cve.org/CVERecord?id=CVE-2022-50211 Référence CVE CVE-2022-50212 https://www.cve.org/CVERecord?id=CVE-2022-50212 Référence CVE CVE-2022-50213 https://www.cve.org/CVERecord?id=CVE-2022-50213 Référence CVE CVE-2022-50215 https://www.cve.org/CVERecord?id=CVE-2022-50215 Référence CVE CVE-2022-50218 https://www.cve.org/CVERecord?id=CVE-2022-50218 Référence CVE CVE-2022-50220 https://www.cve.org/CVERecord?id=CVE-2022-50220 Référence CVE CVE-2022-50222 https://www.cve.org/CVERecord?id=CVE-2022-50222 Référence CVE CVE-2022-50226 https://www.cve.org/CVERecord?id=CVE-2022-50226 Référence CVE CVE-2022-50228 https://www.cve.org/CVERecord?id=

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

embre 2025 https://access.redhat.com/errata/RHSA-2025:22661 Bulletin de sécurité Red Hat RHSA-2025:22752 du 04 décembre 2025 https://access.redhat.com/errata/RHSA-2025:22752 Référence CVE CVE-2022-48701 https://www.cve.org/CVERecord?id=CVE-2022-48701 Référence CVE CVE-2022-49969 https://www.cve.org/CVERecord?id=CVE-2022-49969 Référence CVE CVE-2022-49985 https://www.cve.org/CVERecord?id=CVE-2022-49985 Référence CVE CVE-2022-50050 https://www.cve.org/CVERecord?id=CVE-2022-50050 Référence CVE CVE-2022-50070 https://www.cve.org/CVERecord?id=CVE-2022-50070 Référence CVE CVE-2022-50087 https://www.cve.org/CVERecord?id=CVE-2022-50087 Référence CVE CVE-2022-50211 https://www.cve.org/CVERecord?id=CVE-2022-50211 Référence CVE CVE-2022-50228 https://www.cve.org/CVERecord?id=CVE-2022-50228 Référence CVE CVE-2022-50229 https://www.cve.org/CVERecord?id=CVE-2022-50229 Référence CVE CVE-2022-50356 https://www.cve.org/CVERecord?id=CVE-2022-50356 Référence CVE CVE-2022-50367 https://www.cve.org/CVERecord?id=CVE-2022-50367 Référence CVE CVE-2022-50386 https://www.cve.org/CVERecord?id=CVE-2022-50386 Référence CVE CVE-2022-50403 https://www.cve.org/CVERecord?id=CVE-2022-50403 Référence CVE CVE-2022-50408 https://www.cve.org/CVERecord?id=CVE-2022-50408 Référence CVE CVE-2022-50410 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-50200 Référence CVE CVE-2022-50201 https://www.cve.org/CVERecord?id=CVE-2022-50201 Référence CVE CVE-2022-50202 https://www.cve.org/CVERecord?id=CVE-2022-50202 Référence CVE CVE-2022-50203 https://www.cve.org/CVERecord?id=CVE-2022-50203 Référence CVE CVE-2022-50204 https://www.cve.org/CVERecord?id=CVE-2022-50204 Référence CVE CVE-2022-50206 https://www.cve.org/CVERecord?id=CVE-2022-50206 Référence CVE CVE-2022-50207 https://www.cve.org/CVERecord?id=CVE-2022-50207 Référence CVE CVE-2022-50208 https://www.cve.org/CVERecord?id=CVE-2022-50208 Référence CVE CVE-2022-50209 https://www.cve.org/CVERecord?id=CVE-2022-50209 Référence CVE CVE-2022-50211 https://www.cve.org/CVERecord?id=CVE-2022-50211 Référence CVE CVE-2022-50212 https://www.cve.org/CVERecord?id=CVE-2022-50212 Référence CVE CVE-2022-50213 https://www.cve.org/CVERecord?id=CVE-2022-50213 Référence CVE CVE-2022-50215 https://www.cve.org/CVERecord?id=CVE-2022-50215 Référence CVE CVE-2022-50218 https://www.cve.org/CVERecord?id=CVE-2022-50218 Référence CVE CVE-2022-50220 https://www.cve.org/CVERecord?id=CVE-2022-50220 Référence CVE CVE-2022-50221 https://www.cve.org/CVERecord?id=CVE-2022-50221 Référence CVE CVE-2022-50222 https://www.cve.org/CVERecord?id=CVE-2022-50222 Référence CVE CVE-2022-50226 https://www.cve.org/CVERecord?id=

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

01 octobre 2025 https://access.redhat.com/errata/RHSA-2025:17123 Bulletin de sécurité Red Hat RHSA-2025:17124 du 01 octobre 2025 https://access.redhat.com/errata/RHSA-2025:17124 Bulletin de sécurité Red Hat RHSA-2025:17192 du 01 octobre 2025 https://access.redhat.com/errata/RHSA-2025:17192 Bulletin de sécurité Red Hat RHSA-2025:17241 du 02 octobre 2025 https://access.redhat.com/errata/RHSA-2025:17241 Référence CVE CVE-2022-48701 https://www.cve.org/CVERecord?id=CVE-2022-48701 Référence CVE CVE-2022-49969 https://www.cve.org/CVERecord?id=CVE-2022-49969 Référence CVE CVE-2022-50087 https://www.cve.org/CVERecord?id=CVE-2022-50087 Référence CVE CVE-2022-50211 https://www.cve.org/CVERecord?id=CVE-2022-50211 Référence CVE CVE-2022-50229 https://www.cve.org/CVERecord?id=CVE-2022-50229 Référence CVE CVE-2023-53125 https://www.cve.org/CVERecord?id=CVE-2023-53125 Référence CVE CVE-2025-21759 https://www.cve.org/CVERecord?id=CVE-2025-21759 Référence CVE CVE-2025-22026 https://www.cve.org/CVERecord?id=CVE-2025-22026 Référence CVE CVE-2025-22058 https://www.cve.org/CVERecord?id=CVE-2025-22058 Référence CVE CVE-2025-22097 https://www.cve.org/CVERecord?id=CVE-2025-22097 Référence CVE CVE-2025-37797 https://www.cve.org/CVERecord?id=CVE-2025-37797 Référence CVE CVE-2025-37810 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2022-50066 Référence CVE CVE-2022-50080 https://www.cve.org/CVERecord?id=CVE-2022-50080 Référence CVE CVE-2022-50116 https://www.cve.org/CVERecord?id=CVE-2022-50116 Référence CVE CVE-2022-50127 https://www.cve.org/CVERecord?id=CVE-2022-50127 Référence CVE CVE-2022-50138 https://www.cve.org/CVERecord?id=CVE-2022-50138 Référence CVE CVE-2022-50141 https://www.cve.org/CVERecord?id=CVE-2022-50141 Référence CVE CVE-2022-50162 https://www.cve.org/CVERecord?id=CVE-2022-50162 Référence CVE CVE-2022-50185 https://www.cve.org/CVERecord?id=CVE-2022-50185 Référence CVE CVE-2022-50191 https://www.cve.org/CVERecord?id=CVE-2022-50191 Référence CVE CVE-2022-50211 https://www.cve.org/CVERecord?id=CVE-2022-50211 Référence CVE CVE-2022-50228 https://www.cve.org/CVERecord?id=CVE-2022-50228 Référence CVE CVE-2022-50229 https://www.cve.org/CVERecord?id=CVE-2022-50229 Référence CVE CVE-2023-3867 https://www.cve.org/CVERecord?id=CVE-2023-3867 Référence CVE CVE-2023-4130 https://www.cve.org/CVERecord?id=CVE-2023-4130 Référence CVE CVE-2023-4515 https://www.cve.org/CVERecord?id=CVE-2023-4515 Référence CVE CVE-2023-52813 https://www.cve.org/CVERecord?id=CVE-2023-52813 Référence CVE CVE-2023-53020 https://www.cve.org/CVERecord?id=CVE-2023-53020 Référence CVE CVE-2023-53117 https://www.cve.org/CVERecord?id=CVE-20

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

rrata/RHSA-2025:15661 Bulletin de sécurité Red Hat RHSA-2025:15662 du 11 septembre 2025 https://access.redhat.com/errata/RHSA-2025:15662 Bulletin de sécurité Red Hat RHSA-2025:15668 du 11 septembre 2025 https://access.redhat.com/errata/RHSA-2025:15668 Bulletin de sécurité Red Hat RHSA-2025:15669 du 11 septembre 2025 https://access.redhat.com/errata/RHSA-2025:15669 Bulletin de sécurité Red Hat RHSA-2025:15670 du 11 septembre 2025 https://access.redhat.com/errata/RHSA-2025:15670 Référence CVE CVE-2022-49985 https://www.cve.org/CVERecord?id=CVE-2022-49985 Référence CVE CVE-2022-50000 https://www.cve.org/CVERecord?id=CVE-2022-50000 Référence CVE CVE-2022-50211 https://www.cve.org/CVERecord?id=CVE-2022-50211 Référence CVE CVE-2023-2513 https://www.cve.org/CVERecord?id=CVE-2023-2513 Référence CVE CVE-2024-42094 https://www.cve.org/CVERecord?id=CVE-2024-42094 Référence CVE CVE-2024-50102 https://www.cve.org/CVERecord?id=CVE-2024-50102 Référence CVE CVE-2025-21759 https://www.cve.org/CVERecord?id=CVE-2025-21759 Référence CVE CVE-2025-22058 https://www.cve.org/CVERecord?id=CVE-2025-22058 Référence CVE CVE-2025-22097 https://www.cve.org/CVERecord?id=CVE-2025-22097 Référence CVE CVE-2025-37803 https://www.cve.org/CVERecord?id=CVE-2025-37803 Référence CVE CVE-2025-37914 https://www.cve.org/CVERecord?id=CV

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

d?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=CVE-2023-53020 Référence CVE CVE-2023-53117 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-50200 Référence CVE CVE-2022-50201 https://www.cve.org/CVERecord?id=CVE-2022-50201 Référence CVE CVE-2022-50202 https://www.cve.org/CVERecord?id=CVE-2022-50202 Référence CVE CVE-2022-50203 https://www.cve.org/CVERecord?id=CVE-2022-50203 Référence CVE CVE-2022-50204 https://www.cve.org/CVERecord?id=CVE-2022-50204 Référence CVE CVE-2022-50206 https://www.cve.org/CVERecord?id=CVE-2022-50206 Référence CVE CVE-2022-50207 https://www.cve.org/CVERecord?id=CVE-2022-50207 Référence CVE CVE-2022-50208 https://www.cve.org/CVERecord?id=CVE-2022-50208 Référence CVE CVE-2022-50209 https://www.cve.org/CVERecord?id=CVE-2022-50209 Référence CVE CVE-2022-50211 https://www.cve.org/CVERecord?id=CVE-2022-50211 Référence CVE CVE-2022-50212 https://www.cve.org/CVERecord?id=CVE-2022-50212 Référence CVE CVE-2022-50213 https://www.cve.org/CVERecord?id=CVE-2022-50213 Référence CVE CVE-2022-50215 https://www.cve.org/CVERecord?id=CVE-2022-50215 Référence CVE CVE-2022-50218 https://www.cve.org/CVERecord?id=CVE-2022-50218 Référence CVE CVE-2022-50220 https://www.cve.org/CVERecord?id=CVE-2022-50220 Référence CVE CVE-2022-50222 https://www.cve.org/CVERecord?id=CVE-2022-50222 Référence CVE CVE-2022-50226 https://www.cve.org/CVERecord?id=CVE-2022-50226 Référence CVE CVE-2022-50228 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-50200 Référence CVE CVE-2022-50201 https://www.cve.org/CVERecord?id=CVE-2022-50201 Référence CVE CVE-2022-50202 https://www.cve.org/CVERecord?id=CVE-2022-50202 Référence CVE CVE-2022-50203 https://www.cve.org/CVERecord?id=CVE-2022-50203 Référence CVE CVE-2022-50204 https://www.cve.org/CVERecord?id=CVE-2022-50204 Référence CVE CVE-2022-50206 https://www.cve.org/CVERecord?id=CVE-2022-50206 Référence CVE CVE-2022-50207 https://www.cve.org/CVERecord?id=CVE-2022-50207 Référence CVE CVE-2022-50208 https://www.cve.org/CVERecord?id=CVE-2022-50208 Référence CVE CVE-2022-50209 https://www.cve.org/CVERecord?id=CVE-2022-50209 Référence CVE CVE-2022-50211 https://www.cve.org/CVERecord?id=CVE-2022-50211 Référence CVE CVE-2022-50212 https://www.cve.org/CVERecord?id=CVE-2022-50212 Référence CVE CVE-2022-50213 https://www.cve.org/CVERecord?id=CVE-2022-50213 Référence CVE CVE-2022-50215 https://www.cve.org/CVERecord?id=CVE-2022-50215 Référence CVE CVE-2022-50218 https://www.cve.org/CVERecord?id=CVE-2022-50218 Référence CVE CVE-2022-50220 https://www.cve.org/CVERecord?id=CVE-2022-50220 Référence CVE CVE-2022-50221 https://www.cve.org/CVERecord?id=CVE-2022-50221 Référence CVE CVE-2022-50222 https://www.cve.org/CVERecord?id=CVE-2022-50222 Référence CVE CVE-2022-50226 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-50200 Référence CVE CVE-2022-50201 https://www.cve.org/CVERecord?id=CVE-2022-50201 Référence CVE CVE-2022-50202 https://www.cve.org/CVERecord?id=CVE-2022-50202 Référence CVE CVE-2022-50203 https://www.cve.org/CVERecord?id=CVE-2022-50203 Référence CVE CVE-2022-50204 https://www.cve.org/CVERecord?id=CVE-2022-50204 Référence CVE CVE-2022-50206 https://www.cve.org/CVERecord?id=CVE-2022-50206 Référence CVE CVE-2022-50207 https://www.cve.org/CVERecord?id=CVE-2022-50207 Référence CVE CVE-2022-50208 https://www.cve.org/CVERecord?id=CVE-2022-50208 Référence CVE CVE-2022-50209 https://www.cve.org/CVERecord?id=CVE-2022-50209 Référence CVE CVE-2022-50211 https://www.cve.org/CVERecord?id=CVE-2022-50211 Référence CVE CVE-2022-50212 https://www.cve.org/CVERecord?id=CVE-2022-50212 Référence CVE CVE-2022-50213 https://www.cve.org/CVERecord?id=CVE-2022-50213 Référence CVE CVE-2022-50215 https://www.cve.org/CVERecord?id=CVE-2022-50215 Référence CVE CVE-2022-50218 https://www.cve.org/CVERecord?id=CVE-2022-50218 Référence CVE CVE-2022-50220 https://www.cve.org/CVERecord?id=CVE-2022-50220 Référence CVE CVE-2022-50221 https://www.cve.org/CVERecord?id=CVE-2022-50221 Référence CVE CVE-2022-50222 https://www.cve.org/CVERecord?id=CVE-2022-50222 Référence CVE CVE-2022-50226 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
b8321b68d1445f308324517e45fb0a5c2b48e271 < 75fbd370a2cec9e92f48285bd90735ed0c837f52; b8321b68d1445f308324517e45fb0a5c2b48e271 < bcbdc26a44aba488d2f7122f2d66801bccb74733; b8321b68d1445f308324517e45fb0a5c2b48e271 < 7a6ccc8fa192fd357c2d5d4c6ce67c834a179e23; b8321b68d1445f308324517e45fb0a5c2b48e271 < ce839b9331c11780470f3d727b6fe3c2794a4620; b8321b68d1445f308324517e45fb0a5c2b48e271 < 5fd4ffa2372a41361d2bdd27ea5730e4e673240c; b8321b68d1445f308324517e45fb0a5c2b48e271 < 0f4d18cbea4a6e37a05fd8ee2887439f85211110; b8321b68d1445f308324517e45fb0a5c2b48e271 < bf30b9ba09b0ac2a10f04dce2b0835ec4d178aa6; b8321b68d1445f308324517e45fb0a5c2b48e271 < 5f57843565131bb782388f9d993f9ee8f453dee1
Fixed
< 3.3; 4.9.326 ≤ 4.9.*; 4.14.291 ≤ 4.14.*; 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.*
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 11 May 2026, 19:14 UTC · CWE-125 · Out-of-bounds Read

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-55473
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-55473↗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-50211 · cve.blacktree.nl