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

RDMA/rxe: Fix the warning "__rxe_cleanup+0x12c/0x170 [rdma_rxe]"

Linux · Linux

9.8CriticalCVSS 3.1
Recommended action
Within 72 hours

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

Patch available
Distribution package intelligence

Ubuntu vendor package status

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

19 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 archivelinuxAffected, 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-awsAffected, 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-azureAffected, 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-azure-nvidiaAffected, 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-gcpAffected, 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-gkeAffected, 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-gkeopAffected, 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-ibmAffected, 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-lowlatencyAffected, 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-nvidiaAffected, 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-lowlatencyAffected, 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-tegraAffected, 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-oracleAffected, 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-raspiAffected, 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
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, 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-6216

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 72 hours

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

Patch available
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Fix the warning "__rxe_cleanup+0x12c/0x170 [rdma_rxe]" The Call Trace is as below: " <TASK> ? show_regs.cold+0x1a/0x1f ? __rxe_cleanup+0x12c/0x170 [rdma_rxe] ? __warn+0x84/0xd0 ? __rxe_cleanup+0x12c/0x170 [rdma_rxe] ? report_bug+0x105/0x180 ? handle_bug+0x46/0x80 ? exc_invalid_op+0x19/0x70 ? asm_exc_invalid_op+0x1b/0x20 ? __rxe_cleanup+0x12c/0x170 [rdma_rxe] ? __rxe_cleanup+0x124/0x170 [rdma_rxe] rxe_destroy_qp.cold+0x24/0x29 [rdma_rxe] ib_destroy_qp_user+0x118/0x190 [ib_core] rdma_destroy_qp.cold+0x43/0x5e [rdma_cm] rtrs_cq_qp_destroy.cold+0x1d/0x2b [rtrs_core] rtrs_srv_close_work.cold+0x1b/0x31 [rtrs_server] process_one_work+0x21d/0x3f0 worker_thread+0x4a/0x3c0 ? process_one_work+0x3f0/0x3f0 kthread+0xf0/0x120 ? kthread_complete_and_exit+0x20/0x20 ret_from_fork+0x22/0x30 </TASK> " When too many rdma resources are allocated, rxe needs more time to handle these rdma resources. Sometimes with the current timeout, rxe can not release the rdma resources correctly. Compared with other rdma drivers, a bigger timeout is used.

What

