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

wifi: ath10k: Delay the unmapping of the buffer

Linux · Linux

7.5HighCVSS 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.

9 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-azure-6.11Affected, 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-gcp-6.11Affected, 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-hwe-6.11Affected, 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-lowlatency-hwe-6.11Affected, 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-nvidia-6.11Affected, 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-oem-6.11Affected, 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-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-2025-205178

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: wifi: ath10k: Delay the unmapping of the buffer On WCN3990, we are seeing a rare scenario where copy engine hardware is sending a copy complete interrupt to the host driver while still processing the buffer that the driver has sent, this is leading into an SMMU fault triggering kernel panic. This is happening on copy engine channel 3 (CE3) where the driver normally enqueues WMI commands to the firmware. Upon receiving a copy complete interrupt, host driver will immediately unmap and frees the buffer presuming that hardware has processed the buffer. In the issue case, upon receiving copy complete interrupt, host driver will unmap and free the buffer but since hardware is still accessing the buffer (which in this case got unmapped in parallel), SMMU hardware will trigger an SMMU fault resulting in a kernel panic. In order to avoid this, as a work around, add a delay before unmapping the copy engine source DMA buffer. This is conditionally done for WCN3990 and only for the CE3 channel where issue is seen. Below is the crash signature: wifi smmu error: kernel: [ 10.120965] arm-smmu 15000000.iommu: Unhandled context fault: fsr=0x402, iova=0x7fdfd8ac0, fsynr=0x500003,cbfrsynra=0xc1, cb=6 arm-smmu 15000000.iommu: Unhandled context fault:fsr=0x402, iova=0x7fe06fdc0, fsynr=0x710003, cbfrsynra=0xc1, cb=6 qcom-q6v5-mss 4080000.remoteproc: fatal error received: err_qdi.c:1040:EF:wlan_process:0x1:WLAN RT:0x2091: cmnos_thread.c:3998:Asserted in copy_engine.c:AXI_ERROR_DETECTED:2149 remoteproc remoteproc0: crash detected in 4080000.remoteproc: type fatal error <3> remoteproc remoteproc0: handling crash #1 in 4080000.remoteproc pc : __arm_lpae_unmap+0x500/0x514 lr : __arm_lpae_unmap+0x4bc/0x514 sp : ffffffc011ffb530 x29: ffffffc011ffb590 x28: 0000000000000000 x27: 0000000000000000 x26: 0000000000000004 x25: 0000000000000003 x24: ffffffc011ffb890 x23: ffffffa762ef9be0 x22: ffffffa77244ef00 x21: 0000000000000009 x20: 00000007fff7c000 x19: 0000000000000003 x18: 0000000000000000 x17: 0000000000000004 x16: ffffffd7a357d9f0 x15: 0000000000000000 x14: 00fd5d4fa7ffffff x13: 000000000000000e x12: 0000000000000000 x11: 00000000ffffffff x10: 00000000fffffe00 x9 : 000000000000017c x8 : 000000000000000c x7 : 0000000000000000 x6 : ffffffa762ef9000 x5 : 0000000000000003 x4 : 0000000000000004 x3 : 0000000000001000 x2 : 00000007fff7c000 x1 : ffffffc011ffb890 x0 : 0000000000000000 Call trace: __arm_lpae_unmap+0x500/0x514 __arm_lpae_unmap+0x4bc/0x514 __arm_lpae_unmap+0x4bc/0x514 arm_lpae_unmap_pages+0x78/0xa4 arm_smmu_unmap_pages+0x78/0x104 __iommu_unmap+0xc8/0x1e4 iommu_unmap_fast+0x38/0x48 __iommu_dma_unmap+0x84/0x104 iommu_dma_free+0x34/0x50 dma_free_attrs+0xa4/0xd0 ath10k_htt_rx_free+0xc4/0xf4 [ath10k_core] ath10k_core_stop+0x64/0x7c [ath10k_core] ath10k_halt+0x11c/0x180 [ath10k_core] ath10k_stop+0x54/0x94 [ath10k_core] drv_stop+0x48/0x1c8 [mac80211] ieee80211_do_open+0x638/0x77c [mac80211] ieee80211_open+0x48/0x5c [mac80211] __dev_open+0xb4/0x174 __dev_change_flags+0xc4/0x1dc dev_change_flags+0x3c/0x7c devinet_ioctl+0x2b4/0x580 inet_ioctl+0xb0/0x1b4 sock_do_ioctl+0x4c/0x16c compat_ifreq_ioctl+0x1cc/0x35c compat_sock_ioctl+0x110/0x2ac __arm64_compat_sys_ioctl+0xf4/0x3e0 el0_svc_common+0xb4/0x17c el0_svc_compat_handler+0x2c/0x58 el0_svc_compat+0x8/0x2c Tested-on: WCN3990 hw1.0 SNOC WLAN.HL.2.0-01387-QCAHLSWMTPLZ-1

