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

udmabuf: Set the DMA mask for the udmabuf device (v2)

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Scheduled

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

Patch available
Distribution package intelligence

Ubuntu vendor package status

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

3 package states
Repository candidate not checked

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

Ubuntu releaseSource packageVendor stateFixed versionEvidence
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 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-55262

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: udmabuf: Set the DMA mask for the udmabuf device (v2) If the DMA mask is not set explicitly, the following warning occurs when the userspace tries to access the dma-buf via the CPU as reported by syzbot here: WARNING: CPU: 1 PID: 3595 at kernel/dma/mapping.c:188 __dma_map_sg_attrs+0x181/0x1f0 kernel/dma/mapping.c:188 Modules linked in: CPU: 0 PID: 3595 Comm: syz-executor249 Not tainted 5.17.0-rc2-syzkaller-00316-g0457e5153e0e #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 RIP: 0010:__dma_map_sg_attrs+0x181/0x1f0 kernel/dma/mapping.c:188 Code: 00 00 00 00 00 fc ff df 48 c1 e8 03 80 3c 10 00 75 71 4c 8b 3d c0 83 b5 0d e9 db fe ff ff e8 b6 0f 13 00 0f 0b e8 af 0f 13 00 <0f> 0b 45 31 e4 e9 54 ff ff ff e8 a0 0f 13 00 49 8d 7f 50 48 b8 00 RSP: 0018:ffffc90002a07d68 EFLAGS: 00010293 RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000 RDX: ffff88807e25e2c0 RSI: ffffffff81649e91 RDI: ffff88801b848408 RBP: ffff88801b848000 R08: 0000000000000002 R09: ffff88801d86c74f R10: ffffffff81649d72 R11: 0000000000000001 R12: 0000000000000002 R13: ffff88801d86c680 R14: 0000000000000001 R15: 0000000000000000 FS: 0000555556e30300(0000) GS:ffff8880b9d00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00000000200000cc CR3: 000000001d74a000 CR4: 00000000003506e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> dma_map_sgtable+0x70/0xf0 kernel/dma/mapping.c:264 get_sg_table.isra.0+0xe0/0x160 drivers/dma-buf/udmabuf.c:72 begin_cpu_udmabuf+0x130/0x1d0 drivers/dma-buf/udmabuf.c:126 dma_buf_begin_cpu_access+0xfd/0x1d0 drivers/dma-buf/dma-buf.c:1164 dma_buf_ioctl+0x259/0x2b0 drivers/dma-buf/dma-buf.c:363 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:874 [inline] __se_sys_ioctl fs/ioctl.c:860 [inline] __x64_sys_ioctl+0x193/0x200 fs/ioctl.c:860 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7f62fcf530f9 Code: 28 c3 e8 2a 14 00 00 66 2e 0f 1f 84 00 00 00 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007ffe3edab9b8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f62fcf530f9 RDX: 0000000020000200 RSI: 0000000040086200 RDI: 0000000000000006 RBP: 00007f62fcf170e0 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 00007f62fcf17170 R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 </TASK> v2: Dont't forget to deregister if DMA mask setup fails.

What