In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Fix the warning "__rxe_cleanup+0x12c/0x170 [rdma_rxe]" The Call Trace is as below: " <TASK> ? show_regs.cold+0x1a/0x1f ? __rxe_cleanup+0x12c/0x170 [rdma_rxe] ? __warn+0x84/0xd0 ? __rxe_cleanup+0x12c/0x170 [rdma_rxe] ? report_bug+0x105/0x180 ? handle_bug+0x46/0x80 ? exc_invalid_op+0x19/0x70 ? asm_exc_invalid_op+0x1b/0x20 ? __rxe_cleanup+0x12c/0x170 [rdma_rxe] ? __rxe_cleanup+0x124/0x170 [rdma_rxe] rxe_destroy_qp.cold+0x24/0x29 [rdma_rxe] ib_destroy_qp_user+0x118/0x190 [ib_core] rdma_destroy_qp.cold+0x43/0x5e [rdma_cm] rtrs_cq_qp_destroy.cold+0x1d/0x2b [rtrs_core] rtrs_srv_close_work.cold+0x1b/0x31 [rtrs_server] process_one_work+0x21d/0x3f0 worker_thread+0x4a/0x3c0 ? process_one_work+0x3f0/0x3f0 kthread+0xf0/0x120 ? kthread_complete_and_exit+0x20/0x20 ret_from_fork+0x22/0x30 </TASK> " When too many rdma resources are allocated, rxe needs more time to handle these rdma resources. Sometimes with the current timeout, rxe can not release the rdma resources correctly. Compared with other rdma drivers, a bigger timeout is used.

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 a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Fix the warning "__rxe_cleanup+0x12c/0x170 [rdma_rxe]" The Call Trace is as below: " <TASK> ? show_regs.cold+0x1a/0x1f ? __rxe_cleanup+0x12c/0x170 [rdma_rxe] ? __warn+0x84/0xd0 ? __rxe_cleanup+0x12c/0x170 [rdma_rxe] ? report_bug+0x105/0x180 ? handle_bug+0x46/0x80 ? exc_invalid_op+0x19/0x70 ? asm_exc_invalid_op+0x1b/0x20 ? __rxe_cleanup+0x12c/0x170 [rdma_rxe] ? __rxe_cleanup+0x124/0x170 [rdma_rxe] rxe_destroy_qp.cold+0x24/0x29 [rdma_rxe] ib_destroy_qp_user+0x118/0x190 [ib_core] rdma_destroy_qp.cold+0x43/0x5e [rdma_cm] rtrs_cq_qp_destroy.cold+0x1d/0x2b [rtrs_core] rtrs_srv_close_work.cold+0x1b/0x31 [rtrs_server] process_one_work+0x21d/0x3f0 worker_thread+0x4a/0x3c0 ? process_one_work+0x3f0/0x3f0 kthread+0xf0/0x120 ? kthread_complete_and_exit+0x20/0x20 ret_from_fork+0x22/0x30 </TASK> " When too many rdma resources are allocated, rxe needs more time to handle these rdma resources. Sometimes with the current timeout, rxe can not release the rdma resources correctly. Compared with other rdma drivers, a bigger timeout is used.

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 a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration.
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:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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

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

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-W-2026-2253IBM Security Verify Access: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM Security Verify Access ausnutzen, um erweiterte Berechtigungen zu erlangen, beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren, sensible Informationen offenzulegen und andere, nicht näher bezeichnete Angriffe durchzuführen.

Official advisory
BSI · German · WID-SEC-W-2025-0499Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht spezifizierte Auswirkungen zu erzeugen oder einen Denial-of-Service-Zustand zu verursachen.

Official advisory
BSI · German · WID-SEC-W-2025-1439Dell Secure Connect Gateway: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff

Ein Angreifer kann mehrere Schwachstellen in Dell Secure Connect Gateway ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.

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