What

In the Linux kernel, the following vulnerability has been resolved: wifi: ath10k: Delay the unmapping of the buffer On WCN3990, we are seeing a rare scenario where copy engine hardware is sending a copy complete interrupt to the host driver while still processing the buffer that the driver has sent, this is leading into an SMMU fault triggering kernel panic. This is happening on copy engine channel 3 (CE3) where the driver normally enqueues WMI commands to the firmware. Upon receiving a copy complete interrupt, host driver will immediately unmap and frees the buffer presuming that hardware has processed the buffer. In the issue case, upon receiving copy complete interrupt, host driver will unmap and free the buffer but since hardware is still accessing the buffer (which in this case got unmapped in parallel), SMMU hardware will trigger an SMMU fault resulting in a kernel panic. In order to avoid this, as a work around, add a delay before unmapping the copy engine source DMA buffer. This is conditionally done for WCN3990 and only for the CE3 channel where issue is seen. Below is the crash signature: wifi smmu error: kernel: [ 10.120965] arm-smmu 15000000.iommu: Unhandled context fault: fsr=0x402, iova=0x7fdfd8ac0, fsynr=0x500003,cbfrsynra=0xc1, cb=6 arm-smmu 15000000.iommu: Unhandled context fault:fsr=0x402, iova=0x7fe06fdc0, fsynr=0x710003, cbfrsynra=0xc1, cb=6 qcom-q6v5-mss 4080000.remoteproc: fatal error received: err_qdi.c:1040:EF:wlan_process:0x1:WLAN RT:0x2091: cmnos_thread.c:3998:Asserted in copy_engine.c:AXI_ERROR_DETECTED:2149 remoteproc remoteproc0: crash detected in 4080000.remoteproc: type fatal error <3> remoteproc remoteproc0: handling crash #1 in 4080000.remoteproc pc : __arm_lpae_unmap+0x500/0x514 lr : __arm_lpae_unmap+0x4bc/0x514 sp : ffffffc011ffb530 x29: ffffffc011ffb590 x28: 0000000000000000 x27: 0000000000000000 x26: 0000000000000004 x25: 0000000000000003 x24: ffffffc011ffb890 x23: ffffffa762ef9be0 x22: ffffffa77244ef00 x21: 0000000000000009 x20: 00000007fff7c000 x19: 0000000000000003 x18: 0000000000000000 x17: 0000000000000004 x16: ffffffd7a357d9f0 x15: 0000000000000000 x14: 00fd5d4fa7ffffff x13: 000000000000000e x12: 0000000000000000 x11: 00000000ffffffff x10: 00000000fffffe00 x9 : 000000000000017c x8 : 000000000000000c x7 : 0000000000000000 x6 : ffffffa762ef9000 x5 : 0000000000000003 x4 : 0000000000000004 x3 : 0000000000001000 x2 : 00000007fff7c000 x1 : ffffffc011ffb890 x0 : 0000000000000000 Call trace: __arm_lpae_unmap+0x500/0x514 __arm_lpae_unmap+0x4bc/0x514 __arm_lpae_unmap+0x4bc/0x514 arm_lpae_unmap_pages+0x78/0xa4 arm_smmu_unmap_pages+0x78/0x104 __iommu_unmap+0xc8/0x1e4 iommu_unmap_fast+0x38/0x48 __iommu_dma_unmap+0x84/0x104 iommu_dma_free+0x34/0x50 dma_free_attrs+0xa4/0xd0 ath10k_htt_rx_free+0xc4/0xf4 [ath10k_core] ath10k_core_stop+0x64/0x7c [ath10k_core] ath10k_halt+0x11c/0x180 [ath10k_core] ath10k_stop+0x54/0x94 [ath10k_core] drv_stop+0x48/0x1c8 [mac80211] ieee80211_do_open+0x638/0x77c [mac80211] ieee80211_open+0x48/0x5c [mac80211] __dev_open+0xb4/0x174 __dev_change_flags+0xc4/0x1dc dev_change_flags+0x3c/0x7c devinet_ioctl+0x2b4/0x580 inet_ioctl+0xb0/0x1b4 sock_do_ioctl+0x4c/0x16c compat_ifreq_ioctl+0x1cc/0x35c compat_sock_ioctl+0x110/0x2ac __arm64_compat_sys_ioctl+0xf4/0x3e0 el0_svc_common+0xb4/0x17c el0_svc_compat_handler+0x2c/0x58 el0_svc_compat+0x8/0x2c Tested-on: WCN3990 hw1.0 SNOC WLAN.HL.2.0-01387-QCAHLSWMTPLZ-1

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 an adjacent network may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.