In the Linux kernel, the following vulnerability has been resolved: udmabuf: Set the DMA mask for the udmabuf device (v2) If the DMA mask is not set explicitly, the following warning occurs when the userspace tries to access the dma-buf via the CPU as reported by syzbot here: WARNING: CPU: 1 PID: 3595 at kernel/dma/mapping.c:188 __dma_map_sg_attrs+0x181/0x1f0 kernel/dma/mapping.c:188 Modules linked in: CPU: 0 PID: 3595 Comm: syz-executor249 Not tainted 5.17.0-rc2-syzkaller-00316-g0457e5153e0e #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 RIP: 0010:__dma_map_sg_attrs+0x181/0x1f0 kernel/dma/mapping.c:188 Code: 00 00 00 00 00 fc ff df 48 c1 e8 03 80 3c 10 00 75 71 4c 8b 3d c0 83 b5 0d e9 db fe ff ff e8 b6 0f 13 00 0f 0b e8 af 0f 13 00 <0f> 0b 45 31 e4 e9 54 ff ff ff e8 a0 0f 13 00 49 8d 7f 50 48 b8 00 RSP: 0018:ffffc90002a07d68 EFLAGS: 00010293 RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000 RDX: ffff88807e25e2c0 RSI: ffffffff81649e91 RDI: ffff88801b848408 RBP: ffff88801b848000 R08: 0000000000000002 R09: ffff88801d86c74f R10: ffffffff81649d72 R11: 0000000000000001 R12: 0000000000000002 R13: ffff88801d86c680 R14: 0000000000000001 R15: 0000000000000000 FS: 0000555556e30300(0000) GS:ffff8880b9d00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00000000200000cc CR3: 000000001d74a000 CR4: 00000000003506e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> dma_map_sgtable+0x70/0xf0 kernel/dma/mapping.c:264 get_sg_table.isra.0+0xe0/0x160 drivers/dma-buf/udmabuf.c:72 begin_cpu_udmabuf+0x130/0x1d0 drivers/dma-buf/udmabuf.c:126 dma_buf_begin_cpu_access+0xfd/0x1d0 drivers/dma-buf/dma-buf.c:1164 dma_buf_ioctl+0x259/0x2b0 drivers/dma-buf/dma-buf.c:363 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:874 [inline] __se_sys_ioctl fs/ioctl.c:860 [inline] __x64_sys_ioctl+0x193/0x200 fs/ioctl.c:860 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7f62fcf530f9 Code: 28 c3 e8 2a 14 00 00 66 2e 0f 1f 84 00 00 00 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007ffe3edab9b8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f62fcf530f9 RDX: 0000000020000200 RSI: 0000000040086200 RDI: 0000000000000006 RBP: 00007f62fcf170e0 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 00007f62fcf17170 R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 </TASK> v2: Dont't forget to deregister if DMA mask setup fails.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

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: udmabuf: Set the DMA mask for the udmabuf device (v2) If the DMA mask is not set explicitly, the following warning occurs when the userspace tries to access the dma-buf via the CPU as reported by syzbot here: WARNING: CPU: 1 PID: 3595 at kernel/dma/mapping.c:188 __dma_map_sg_attrs+0x181/0x1f0 kernel/dma/mapping.c:188 Modules linked in: CPU: 0 PID: 3595 Comm: syz-executor249 Not tainted 5.17.0-rc2-syzkaller-00316-g0457e5153e0e #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 RIP: 0010:__dma_map_sg_attrs+0x181/0x1f0 kernel/dma/mapping.c:188 Code: 00 00 00 00 00 fc ff df 48 c1 e8 03 80 3c 10 00 75 71 4c 8b 3d c0 83 b5 0d e9 db fe ff ff e8 b6 0f 13 00 0f 0b e8 af 0f 13 00 <0f> 0b 45 31 e4 e9 54 ff ff ff e8 a0 0f 13 00 49 8d 7f 50 48 b8 00 RSP: 0018:ffffc90002a07d68 EFLAGS: 00010293 RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000 RDX: ffff88807e25e2c0 RSI: ffffffff81649e91 RDI: ffff88801b848408 RBP: ffff88801b848000 R08: 0000000000000002 R09: ffff88801d86c74f R10: ffffffff81649d72 R11: 0000000000000001 R12: 0000000000000002 R13: ffff88801d86c680 R14: 0000000000000001 R15: 0000000000000000 FS: 0000555556e30300(0000) GS:ffff8880b9d00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00000000200000cc CR3: 000000001d74a000 CR4: 00000000003506e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> dma_map_sgtable+0x70/0xf0 kernel/dma/mapping.c:264 get_sg_table.isra.0+0xe0/0x160 drivers/dma-buf/udmabuf.c:72 begin_cpu_udmabuf+0x130/0x1d0 drivers/dma-buf/udmabuf.c:126 dma_buf_begin_cpu_access+0xfd/0x1d0 drivers/dma-buf/dma-buf.c:1164 dma_buf_ioctl+0x259/0x2b0 drivers/dma-buf/dma-buf.c:363 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:874 [inline] __se_sys_ioctl fs/ioctl.c:860 [inline] __x64_sys_ioctl+0x193/0x200 fs/ioctl.c:860 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7f62fcf530f9 Code: 28 c3 e8 2a 14 00 00 66 2e 0f 1f 84 00 00 00 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007ffe3edab9b8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f62fcf530f9 RDX: 0000000020000200 RSI: 0000000040086200 RDI: 0000000000000006 RBP: 00007f62fcf170e0 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 00007f62fcf17170 R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 </TASK> v2: Dont't forget to deregister if DMA mask setup fails.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

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 → vulnerable operation → 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.
CWE not yet assigned
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.
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-49960 Référence CVE CVE-2022-49964 https://www.cve.org/CVERecord?id=CVE-2022-49964 Référence CVE CVE-2022-49966 https://www.cve.org/CVERecord?id=CVE-2022-49966 Référence CVE CVE-2022-49968 https://www.cve.org/CVERecord?id=CVE-2022-49968 Référence CVE CVE-2022-49969 https://www.cve.org/CVERecord?id=CVE-2022-49969 Référence CVE CVE-2022-49977 https://www.cve.org/CVERecord?id=CVE-2022-49977 Référence CVE CVE-2022-49978 https://www.cve.org/CVERecord?id=CVE-2022-49978 Référence CVE CVE-2022-49981 https://www.cve.org/CVERecord?id=CVE-2022-49981 Référence CVE CVE-2022-49982 https://www.cve.org/CVERecord?id=CVE-2022-49982 Référence CVE CVE-2022-49983 https://www.cve.org/CVERecord?id=CVE-2022-49983 Référence CVE CVE-2022-49984 https://www.cve.org/CVERecord?id=CVE-2022-49984 Référence CVE CVE-2022-49985 https://www.cve.org/CVERecord?id=CVE-2022-49985 Référence CVE CVE-2022-49986 https://www.cve.org/CVERecord?id=CVE-2022-49986 Référence CVE CVE-2022-49987 https://www.cve.org/CVERecord?id=CVE-2022-49987 Référence CVE CVE-2022-49989 https://www.cve.org/CVERecord?id=CVE-2022-49989 Référence CVE CVE-2022-49990 https://www.cve.org/CVERecord?id=CVE-2022-49990 Référence CVE CVE-2022-49993 https://www.cve.org/CVERecord?id=CVE-2022-49993 Référence CVE CVE-2022-49995 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-49968 Référence CVE CVE-2022-49969 https://www.cve.org/CVERecord?id=CVE-2022-49969 Référence CVE CVE-2022-49971 https://www.cve.org/CVERecord?id=CVE-2022-49971 Référence CVE CVE-2022-49972 https://www.cve.org/CVERecord?id=CVE-2022-49972 Référence CVE CVE-2022-49977 https://www.cve.org/CVERecord?id=CVE-2022-49977 Référence CVE CVE-2022-49978 https://www.cve.org/CVERecord?id=CVE-2022-49978 Référence CVE CVE-2022-49980 https://www.cve.org/CVERecord?id=CVE-2022-49980 Référence CVE CVE-2022-49981 https://www.cve.org/CVERecord?id=CVE-2022-49981 Référence CVE CVE-2022-49982 https://www.cve.org/CVERecord?id=CVE-2022-49982 Référence CVE CVE-2022-49983 https://www.cve.org/CVERecord?id=CVE-2022-49983 Référence CVE CVE-2022-49984 https://www.cve.org/CVERecord?id=CVE-2022-49984 Référence CVE CVE-2022-49985 https://www.cve.org/CVERecord?id=CVE-2022-49985 Référence CVE CVE-2022-49986 https://www.cve.org/CVERecord?id=CVE-2022-49986 Référence CVE CVE-2022-49987 https://www.cve.org/CVERecord?id=CVE-2022-49987 Référence CVE CVE-2022-49989 https://www.cve.org/CVERecord?id=CVE-2022-49989 Référence CVE CVE-2022-49990 https://www.cve.org/CVERecord?id=CVE-2022-49990 Référence CVE CVE-2022-49993 https://www.cve.org/CVERecord?id=CVE-2022-49993 Référence CVE CVE-2022-49995 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2022-49960 Référence CVE CVE-2022-49964 https://www.cve.org/CVERecord?id=CVE-2022-49964 Référence CVE CVE-2022-49966 https://www.cve.org/CVERecord?id=CVE-2022-49966 Référence CVE CVE-2022-49968 https://www.cve.org/CVERecord?id=CVE-2022-49968 Référence CVE CVE-2022-49969 https://www.cve.org/CVERecord?id=CVE-2022-49969 Référence CVE CVE-2022-49977 https://www.cve.org/CVERecord?id=CVE-2022-49977 Référence CVE CVE-2022-49978 https://www.cve.org/CVERecord?id=CVE-2022-49978 Référence CVE CVE-2022-49981 https://www.cve.org/CVERecord?id=CVE-2022-49981 Référence CVE CVE-2022-49982 https://www.cve.org/CVERecord?id=CVE-2022-49982 Référence CVE CVE-2022-49983 https://www.cve.org/CVERecord?id=CVE-2022-49983 Référence CVE CVE-2022-49984 https://www.cve.org/CVERecord?id=CVE-2022-49984 Référence CVE CVE-2022-49985 https://www.cve.org/CVERecord?id=CVE-2022-49985 Référence CVE CVE-2022-49986 https://www.cve.org/CVERecord?id=CVE-2022-49986 Référence CVE CVE-2022-49987 https://www.cve.org/CVERecord?id=CVE-2022-49987 Référence CVE CVE-2022-49989 https://www.cve.org/CVERecord?id=CVE-2022-49989 Référence CVE CVE-2022-49990 https://www.cve.org/CVERecord?id=CVE-2022-49990 Référence CVE CVE-2022-49993 https://www.cve.org/CVERecord?id=CVE-2022-49993 Référence CVE CVE-2022-49995 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-49968 Référence CVE CVE-2022-49969 https://www.cve.org/CVERecord?id=CVE-2022-49969 Référence CVE CVE-2022-49971 https://www.cve.org/CVERecord?id=CVE-2022-49971 Référence CVE CVE-2022-49972 https://www.cve.org/CVERecord?id=CVE-2022-49972 Référence CVE CVE-2022-49977 https://www.cve.org/CVERecord?id=CVE-2022-49977 Référence CVE CVE-2022-49978 https://www.cve.org/CVERecord?id=CVE-2022-49978 Référence CVE CVE-2022-49980 https://www.cve.org/CVERecord?id=CVE-2022-49980 Référence CVE CVE-2022-49981 https://www.cve.org/CVERecord?id=CVE-2022-49981 Référence CVE CVE-2022-49982 https://www.cve.org/CVERecord?id=CVE-2022-49982 Référence CVE CVE-2022-49983 https://www.cve.org/CVERecord?id=CVE-2022-49983 Référence CVE CVE-2022-49984 https://www.cve.org/CVERecord?id=CVE-2022-49984 Référence CVE CVE-2022-49985 https://www.cve.org/CVERecord?id=CVE-2022-49985 Référence CVE CVE-2022-49986 https://www.cve.org/CVERecord?id=CVE-2022-49986 Référence CVE CVE-2022-49987 https://www.cve.org/CVERecord?id=CVE-2022-49987 Référence CVE CVE-2022-49989 https://www.cve.org/CVERecord?id=CVE-2022-49989 Référence CVE CVE-2022-49990 https://www.cve.org/CVERecord?id=CVE-2022-49990 Référence CVE CVE-2022-49993 https://www.cve.org/CVERecord?id=CVE-2022-49993 Référence CVE CVE-2022-49995 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-49968 Référence CVE CVE-2022-49969 https://www.cve.org/CVERecord?id=CVE-2022-49969 Référence CVE CVE-2022-49971 https://www.cve.org/CVERecord?id=CVE-2022-49971 Référence CVE CVE-2022-49972 https://www.cve.org/CVERecord?id=CVE-2022-49972 Référence CVE CVE-2022-49977 https://www.cve.org/CVERecord?id=CVE-2022-49977 Référence CVE CVE-2022-49978 https://www.cve.org/CVERecord?id=CVE-2022-49978 Référence CVE CVE-2022-49980 https://www.cve.org/CVERecord?id=CVE-2022-49980 Référence CVE CVE-2022-49981 https://www.cve.org/CVERecord?id=CVE-2022-49981 Référence CVE CVE-2022-49982 https://www.cve.org/CVERecord?id=CVE-2022-49982 Référence CVE CVE-2022-49983 https://www.cve.org/CVERecord?id=CVE-2022-49983 Référence CVE CVE-2022-49984 https://www.cve.org/CVERecord?id=CVE-2022-49984 Référence CVE CVE-2022-49985 https://www.cve.org/CVERecord?id=CVE-2022-49985 Référence CVE CVE-2022-49986 https://www.cve.org/CVERecord?id=CVE-2022-49986 Référence CVE CVE-2022-49987 https://www.cve.org/CVERecord?id=CVE-2022-49987 Référence CVE CVE-2022-49989 https://www.cve.org/CVERecord?id=CVE-2022-49989 Référence CVE CVE-2022-49990 https://www.cve.org/CVERecord?id=CVE-2022-49990 Référence CVE CVE-2022-49993 https://www.cve.org/CVERecord?id=CVE-2022-49993 Référence CVE CVE-2022-49995 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
284562e1f34874e267d4f499362c3816f8f6bc3f < 872875c9ecf8fa2e1d82bb2f2f1963f571aa8959; 284562e1f34874e267d4f499362c3816f8f6bc3f < e658538c610c6047b3c9f552e73801894d9284b1; 284562e1f34874e267d4f499362c3816f8f6bc3f < f2f6ea1a8da1317430a84701fc0170449ee88315; 284562e1f34874e267d4f499362c3816f8f6bc3f < 9e9fa6a9198b767b00f48160800128e83a038f9f; 5.6
Fixed
< 5.6; 5.10.141 ≤ 5.10.*; 5.15.65 ≤ 5.15.*; 5.19.7 ≤ 5.19.*; 6.0 ≤ *
Action
Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 18 Jun 2025 · Last source change 15 Aug 2026, 12:23 UTC · CWE not yet assigned

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-55262
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceUnavailable
NVD statusNVD modified after enrichment

Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates →
  1. Vendor guidanceAuthoritative vendor guidance changed from authoritative remediation link · patch to authoritative remediation link · patch.
    Before
    authoritative remediation link · patch
    After
    authoritative remediation link · patch
    416baaa9-dc9f-4396-8d5f-8c081fb06d67 ↗
  2. Vendor guidanceAuthoritative vendor guidance changed from authoritative remediation link · patch to authoritative remediation link · patch.
    Before
    authoritative remediation link · patch
    After
    authoritative remediation link · patch
    416baaa9-dc9f-4396-8d5f-8c081fb06d67 ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    fbb0de795078190a9834b3409e4b009cfb18a6d4 < 63d8c1933ed280717f934e2bc2edd869bb66f329; fbb0de795078190a9834b3409e4b009cfb18a6d4 < 872875c9ecf8fa2e1d82bb2f2f1963f571aa8959; fbb0de795078190a9834b3409e4b009cfb18a6d4 < e658538c610c6047b3c9f552e73801894d9284b1; fbb0de795078190a9834b3409e4b009cfb18a6d4 < f2f6ea1a8da1317430a84701fc0170449ee88315; fbb0de795078190a9834b3409e4b009cfb18a6d4 < 9e9fa6a9198b767b00f48160800128e83a038f9f; 4.20 · Fixed: < 4.20; 5.4.212 ≤ 5.4.*; 5.10.141 ≤ 5.10.*; 5.15.65 ≤ 5.15.*; 5.19.7 ≤ 5.19.*; 6.0 ≤ *
    After
    284562e1f34874e267d4f499362c3816f8f6bc3f < 872875c9ecf8fa2e1d82bb2f2f1963f571aa8959; 284562e1f34874e267d4f499362c3816f8f6bc3f < e658538c610c6047b3c9f552e73801894d9284b1; 284562e1f34874e267d4f499362c3816f8f6bc3f < f2f6ea1a8da1317430a84701fc0170449ee88315; 284562e1f34874e267d4f499362c3816f8f6bc3f < 9e9fa6a9198b767b00f48160800128e83a038f9f; 5.6 · Fixed: < 5.6; 5.10.141 ≤ 5.10.*; 5.15.65 ≤ 5.15.*; 5.19.7 ≤ 5.19.*; 6.0 ≤ *
    CNA ↗
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-55262↗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-49983 · cve.blacktree.nl