d?id=CVE-2025-21795 Référence CVE CVE-2025-21807 https://www.cve.org/CVERecord?id=CVE-2025-21807 Référence CVE CVE-2025-21808 https://www.cve.org/CVERecord?id=CVE-2025-21808 Référence CVE CVE-2025-21809 https://www.cve.org/CVERecord?id=CVE-2025-21809 Référence CVE CVE-2025-21810 https://www.cve.org/CVERecord?id=CVE-2025-21810 Référence CVE CVE-2025-21817 https://www.cve.org/CVERecord?id=CVE-2025-21817 Référence CVE CVE-2025-21825 https://www.cve.org/CVERecord?id=CVE-2025-21825 Référence CVE CVE-2025-21827 https://www.cve.org/CVERecord?id=CVE-2025-21827 Référence CVE CVE-2025-21828 https://www.cve.org/CVERecord?id=CVE-2025-21828 Référence CVE CVE-2025-21829 https://www.cve.org/CVERecord?id=CVE-2025-21829 Référence CVE CVE-2025-21830 https://www.cve.org/CVERecord?id=CVE-2025-21830 Référence CVE CVE-2025-21832 https://www.cve.org/CVERecord?id=CVE-2025-21832 Référence CVE CVE-2025-21836 https://www.cve.org/CVERecord?id=CVE-2025-21836 Référence CVE CVE-2025-21844 https://www.cve.org/CVERecord?id=CVE-2025-21844 Référence CVE CVE-2025-21847 https://www.cve.org/CVERecord?id=CVE-2025-21847 Référence CVE CVE-2025-21851 https://www.cve.org/CVERecord?id=CVE-2025-21851 Référence CVE CVE-2025-21854 https://www.cve.org/CVERecord?id=CVE-2025-21854 Référence CVE CVE-2025-21856 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-21814 Référence CVE CVE-2025-21815 https://www.cve.org/CVERecord?id=CVE-2025-21815 Référence CVE CVE-2025-21816 https://www.cve.org/CVERecord?id=CVE-2025-21816 Référence CVE CVE-2025-21820 https://www.cve.org/CVERecord?id=CVE-2025-21820 Référence CVE CVE-2025-21821 https://www.cve.org/CVERecord?id=CVE-2025-21821 Référence CVE CVE-2025-21823 https://www.cve.org/CVERecord?id=CVE-2025-21823 Référence CVE CVE-2025-21825 https://www.cve.org/CVERecord?id=CVE-2025-21825 Référence CVE CVE-2025-21826 https://www.cve.org/CVERecord?id=CVE-2025-21826 Référence CVE CVE-2025-21828 https://www.cve.org/CVERecord?id=CVE-2025-21828 Référence CVE CVE-2025-21829 https://www.cve.org/CVERecord?id=CVE-2025-21829 Référence CVE CVE-2025-21830 https://www.cve.org/CVERecord?id=CVE-2025-21830 Référence CVE CVE-2025-21832 https://www.cve.org/CVERecord?id=CVE-2025-21832 Référence CVE CVE-2025-21835 https://www.cve.org/CVERecord?id=CVE-2025-21835 Référence CVE CVE-2025-21836 https://www.cve.org/CVERecord?id=CVE-2025-21836 Référence CVE CVE-2025-21838 https://www.cve.org/CVERecord?id=CVE-2025-21838 Référence CVE CVE-2025-21839 https://www.cve.org/CVERecord?id=CVE-2025-21839 Référence CVE CVE-2025-21844 https://www.cve.org/CVERecord?id=CVE-2025-21844 Référence CVE CVE-2025-21846 https://www.cve.org/CVERecord?id=

Official advisory
CERT-FR · French · CERTFR-2025-AVI-0758Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2025-21814 Référence CVE CVE-2025-21815 https://www.cve.org/CVERecord?id=CVE-2025-21815 Référence CVE CVE-2025-21816 https://www.cve.org/CVERecord?id=CVE-2025-21816 Référence CVE CVE-2025-21820 https://www.cve.org/CVERecord?id=CVE-2025-21820 Référence CVE CVE-2025-21821 https://www.cve.org/CVERecord?id=CVE-2025-21821 Référence CVE CVE-2025-21823 https://www.cve.org/CVERecord?id=CVE-2025-21823 Référence CVE CVE-2025-21825 https://www.cve.org/CVERecord?id=CVE-2025-21825 Référence CVE CVE-2025-21826 https://www.cve.org/CVERecord?id=CVE-2025-21826 Référence CVE CVE-2025-21828 https://www.cve.org/CVERecord?id=CVE-2025-21828 Référence CVE CVE-2025-21829 https://www.cve.org/CVERecord?id=CVE-2025-21829 Référence CVE CVE-2025-21830 https://www.cve.org/CVERecord?id=CVE-2025-21830 Référence CVE CVE-2025-21832 https://www.cve.org/CVERecord?id=CVE-2025-21832 Référence CVE CVE-2025-21835 https://www.cve.org/CVERecord?id=CVE-2025-21835 Référence CVE CVE-2025-21836 https://www.cve.org/CVERecord?id=CVE-2025-21836 Référence CVE CVE-2025-21838 https://www.cve.org/CVERecord?id=CVE-2025-21838 Référence CVE CVE-2025-21839 https://www.cve.org/CVERecord?id=CVE-2025-21839 Référence CVE CVE-2025-21844 https://www.cve.org/CVERecord?id=CVE-2025-21844 Référence CVE CVE-2025-21846 https://www.cve.org/CVERecord?id=