What

In the Linux kernel, the following vulnerability has been resolved: wifi: ath10k: Delay the unmapping of the buffer On WCN3990, we are seeing a rare scenario where copy engine hardware is sending a copy complete interrupt to the host driver while still processing the buffer that the driver has sent, this is leading into an SMMU fault triggering kernel panic. This is happening on copy engine channel 3 (CE3) where the driver normally enqueues WMI commands to the firmware. Upon receiving a copy complete interrupt, host driver will immediately unmap and frees the buffer presuming that hardware has processed the buffer. In the issue case, upon receiving copy complete interrupt, host driver will unmap and free the buffer but since hardware is still accessing the buffer (which in this case got unmapped in parallel), SMMU hardware will trigger an SMMU fault resulting in a kernel panic. In order to avoid this, as a work around, add a delay before unmapping the copy engine source DMA buffer. This is conditionally done for WCN3990 and only for the CE3 channel where issue is seen. Below is the crash signature: wifi smmu error: kernel: [ 10.120965] arm-smmu 15000000.iommu: Unhandled context fault: fsr=0x402, iova=0x7fdfd8ac0, fsynr=0x500003,cbfrsynra=0xc1, cb=6 arm-smmu 15000000.iommu: Unhandled context fault:fsr=0x402, iova=0x7fe06fdc0, fsynr=0x710003, cbfrsynra=0xc1, cb=6 qcom-q6v5-mss 4080000.remoteproc: fatal error received: err_qdi.c:1040:EF:wlan_process:0x1:WLAN RT:0x2091: cmnos_thread.c:3998:Asserted in copy_engine.c:AXI_ERROR_DETECTED:2149 remoteproc remoteproc0: crash detected in 4080000.remoteproc: type fatal error <3> remoteproc remoteproc0: handling crash #1 in 4080000.remoteproc pc : __arm_lpae_unmap+0x500/0x514 lr : __arm_lpae_unmap+0x4bc/0x514 sp : ffffffc011ffb530 x29: ffffffc011ffb590 x28: 0000000000000000 x27: 0000000000000000 x26: 0000000000000004 x25: 0000000000000003 x24: ffffffc011ffb890 x23: ffffffa762ef9be0 x22: ffffffa77244ef00 x21: 0000000000000009 x20: 00000007fff7c000 x19: 0000000000000003 x18: 0000000000000000 x17: 0000000000000004 x16: ffffffd7a357d9f0 x15: 0000000000000000 x14: 00fd5d4fa7ffffff x13: 000000000000000e x12: 0000000000000000 x11: 00000000ffffffff x10: 00000000fffffe00 x9 : 000000000000017c x8 : 000000000000000c x7 : 0000000000000000 x6 : ffffffa762ef9000 x5 : 0000000000000003 x4 : 0000000000000004 x3 : 0000000000001000 x2 : 00000007fff7c000 x1 : ffffffc011ffb890 x0 : 0000000000000000 Call trace: __arm_lpae_unmap+0x500/0x514 __arm_lpae_unmap+0x4bc/0x514 __arm_lpae_unmap+0x4bc/0x514 arm_lpae_unmap_pages+0x78/0xa4 arm_smmu_unmap_pages+0x78/0x104 __iommu_unmap+0xc8/0x1e4 iommu_unmap_fast+0x38/0x48 __iommu_dma_unmap+0x84/0x104 iommu_dma_free+0x34/0x50 dma_free_attrs+0xa4/0xd0 ath10k_htt_rx_free+0xc4/0xf4 [ath10k_core] ath10k_core_stop+0x64/0x7c [ath10k_core] ath10k_halt+0x11c/0x180 [ath10k_core] ath10k_stop+0x54/0x94 [ath10k_core] drv_stop+0x48/0x1c8 [mac80211] ieee80211_do_open+0x638/0x77c [mac80211] ieee80211_open+0x48/0x5c [mac80211] __dev_open+0xb4/0x174 __dev_change_flags+0xc4/0x1dc dev_change_flags+0x3c/0x7c devinet_ioctl+0x2b4/0x580 inet_ioctl+0xb0/0x1b4 sock_do_ioctl+0x4c/0x16c compat_ifreq_ioctl+0x1cc/0x35c compat_sock_ioctl+0x110/0x2ac __arm64_compat_sys_ioctl+0xf4/0x3e0 el0_svc_common+0xb4/0x17c el0_svc_compat_handler+0x2c/0x58 el0_svc_compat+0x8/0x2c Tested-on: WCN3990 hw1.0 SNOC WLAN.HL.2.0-01387-QCAHLSWMTPLZ-1

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 an adjacent network may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.

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
an adjacent network → vulnerable operation → disrupt the affected service
Attack surface
Adjacent
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
High: exploitation depends on specific conditions
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:A/AC:H/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.