Official advisory
CERT-FR · French · CERTFR-2025-AVI-0625Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2025-21811 Référence CVE CVE-2025-21812 https://www.cve.org/CVERecord?id=CVE-2025-21812 Référence CVE CVE-2025-21814 https://www.cve.org/CVERecord?id=CVE-2025-21814 Référence CVE CVE-2025-21815 https://www.cve.org/CVERecord?id=CVE-2025-21815 Référence CVE CVE-2025-21816 https://www.cve.org/CVERecord?id=CVE-2025-21816 Référence CVE CVE-2025-21820 https://www.cve.org/CVERecord?id=CVE-2025-21820 Référence CVE CVE-2025-21825 https://www.cve.org/CVERecord?id=CVE-2025-21825 Référence CVE CVE-2025-21826 https://www.cve.org/CVERecord?id=CVE-2025-21826 Référence CVE CVE-2025-21828 https://www.cve.org/CVERecord?id=CVE-2025-21828 Référence CVE CVE-2025-21829 https://www.cve.org/CVERecord?id=CVE-2025-21829 Référence CVE CVE-2025-21830 https://www.cve.org/CVERecord?id=CVE-2025-21830 Référence CVE CVE-2025-21832 https://www.cve.org/CVERecord?id=CVE-2025-21832 Référence CVE CVE-2025-21839 https://www.cve.org/CVERecord?id=CVE-2025-21839 Référence CVE CVE-2025-21853 https://www.cve.org/CVERecord?id=CVE-2025-21853 Référence CVE CVE-2025-21941 https://www.cve.org/CVERecord?id=CVE-2025-21941 Référence CVE CVE-2025-21956 https://www.cve.org/CVERecord?id=CVE-2025-21956 Référence CVE CVE-2025-21957 https://www.cve.org/CVERecord?id=CVE-2025-21957 Référence CVE CVE-2025-21959 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-21812 Référence CVE CVE-2025-21814 https://www.cve.org/CVERecord?id=CVE-2025-21814 Référence CVE CVE-2025-21815 https://www.cve.org/CVERecord?id=CVE-2025-21815 Référence CVE CVE-2025-21819 https://www.cve.org/CVERecord?id=CVE-2025-21819 Référence CVE CVE-2025-21820 https://www.cve.org/CVERecord?id=CVE-2025-21820 Référence CVE CVE-2025-21821 https://www.cve.org/CVERecord?id=CVE-2025-21821 Référence CVE CVE-2025-21823 https://www.cve.org/CVERecord?id=CVE-2025-21823 Référence CVE CVE-2025-21825 https://www.cve.org/CVERecord?id=CVE-2025-21825 Référence CVE CVE-2025-21828 https://www.cve.org/CVERecord?id=CVE-2025-21828 Référence CVE CVE-2025-21829 https://www.cve.org/CVERecord?id=CVE-2025-21829 Référence CVE CVE-2025-21830 https://www.cve.org/CVERecord?id=CVE-2025-21830 Référence CVE CVE-2025-21831 https://www.cve.org/CVERecord?id=CVE-2025-21831 Référence CVE CVE-2025-21832 https://www.cve.org/CVERecord?id=CVE-2025-21832 Référence CVE CVE-2025-21833 https://www.cve.org/CVERecord?id=CVE-2025-21833 Référence CVE CVE-2025-21835 https://www.cve.org/CVERecord?id=CVE-2025-21835 Référence CVE CVE-2025-21836 https://www.cve.org/CVERecord?id=CVE-2025-21836 Référence CVE CVE-2025-21838 https://www.cve.org/CVERecord?id=CVE-2025-21838 Référence CVE CVE-2025-21844 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-21804 Référence CVE CVE-2025-21810 https://www.cve.org/CVERecord?id=CVE-2025-21810 Référence CVE CVE-2025-21815 https://www.cve.org/CVERecord?id=CVE-2025-21815 Référence CVE CVE-2025-21819 https://www.cve.org/CVERecord?id=CVE-2025-21819 Référence CVE CVE-2025-21820 https://www.cve.org/CVERecord?id=CVE-2025-21820 Référence CVE CVE-2025-21821 https://www.cve.org/CVERecord?id=CVE-2025-21821 Référence CVE CVE-2025-21823 https://www.cve.org/CVERecord?id=CVE-2025-21823 Référence CVE CVE-2025-21825 https://www.cve.org/CVERecord?id=CVE-2025-21825 Référence CVE CVE-2025-21828 https://www.cve.org/CVERecord?id=CVE-2025-21828 Référence CVE CVE-2025-21829 https://www.cve.org/CVERecord?id=CVE-2025-21829 Référence CVE CVE-2025-21830 https://www.cve.org/CVERecord?id=CVE-2025-21830 Référence CVE CVE-2025-21831 https://www.cve.org/CVERecord?id=CVE-2025-21831 Référence CVE CVE-2025-21832 https://www.cve.org/CVERecord?id=CVE-2025-21832 Référence CVE CVE-2025-21835 https://www.cve.org/CVERecord?id=CVE-2025-21835 Référence CVE CVE-2025-21838 https://www.cve.org/CVERecord?id=CVE-2025-21838 Référence CVE CVE-2025-21839 https://www.cve.org/CVERecord?id=CVE-2025-21839 Référence CVE CVE-2025-21844 https://www.cve.org/CVERecord?id=CVE-2025-21844 Référence CVE CVE-2025-21846 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-21806 Référence CVE CVE-2025-21811 https://www.cve.org/CVERecord?id=CVE-2025-21811 Référence CVE CVE-2025-21812 https://www.cve.org/CVERecord?id=CVE-2025-21812 Référence CVE CVE-2025-21814 https://www.cve.org/CVERecord?id=CVE-2025-21814 Référence CVE CVE-2025-21819 https://www.cve.org/CVERecord?id=CVE-2025-21819 Référence CVE CVE-2025-21820 https://www.cve.org/CVERecord?id=CVE-2025-21820 Référence CVE CVE-2025-21821 https://www.cve.org/CVERecord?id=CVE-2025-21821 Référence CVE CVE-2025-21823 https://www.cve.org/CVERecord?id=CVE-2025-21823 Référence CVE CVE-2025-21826 https://www.cve.org/CVERecord?id=CVE-2025-21826 Référence CVE CVE-2025-21829 https://www.cve.org/CVERecord?id=CVE-2025-21829 Référence CVE CVE-2025-21830 https://www.cve.org/CVERecord?id=CVE-2025-21830 Référence CVE CVE-2025-21832 https://www.cve.org/CVERecord?id=CVE-2025-21832 Référence CVE CVE-2025-21835 https://www.cve.org/CVERecord?id=CVE-2025-21835 Gestion détaillée du document le 04 avril 2025 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la Défense et de la Sécurité Nationale / Agence nationale de la sécurité des s

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
215d0a755e1bcd92cbe6a71a21194ce7c82ec106 < 720653309dd31c8a927ef5d87964578ad544980f; 215d0a755e1bcd92cbe6a71a21194ce7c82ec106 < 45e567800492088bc52c9abac35524b4d332a8f8; 215d0a755e1bcd92cbe6a71a21194ce7c82ec106 < 7a2de8126ed3801f2396720e10a03cd546a3cea1; 215d0a755e1bcd92cbe6a71a21194ce7c82ec106 < a7d15eaecf0d6e13226db629ae2401c8c02683e5; 215d0a755e1bcd92cbe6a71a21194ce7c82ec106 < edc4ef0e0154096d6c0cf5e06af6fc330dbad9d1; 6.0
Fixed
< 6.0; 6.1.129 ≤ 6.1.*; 6.6.76 ≤ 6.6.*; 6.12.13 ≤ 6.12.*; 6.13.2 ≤ 6.13.*; 6.14 ≤ *
Action
Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 6 Mar 2025 · Last source change 5 Aug 2026, 11:54 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-6216
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 →

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
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-2025-21829 · cve.blacktree.nl