AVAdjacentAttack vector: The attacker must be on an adjacent or logically close network.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.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.
UnauthenticatedDenial of service
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-2920Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.

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

d?id=CVE-2022-50551 Référence CVE CVE-2022-50552 https://www.cve.org/CVERecord?id=CVE-2022-50552 Référence CVE CVE-2022-50554 https://www.cve.org/CVERecord?id=CVE-2022-50554 Référence CVE CVE-2022-50571 https://www.cve.org/CVERecord?id=CVE-2022-50571 Référence CVE CVE-2022-50583 https://www.cve.org/CVERecord?id=CVE-2022-50583 Référence CVE CVE-2022-50616 https://www.cve.org/CVERecord?id=CVE-2022-50616 Référence CVE CVE-2022-50627 https://www.cve.org/CVERecord?id=CVE-2022-50627 Référence CVE CVE-2022-50628 https://www.cve.org/CVERecord?id=CVE-2022-50628 Référence CVE CVE-2022-50634 https://www.cve.org/CVERecord?id=CVE-2022-50634 Référence CVE CVE-2022-50700 https://www.cve.org/CVERecord?id=CVE-2022-50700 Référence CVE CVE-2022-50704 https://www.cve.org/CVERecord?id=CVE-2022-50704 Référence CVE CVE-2022-50708 https://www.cve.org/CVERecord?id=CVE-2022-50708 Référence CVE CVE-2022-50720 https://www.cve.org/CVERecord?id=CVE-2022-50720 Référence CVE CVE-2022-50721 https://www.cve.org/CVERecord?id=CVE-2022-50721 Référence CVE CVE-2022-50746 https://www.cve.org/CVERecord?id=CVE-2022-50746 Référence CVE CVE-2022-50748 https://www.cve.org/CVERecord?id=CVE-2022-50748 Référence CVE CVE-2022-50759 https://www.cve.org/CVERecord?id=CVE-2022-50759 Référence CVE CVE-2022-50772 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2022-50551 Référence CVE CVE-2022-50552 https://www.cve.org/CVERecord?id=CVE-2022-50552 Référence CVE CVE-2022-50554 https://www.cve.org/CVERecord?id=CVE-2022-50554 Référence CVE CVE-2022-50571 https://www.cve.org/CVERecord?id=CVE-2022-50571 Référence CVE CVE-2022-50583 https://www.cve.org/CVERecord?id=CVE-2022-50583 Référence CVE CVE-2022-50616 https://www.cve.org/CVERecord?id=CVE-2022-50616 Référence CVE CVE-2022-50627 https://www.cve.org/CVERecord?id=CVE-2022-50627 Référence CVE CVE-2022-50628 https://www.cve.org/CVERecord?id=CVE-2022-50628 Référence CVE CVE-2022-50634 https://www.cve.org/CVERecord?id=CVE-2022-50634 Référence CVE CVE-2022-50700 https://www.cve.org/CVERecord?id=CVE-2022-50700 Référence CVE CVE-2022-50704 https://www.cve.org/CVERecord?id=CVE-2022-50704 Référence CVE CVE-2022-50708 https://www.cve.org/CVERecord?id=CVE-2022-50708 Référence CVE CVE-2022-50720 https://www.cve.org/CVERecord?id=CVE-2022-50720 Référence CVE CVE-2022-50721 https://www.cve.org/CVERecord?id=CVE-2022-50721 Référence CVE CVE-2022-50746 https://www.cve.org/CVERecord?id=CVE-2022-50746 Référence CVE CVE-2022-50748 https://www.cve.org/CVERecord?id=CVE-2022-50748 Référence CVE CVE-2022-50759 https://www.cve.org/CVERecord?id=CVE-2022-50759 Référence CVE CVE-2022-50772 https://www.cve.org/CVERecord?id=

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

026 https://www.suse.com/support/update/announcement/2026/suse-su-20260736-1 Bulletin de sécurité SUSE SUSE-SU-2026:0745-1 du 02 mars 2026 https://www.suse.com/support/update/announcement/2026/suse-su-20260745-1 Bulletin de sécurité SUSE SUSE-SU-2026:0748-1 du 02 mars 2026 https://www.suse.com/support/update/announcement/2026/suse-su-20260748-1 Bulletin de sécurité SUSE SUSE-SU-2026:20558-1 du 02 mars 2026 https://www.suse.com/support/update/announcement/2026/suse-su-202620558-1 Référence CVE CVE-2021-0920 https://www.cve.org/CVERecord?id=CVE-2021-0920 Référence CVE CVE-2022-50253 https://www.cve.org/CVERecord?id=CVE-2022-50253 Référence CVE CVE-2022-50700 https://www.cve.org/CVERecord?id=CVE-2022-50700 Référence CVE CVE-2022-50717 https://www.cve.org/CVERecord?id=CVE-2022-50717 Référence CVE CVE-2023-42752 https://www.cve.org/CVERecord?id=CVE-2023-42752 Référence CVE CVE-2023-53676 https://www.cve.org/CVERecord?id=CVE-2023-53676 Référence CVE CVE-2023-53714 https://www.cve.org/CVERecord?id=CVE-2023-53714 Référence CVE CVE-2023-53743 https://www.cve.org/CVERecord?id=CVE-2023-53743 Référence CVE CVE-2023-53750 https://www.cve.org/CVERecord?id=CVE-2023-53750 Référence CVE CVE-2023-53752 https://www.cve.org/CVERecord?id=CVE-2023-53752 Référence CVE CVE-2023-53759 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2022-50672 Référence CVE CVE-2022-50673 https://www.cve.org/CVERecord?id=CVE-2022-50673 Référence CVE CVE-2022-50675 https://www.cve.org/CVERecord?id=CVE-2022-50675 Référence CVE CVE-2022-50677 https://www.cve.org/CVERecord?id=CVE-2022-50677 Référence CVE CVE-2022-50678 https://www.cve.org/CVERecord?id=CVE-2022-50678 Référence CVE CVE-2022-50679 https://www.cve.org/CVERecord?id=CVE-2022-50679 Référence CVE CVE-2022-50697 https://www.cve.org/CVERecord?id=CVE-2022-50697 Référence CVE CVE-2022-50698 https://www.cve.org/CVERecord?id=CVE-2022-50698 Référence CVE CVE-2022-50699 https://www.cve.org/CVERecord?id=CVE-2022-50699 Référence CVE CVE-2022-50700 https://www.cve.org/CVERecord?id=CVE-2022-50700 Référence CVE CVE-2022-50702 https://www.cve.org/CVERecord?id=CVE-2022-50702 Référence CVE CVE-2022-50703 https://www.cve.org/CVERecord?id=CVE-2022-50703 Référence CVE CVE-2022-50704 https://www.cve.org/CVERecord?id=CVE-2022-50704 Référence CVE CVE-2022-50709 https://www.cve.org/CVERecord?id=CVE-2022-50709 Référence CVE CVE-2022-50715 https://www.cve.org/CVERecord?id=CVE-2022-50715 Référence CVE CVE-2022-50716 https://www.cve.org/CVERecord?id=CVE-2022-50716 Référence CVE CVE-2022-50717 https://www.cve.org/CVERecord?id=CVE-2022-50717 Référence CVE CVE-2022-50718 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2022-50673 Référence CVE CVE-2022-50675 https://www.cve.org/CVERecord?id=CVE-2022-50675 Référence CVE CVE-2022-50676 https://www.cve.org/CVERecord?id=CVE-2022-50676 Référence CVE CVE-2022-50677 https://www.cve.org/CVERecord?id=CVE-2022-50677 Référence CVE CVE-2022-50678 https://www.cve.org/CVERecord?id=CVE-2022-50678 Référence CVE CVE-2022-50679 https://www.cve.org/CVERecord?id=CVE-2022-50679 Référence CVE CVE-2022-50697 https://www.cve.org/CVERecord?id=CVE-2022-50697 Référence CVE CVE-2022-50698 https://www.cve.org/CVERecord?id=CVE-2022-50698 Référence CVE CVE-2022-50699 https://www.cve.org/CVERecord?id=CVE-2022-50699 Référence CVE CVE-2022-50700 https://www.cve.org/CVERecord?id=CVE-2022-50700 Référence CVE CVE-2022-50702 https://www.cve.org/CVERecord?id=CVE-2022-50702 Référence CVE CVE-2022-50703 https://www.cve.org/CVERecord?id=CVE-2022-50703 Référence CVE CVE-2022-50704 https://www.cve.org/CVERecord?id=CVE-2022-50704 Référence CVE CVE-2022-50709 https://www.cve.org/CVERecord?id=CVE-2022-50709 Référence CVE CVE-2022-50715 https://www.cve.org/CVERecord?id=CVE-2022-50715 Référence CVE CVE-2022-50716 https://www.cve.org/CVERecord?id=CVE-2022-50716 Référence CVE CVE-2022-50717 https://www.cve.org/CVERecord?id=CVE-2022-50717 Référence CVE CVE-2022-50718 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2022-50635 Référence CVE CVE-2022-50640 https://www.cve.org/CVERecord?id=CVE-2022-50640 Référence CVE CVE-2022-50641 https://www.cve.org/CVERecord?id=CVE-2022-50641 Référence CVE CVE-2022-50644 https://www.cve.org/CVERecord?id=CVE-2022-50644 Référence CVE CVE-2022-50646 https://www.cve.org/CVERecord?id=CVE-2022-50646 Référence CVE CVE-2022-50649 https://www.cve.org/CVERecord?id=CVE-2022-50649 Référence CVE CVE-2022-50668 https://www.cve.org/CVERecord?id=CVE-2022-50668 Référence CVE CVE-2022-50671 https://www.cve.org/CVERecord?id=CVE-2022-50671 Référence CVE CVE-2022-50678 https://www.cve.org/CVERecord?id=CVE-2022-50678 Référence CVE CVE-2022-50700 https://www.cve.org/CVERecord?id=CVE-2022-50700 Référence CVE CVE-2022-50703 https://www.cve.org/CVERecord?id=CVE-2022-50703 Référence CVE CVE-2022-50709 https://www.cve.org/CVERecord?id=CVE-2022-50709 Référence CVE CVE-2022-50717 https://www.cve.org/CVERecord?id=CVE-2022-50717 Référence CVE CVE-2022-50726 https://www.cve.org/CVERecord?id=CVE-2022-50726 Référence CVE CVE-2022-50730 https://www.cve.org/CVERecord?id=CVE-2022-50730 Référence CVE CVE-2022-50731 https://www.cve.org/CVERecord?id=CVE-2022-50731 Référence CVE CVE-2022-50733 https://www.cve.org/CVERecord?id=CVE-2022-50733 Référence CVE CVE-2022-50736 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2022-50671 Référence CVE CVE-2022-50672 https://www.cve.org/CVERecord?id=CVE-2022-50672 Référence CVE CVE-2022-50673 https://www.cve.org/CVERecord?id=CVE-2022-50673 Référence CVE CVE-2022-50675 https://www.cve.org/CVERecord?id=CVE-2022-50675 Référence CVE CVE-2022-50677 https://www.cve.org/CVERecord?id=CVE-2022-50677 Référence CVE CVE-2022-50678 https://www.cve.org/CVERecord?id=CVE-2022-50678 Référence CVE CVE-2022-50679 https://www.cve.org/CVERecord?id=CVE-2022-50679 Référence CVE CVE-2022-50698 https://www.cve.org/CVERecord?id=CVE-2022-50698 Référence CVE CVE-2022-50699 https://www.cve.org/CVERecord?id=CVE-2022-50699 Référence CVE CVE-2022-50700 https://www.cve.org/CVERecord?id=CVE-2022-50700 Référence CVE CVE-2022-50701 https://www.cve.org/CVERecord?id=CVE-2022-50701 Référence CVE CVE-2022-50702 https://www.cve.org/CVERecord?id=CVE-2022-50702 Référence CVE CVE-2022-50703 https://www.cve.org/CVERecord?id=CVE-2022-50703 Référence CVE CVE-2022-50704 https://www.cve.org/CVERecord?id=CVE-2022-50704 Référence CVE CVE-2022-50705 https://www.cve.org/CVERecord?id=CVE-2022-50705 Référence CVE CVE-2022-50706 https://www.cve.org/CVERecord?id=CVE-2022-50706 Référence CVE CVE-2022-50709 https://www.cve.org/CVERecord?id=CVE-2022-50709 Référence CVE CVE-2022-50710 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
d390509bdf501c9c8c6e61248e4bc9314c86d854 < c4bedc3cda09d896c92adcdb6b62aa93b0c47a8a; d390509bdf501c9c8c6e61248e4bc9314c86d854 < 79a124b588aadb5a22695542778de14366ff3219; d390509bdf501c9c8c6e61248e4bc9314c86d854 < acd4324e5f1f11351630234297f95076f0ac9a2f; 4.18
Fixed
< 4.18; 6.0.16 ≤ 6.0.*; 6.1.2 ≤ 6.1.*; 6.2 ≤ *
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 24 Dec 2025 · Last source change 5 Aug 2026, 08:59 UTC · CWE not yet assigned

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-2025-205178
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceUnavailable
NVD statusNVD not scheduled

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 →

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-2025-205178↗CVE authority or vendor 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-50700 · cve.blacktree.nl