BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2025-38024High confidence

RDMA/rxe: Fix slab-use-after-free Read in rxe_queue_cleanup bug

Linux · Linux

7.8HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 21 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Medium, lowered one band.downgradedsince 5 Aug 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.22% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 21 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

25 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 21 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

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.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.30-1Debian Security Tracker ↗Source updated 7 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.140-1Debian Security Tracker ↗Source updated 7 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.30-1Debian Security Tracker ↗Source updated 7 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.30-1Debian Security Tracker ↗Source updated 7 Oct 2026
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 Ubuntu Security ↗Source updated 6 Oct 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 Ubuntu Security ↗Source updated 6 Oct 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 Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-fdeAffected, 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 Ubuntu Security ↗Source updated 6 Oct 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 Ubuntu Security ↗Source updated 6 Oct 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 Ubuntu Security ↗Source updated 6 Oct 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 Ubuntu Security ↗Source updated 6 Oct 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 Ubuntu Security ↗Source updated 6 Oct 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 Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-intelAffected, 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 Ubuntu Security ↗Source updated 6 Oct 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 Ubuntu Security ↗Source updated 6 Oct 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 Ubuntu Security ↗Source updated 6 Oct 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 Ubuntu Security ↗Source updated 6 Oct 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 Ubuntu Security ↗Source updated 6 Oct 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 Ubuntu Security ↗Source updated 6 Oct 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 Ubuntu Security ↗Source updated 6 Oct 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 Ubuntu Security ↗Source updated 6 Oct 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 Ubuntu Security ↗Source updated 6 Oct 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 Ubuntu Security ↗Source updated 6 Oct 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 Ubuntu Security ↗Source updated 6 Oct 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 Ubuntu Security ↗Source updated 6 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2025-38024 · CSAF 2.0 · revision 46 · interimSUSE Product Security TeamCVE-2025-38024
324 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • kernel-default as component of SLES-LTSS-TERADATA 15 SP2
  • kernel-source as component of SLES-LTSS-TERADATA 15 SP2
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
Summary
In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Fix slab-use-after-free Read in rxe_queue_cleanup bug Call Trace: __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x7d/0xa0 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:378 [inline] print_report+0xcf/0x610 mm/kasan/report.c:489 kasan_report+0xb5/0xe0 mm/kasan/report.c:602 rxe_queue_cleanup+0xd0/0xe0 drivers/infiniband/sw/rxe/rxe_queue.c:195 rxe_cq_cleanup+0x3f/0x50 drivers/infiniband/sw/rxe/rxe_cq.c:132 __rxe_cleanup+0x168/0x300 drivers/infiniband/sw/rxe/rxe_pool.c:232 rxe_create_cq+0x22e/0x3a0 drivers/infiniband/sw/rxe/rxe_verbs.c:1109 create_cq+0x658/0xb90 drivers/infiniband/core/uverbs_cmd.c:1052 ib_uverbs_create_cq+0xc7/0x120 drivers/infiniband/core/uverbs_cmd.c:1095 ib_uverbs_write+0x969/0xc90 drivers/infiniband/core/uverbs_main.c:679 vfs_write fs/read_write.c:677 [inline] vfs_write+0x26a/0xcc0 fs/read_write.c:659 ksys_write+0x1b8/0x200 fs/read_write.c:731 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xaa/0x1b0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f In the function rxe_create_cq, when rxe_cq_from_init fails, the function rxe_cleanup will be called to handle the allocated resources. In fact, some memory resources have already been freed in the function rxe_cq_from_init. Thus, this problem will occur. The solution is to let rxe_cleanup do all the work.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

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

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 actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 21 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Fix slab-use-after-free Read in rxe_queue_cleanup bug Call Trace: <TASK> __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x7d/0xa0 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:378 [inline] print_report+0xcf/0x610 mm/kasan/report.c:489 kasan_report+0xb5/0xe0 mm/kasan/report.c:602 rxe_queue_cleanup+0xd0/0xe0 drivers/infiniband/sw/rxe/rxe_queue.c:195 rxe_cq_cleanup+0x3f/0x50 drivers/infiniband/sw/rxe/rxe_cq.c:132 __rxe_cleanup+0x168/0x300 drivers/infiniband/sw/rxe/rxe_pool.c:232 rxe_create_cq+0x22e/0x3a0 drivers/infiniband/sw/rxe/rxe_verbs.c:1109 create_cq+0x658/0xb90 drivers/infiniband/core/uverbs_cmd.c:1052 ib_uverbs_create_cq+0xc7/0x120 drivers/infiniband/core/uverbs_cmd.c:1095 ib_uverbs_write+0x969/0xc90 drivers/infiniband/core/uverbs_main.c:679 vfs_write fs/read_write.c:677 [inline] vfs_write+0x26a/0xcc0 fs/read_write.c:659 ksys_write+0x1b8/0x200 fs/read_write.c:731 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xaa/0x1b0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f In the function rxe_create_cq, when rxe_cq_from_init fails, the function rxe_cleanup will be called to handle the allocated resources. In fact, some memory resources have already been freed in the function rxe_cq_from_init. Thus, this problem will occur. The solution is to let rxe_cleanup do all the work.

What

In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Fix slab-use-after-free Read in rxe_queue_cleanup bug Call Trace: <TASK> __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x7d/0xa0 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:378 [inline] print_report+0xcf/0x610 mm/kasan/report.c:489 kasan_report+0xb5/0xe0 mm/kasan/report.c:602 rxe_queue_cleanup+0xd0/0xe0 drivers/infiniband/sw/rxe/rxe_queue.c:195 rxe_cq_cleanup+0x3f/0x50 drivers/infiniband/sw/rxe/rxe_cq.c:132 __rxe_cleanup+0x168/0x300 drivers/infiniband/sw/rxe/rxe_pool.c:232 rxe_create_cq+0x22e/0x3a0 drivers/infiniband/sw/rxe/rxe_verbs.c:1109 create_cq+0x658/0xb90 drivers/infiniband/core/uverbs_cmd.c:1052 ib_uverbs_create_cq+0xc7/0x120 drivers/infiniband/core/uverbs_cmd.c:1095 ib_uverbs_write+0x969/0xc90 drivers/infiniband/core/uverbs_main.c:679 vfs_write fs/read_write.c:677 [inline] vfs_write+0x26a/0xcc0 fs/read_write.c:659 ksys_write+0x1b8/0x200 fs/read_write.c:731 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xaa/0x1b0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f In the function rxe_create_cq, when rxe_cq_from_init fails, the function rxe_cleanup will be called to handle the allocated resources. In fact, some memory resources have already been freed in the function rxe_cq_from_init. Thus, this problem will occur. The solution is to let rxe_cleanup do all the work.

Why

The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.

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: RDMA/rxe: Fix slab-use-after-free Read in rxe_queue_cleanup bug Call Trace: <TASK> __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x7d/0xa0 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:378 [inline] print_report+0xcf/0x610 mm/kasan/report.c:489 kasan_report+0xb5/0xe0 mm/kasan/report.c:602 rxe_queue_cleanup+0xd0/0xe0 drivers/infiniband/sw/rxe/rxe_queue.c:195 rxe_cq_cleanup+0x3f/0x50 drivers/infiniband/sw/rxe/rxe_cq.c:132 __rxe_cleanup+0x168/0x300 drivers/infiniband/sw/rxe/rxe_pool.c:232 rxe_create_cq+0x22e/0x3a0 drivers/infiniband/sw/rxe/rxe_verbs.c:1109 create_cq+0x658/0xb90 drivers/infiniband/core/uverbs_cmd.c:1052 ib_uverbs_create_cq+0xc7/0x120 drivers/infiniband/core/uverbs_cmd.c:1095 ib_uverbs_write+0x969/0xc90 drivers/infiniband/core/uverbs_main.c:679 vfs_write fs/read_write.c:677 [inline] vfs_write+0x26a/0xcc0 fs/read_write.c:659 ksys_write+0x1b8/0x200 fs/read_write.c:731 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xaa/0x1b0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f In the function rxe_create_cq, when rxe_cq_from_init fails, the function rxe_cleanup will be called to handle the allocated resources. In fact, some memory resources have already been freed in the function rxe_cq_from_init. Thus, this problem will occur. The solution is to let rxe_cleanup do all the work.

Why

The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.

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 → Use After Free → 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-416 ↗

CWE-416: Use After Free. The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory belongs to the code that operates on the new pointer.

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:H/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.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
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
CWE-416
A

Official authority intelligence

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

BSI · German · WID-SEC-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-2026-0783IBM QRadar SIEM: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM QRadar SIEM ausnutzen, um beliebigen Programmcode auszuführen, um Informationen offenzulegen, um einen Denial of Service Angriff durchzuführen, um einen Cross-Site Scripting Angriff durchzuführen, und um Dateien zu manipulieren.

Official advisory ↗
BSI · German · WID-SEC-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 ↗
Cyber Security Agency of Singapore · English · CSA-SB-20250625Security Bulletin 25 Jun 2025

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 25 Jun 2025, published on 25 June 2025. Open the linked bulletin for the product, severity and reference information published in that issue.

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

De multiples vulnérabilités ont été découvertes dans le noyau Linux de Red Hat. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire, une élévation de privilèges et une atteinte à la confidentialité des données.

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

De multiples vulnérabilités ont été découvertes dans le noyau Linux de Red Hat. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire, une élévation de privilèges et un déni de service à distance.

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

tps://access.redhat.com/errata/RHSA-2026:9643 Bulletin de sécurité Red Hat RHSA-2026:9644 du 22 avril 2026 https://access.redhat.com/errata/RHSA-2026:9644 Bulletin de sécurité Red Hat RHSA-2026:9835 du 22 avril 2026 https://access.redhat.com/errata/RHSA-2026:9835 Bulletin de sécurité Red Hat RHSA-2026:9836 du 22 avril 2026 https://access.redhat.com/errata/RHSA-2026:9836 Bulletin de sécurité Red Hat RHSA-2026:9870 du 22 avril 2026 https://access.redhat.com/errata/RHSA-2026:9870 Référence CVE CVE-2022-50053 https://www.cve.org/CVERecord?id=CVE-2022-50053 Référence CVE CVE-2023-53539 https://www.cve.org/CVERecord?id=CVE-2023-53539 Référence CVE CVE-2025-38024 https://www.cve.org/CVERecord?id=CVE-2025-38024 Référence CVE CVE-2025-38180 https://www.cve.org/CVERecord?id=CVE-2025-38180 Référence CVE CVE-2025-38248 https://www.cve.org/CVERecord?id=CVE-2025-38248 Référence CVE CVE-2025-39766 https://www.cve.org/CVERecord?id=CVE-2025-39766 Référence CVE CVE-2025-39981 https://www.cve.org/CVERecord?id=CVE-2025-39981 Référence CVE CVE-2025-40064 https://www.cve.org/CVERecord?id=CVE-2025-40064 Référence CVE CVE-2025-40168 https://www.cve.org/CVERecord?id=CVE-2025-40168 Référence CVE CVE-2025-68741 https://www.cve.org/CVERecord?id=CVE-2025-68741 Référence CVE CVE-2025-68800 https://www.cve.org/CVERecord?id=

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

De multiples vulnérabilités ont été découvertes dans le noyau Linux de Red Hat. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire, une élévation de privilèges et une atteinte à la confidentialité des données.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0327Multiples vulnérabilités dans les produits IBM

d?id=CVE-2025-22150 Référence CVE CVE-2025-23184 https://www.cve.org/CVERecord?id=CVE-2025-23184 Référence CVE CVE-2025-27152 https://www.cve.org/CVERecord?id=CVE-2025-27152 Référence CVE CVE-2025-27533 https://www.cve.org/CVERecord?id=CVE-2025-27533 Référence CVE CVE-2025-29927 https://www.cve.org/CVERecord?id=CVE-2025-29927 Référence CVE CVE-2025-32421 https://www.cve.org/CVERecord?id=CVE-2025-32421 Référence CVE CVE-2025-32996 https://www.cve.org/CVERecord?id=CVE-2025-32996 Référence CVE CVE-2025-32997 https://www.cve.org/CVERecord?id=CVE-2025-32997 Référence CVE CVE-2025-38022 https://www.cve.org/CVERecord?id=CVE-2025-38022 Référence CVE CVE-2025-38024 https://www.cve.org/CVERecord?id=CVE-2025-38024 Référence CVE CVE-2025-38051 https://www.cve.org/CVERecord?id=CVE-2025-38051 Référence CVE CVE-2025-38403 https://www.cve.org/CVERecord?id=CVE-2025-38403 Référence CVE CVE-2025-38415 https://www.cve.org/CVERecord?id=CVE-2025-38415 Référence CVE CVE-2025-38459 https://www.cve.org/CVERecord?id=CVE-2025-38459 Référence CVE CVE-2025-39760 https://www.cve.org/CVERecord?id=CVE-2025-39760 Référence CVE CVE-2025-39933 https://www.cve.org/CVERecord?id=CVE-2025-39933 Référence CVE CVE-2025-40096 https://www.cve.org/CVERecord?id=CVE-2025-40096 Référence CVE CVE-2025-40135 https://www.cve.org/CVERecord?id=

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

De multiples vulnérabilités ont été découvertes dans le noyau Linux de Red Hat. Elles permettent à un attaquant de provoquer une atteinte à l'intégrité des données, un contournement de la politique de sécurité et un problème de sécurité non spécifié par l'éditeur.

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

d?id=CVE-2025-38010 Référence CVE CVE-2025-38011 https://www.cve.org/CVERecord?id=CVE-2025-38011 Référence CVE CVE-2025-38013 https://www.cve.org/CVERecord?id=CVE-2025-38013 Référence CVE CVE-2025-38014 https://www.cve.org/CVERecord?id=CVE-2025-38014 Référence CVE CVE-2025-38015 https://www.cve.org/CVERecord?id=CVE-2025-38015 Référence CVE CVE-2025-38018 https://www.cve.org/CVERecord?id=CVE-2025-38018 Référence CVE CVE-2025-38019 https://www.cve.org/CVERecord?id=CVE-2025-38019 Référence CVE CVE-2025-38020 https://www.cve.org/CVERecord?id=CVE-2025-38020 Référence CVE CVE-2025-38023 https://www.cve.org/CVERecord?id=CVE-2025-38023 Référence CVE CVE-2025-38024 https://www.cve.org/CVERecord?id=CVE-2025-38024 Référence CVE CVE-2025-38027 https://www.cve.org/CVERecord?id=CVE-2025-38027 Référence CVE CVE-2025-38031 https://www.cve.org/CVERecord?id=CVE-2025-38031 Référence CVE CVE-2025-38034 https://www.cve.org/CVERecord?id=CVE-2025-38034 Référence CVE CVE-2025-38035 https://www.cve.org/CVERecord?id=CVE-2025-38035 Référence CVE CVE-2025-38037 https://www.cve.org/CVERecord?id=CVE-2025-38037 Référence CVE CVE-2025-38039 https://www.cve.org/CVERecord?id=CVE-2025-38039 Référence CVE CVE-2025-38040 https://www.cve.org/CVERecord?id=CVE-2025-38040 Référence CVE CVE-2025-38043 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38010 Référence CVE CVE-2025-38011 https://www.cve.org/CVERecord?id=CVE-2025-38011 Référence CVE CVE-2025-38013 https://www.cve.org/CVERecord?id=CVE-2025-38013 Référence CVE CVE-2025-38014 https://www.cve.org/CVERecord?id=CVE-2025-38014 Référence CVE CVE-2025-38015 https://www.cve.org/CVERecord?id=CVE-2025-38015 Référence CVE CVE-2025-38018 https://www.cve.org/CVERecord?id=CVE-2025-38018 Référence CVE CVE-2025-38019 https://www.cve.org/CVERecord?id=CVE-2025-38019 Référence CVE CVE-2025-38020 https://www.cve.org/CVERecord?id=CVE-2025-38020 Référence CVE CVE-2025-38023 https://www.cve.org/CVERecord?id=CVE-2025-38023 Référence CVE CVE-2025-38024 https://www.cve.org/CVERecord?id=CVE-2025-38024 Référence CVE CVE-2025-38027 https://www.cve.org/CVERecord?id=CVE-2025-38027 Référence CVE CVE-2025-38031 https://www.cve.org/CVERecord?id=CVE-2025-38031 Référence CVE CVE-2025-38034 https://www.cve.org/CVERecord?id=CVE-2025-38034 Référence CVE CVE-2025-38035 https://www.cve.org/CVERecord?id=CVE-2025-38035 Référence CVE CVE-2025-38037 https://www.cve.org/CVERecord?id=CVE-2025-38037 Référence CVE CVE-2025-38039 https://www.cve.org/CVERecord?id=CVE-2025-38039 Référence CVE CVE-2025-38040 https://www.cve.org/CVERecord?id=CVE-2025-38040 Référence CVE CVE-2025-38043 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38010 Référence CVE CVE-2025-38011 https://www.cve.org/CVERecord?id=CVE-2025-38011 Référence CVE CVE-2025-38013 https://www.cve.org/CVERecord?id=CVE-2025-38013 Référence CVE CVE-2025-38014 https://www.cve.org/CVERecord?id=CVE-2025-38014 Référence CVE CVE-2025-38015 https://www.cve.org/CVERecord?id=CVE-2025-38015 Référence CVE CVE-2025-38018 https://www.cve.org/CVERecord?id=CVE-2025-38018 Référence CVE CVE-2025-38019 https://www.cve.org/CVERecord?id=CVE-2025-38019 Référence CVE CVE-2025-38020 https://www.cve.org/CVERecord?id=CVE-2025-38020 Référence CVE CVE-2025-38023 https://www.cve.org/CVERecord?id=CVE-2025-38023 Référence CVE CVE-2025-38024 https://www.cve.org/CVERecord?id=CVE-2025-38024 Référence CVE CVE-2025-38027 https://www.cve.org/CVERecord?id=CVE-2025-38027 Référence CVE CVE-2025-38031 https://www.cve.org/CVERecord?id=CVE-2025-38031 Référence CVE CVE-2025-38034 https://www.cve.org/CVERecord?id=CVE-2025-38034 Référence CVE CVE-2025-38035 https://www.cve.org/CVERecord?id=CVE-2025-38035 Référence CVE CVE-2025-38037 https://www.cve.org/CVERecord?id=CVE-2025-38037 Référence CVE CVE-2025-38039 https://www.cve.org/CVERecord?id=CVE-2025-38039 Référence CVE CVE-2025-38040 https://www.cve.org/CVERecord?id=CVE-2025-38040 Référence CVE CVE-2025-38043 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38010 Référence CVE CVE-2025-38011 https://www.cve.org/CVERecord?id=CVE-2025-38011 Référence CVE CVE-2025-38013 https://www.cve.org/CVERecord?id=CVE-2025-38013 Référence CVE CVE-2025-38014 https://www.cve.org/CVERecord?id=CVE-2025-38014 Référence CVE CVE-2025-38015 https://www.cve.org/CVERecord?id=CVE-2025-38015 Référence CVE CVE-2025-38018 https://www.cve.org/CVERecord?id=CVE-2025-38018 Référence CVE CVE-2025-38019 https://www.cve.org/CVERecord?id=CVE-2025-38019 Référence CVE CVE-2025-38020 https://www.cve.org/CVERecord?id=CVE-2025-38020 Référence CVE CVE-2025-38023 https://www.cve.org/CVERecord?id=CVE-2025-38023 Référence CVE CVE-2025-38024 https://www.cve.org/CVERecord?id=CVE-2025-38024 Référence CVE CVE-2025-38027 https://www.cve.org/CVERecord?id=CVE-2025-38027 Référence CVE CVE-2025-38031 https://www.cve.org/CVERecord?id=CVE-2025-38031 Référence CVE CVE-2025-38034 https://www.cve.org/CVERecord?id=CVE-2025-38034 Référence CVE CVE-2025-38035 https://www.cve.org/CVERecord?id=CVE-2025-38035 Référence CVE CVE-2025-38037 https://www.cve.org/CVERecord?id=CVE-2025-38037 Référence CVE CVE-2025-38039 https://www.cve.org/CVERecord?id=CVE-2025-38039 Référence CVE CVE-2025-38040 https://www.cve.org/CVERecord?id=CVE-2025-38040 Référence CVE CVE-2025-38043 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2023-53751 Référence CVE CVE-2023-53833 https://www.cve.org/CVERecord?id=CVE-2023-53833 Référence CVE CVE-2024-54456 https://www.cve.org/CVERecord?id=CVE-2024-54456 Référence CVE CVE-2025-21647 https://www.cve.org/CVERecord?id=CVE-2025-21647 Référence CVE CVE-2025-21786 https://www.cve.org/CVERecord?id=CVE-2025-21786 Référence CVE CVE-2025-21791 https://www.cve.org/CVERecord?id=CVE-2025-21791 Référence CVE CVE-2025-37789 https://www.cve.org/CVERecord?id=CVE-2025-37789 Référence CVE CVE-2025-37819 https://www.cve.org/CVERecord?id=CVE-2025-37819 Référence CVE CVE-2025-38022 https://www.cve.org/CVERecord?id=CVE-2025-38022 Référence CVE CVE-2025-38024 https://www.cve.org/CVERecord?id=CVE-2025-38024 Référence CVE CVE-2025-38051 https://www.cve.org/CVERecord?id=CVE-2025-38051 Référence CVE CVE-2025-38403 https://www.cve.org/CVERecord?id=CVE-2025-38403 Référence CVE CVE-2025-38415 https://www.cve.org/CVERecord?id=CVE-2025-38415 Référence CVE CVE-2025-38459 https://www.cve.org/CVERecord?id=CVE-2025-38459 Référence CVE CVE-2025-38568 https://www.cve.org/CVERecord?id=CVE-2025-38568 Référence CVE CVE-2025-38730 https://www.cve.org/CVERecord?id=CVE-2025-38730 Référence CVE CVE-2025-39760 https://www.cve.org/CVERecord?id=CVE-2025-39760 Référence CVE CVE-2025-39817 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38010 Référence CVE CVE-2025-38011 https://www.cve.org/CVERecord?id=CVE-2025-38011 Référence CVE CVE-2025-38013 https://www.cve.org/CVERecord?id=CVE-2025-38013 Référence CVE CVE-2025-38014 https://www.cve.org/CVERecord?id=CVE-2025-38014 Référence CVE CVE-2025-38015 https://www.cve.org/CVERecord?id=CVE-2025-38015 Référence CVE CVE-2025-38018 https://www.cve.org/CVERecord?id=CVE-2025-38018 Référence CVE CVE-2025-38019 https://www.cve.org/CVERecord?id=CVE-2025-38019 Référence CVE CVE-2025-38020 https://www.cve.org/CVERecord?id=CVE-2025-38020 Référence CVE CVE-2025-38023 https://www.cve.org/CVERecord?id=CVE-2025-38023 Référence CVE CVE-2025-38024 https://www.cve.org/CVERecord?id=CVE-2025-38024 Référence CVE CVE-2025-38027 https://www.cve.org/CVERecord?id=CVE-2025-38027 Référence CVE CVE-2025-38031 https://www.cve.org/CVERecord?id=CVE-2025-38031 Référence CVE CVE-2025-38034 https://www.cve.org/CVERecord?id=CVE-2025-38034 Référence CVE CVE-2025-38035 https://www.cve.org/CVERecord?id=CVE-2025-38035 Référence CVE CVE-2025-38037 https://www.cve.org/CVERecord?id=CVE-2025-38037 Référence CVE CVE-2025-38039 https://www.cve.org/CVERecord?id=CVE-2025-38039 Référence CVE CVE-2025-38040 https://www.cve.org/CVERecord?id=CVE-2025-38040 Référence CVE CVE-2025-38043 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2022-50865 Référence CVE CVE-2023-53034 https://www.cve.org/CVERecord?id=CVE-2023-53034 Référence CVE CVE-2023-53539 https://www.cve.org/CVERecord?id=CVE-2023-53539 Référence CVE CVE-2023-53751 https://www.cve.org/CVERecord?id=CVE-2023-53751 Référence CVE CVE-2024-26766 https://www.cve.org/CVERecord?id=CVE-2024-26766 Référence CVE CVE-2025-21863 https://www.cve.org/CVERecord?id=CVE-2025-21863 Référence CVE CVE-2025-37789 https://www.cve.org/CVERecord?id=CVE-2025-37789 Référence CVE CVE-2025-37849 https://www.cve.org/CVERecord?id=CVE-2025-37849 Référence CVE CVE-2025-38022 https://www.cve.org/CVERecord?id=CVE-2025-38022 Référence CVE CVE-2025-38024 https://www.cve.org/CVERecord?id=CVE-2025-38024 Référence CVE CVE-2025-38051 https://www.cve.org/CVERecord?id=CVE-2025-38051 Référence CVE CVE-2025-38415 https://www.cve.org/CVERecord?id=CVE-2025-38415 Référence CVE CVE-2025-38459 https://www.cve.org/CVERecord?id=CVE-2025-38459 Référence CVE CVE-2025-38568 https://www.cve.org/CVERecord?id=CVE-2025-38568 Référence CVE CVE-2025-39760 https://www.cve.org/CVERecord?id=CVE-2025-39760 Référence CVE CVE-2025-39898 https://www.cve.org/CVERecord?id=CVE-2025-39898 Référence CVE CVE-2025-39971 https://www.cve.org/CVERecord?id=CVE-2025-39971 Référence CVE CVE-2025-40154 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-37997 Référence CVE CVE-2025-37998 https://www.cve.org/CVERecord?id=CVE-2025-37998 Référence CVE CVE-2025-38000 https://www.cve.org/CVERecord?id=CVE-2025-38000 Référence CVE CVE-2025-38001 https://www.cve.org/CVERecord?id=CVE-2025-38001 Référence CVE CVE-2025-38003 https://www.cve.org/CVERecord?id=CVE-2025-38003 Référence CVE CVE-2025-38004 https://www.cve.org/CVERecord?id=CVE-2025-38004 Référence CVE CVE-2025-38005 https://www.cve.org/CVERecord?id=CVE-2025-38005 Référence CVE CVE-2025-38009 https://www.cve.org/CVERecord?id=CVE-2025-38009 Référence CVE CVE-2025-38023 https://www.cve.org/CVERecord?id=CVE-2025-38023 Référence CVE CVE-2025-38024 https://www.cve.org/CVERecord?id=CVE-2025-38024 Référence CVE CVE-2025-38031 https://www.cve.org/CVERecord?id=CVE-2025-38031 Référence CVE CVE-2025-38034 https://www.cve.org/CVERecord?id=CVE-2025-38034 Référence CVE CVE-2025-38035 https://www.cve.org/CVERecord?id=CVE-2025-38035 Référence CVE CVE-2025-38037 https://www.cve.org/CVERecord?id=CVE-2025-38037 Référence CVE CVE-2025-38040 https://www.cve.org/CVERecord?id=CVE-2025-38040 Référence CVE CVE-2025-38043 https://www.cve.org/CVERecord?id=CVE-2025-38043 Référence CVE CVE-2025-38044 https://www.cve.org/CVERecord?id=CVE-2025-38044 Référence CVE CVE-2025-38048 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-37997 Référence CVE CVE-2025-37998 https://www.cve.org/CVERecord?id=CVE-2025-37998 Référence CVE CVE-2025-38000 https://www.cve.org/CVERecord?id=CVE-2025-38000 Référence CVE CVE-2025-38001 https://www.cve.org/CVERecord?id=CVE-2025-38001 Référence CVE CVE-2025-38003 https://www.cve.org/CVERecord?id=CVE-2025-38003 Référence CVE CVE-2025-38004 https://www.cve.org/CVERecord?id=CVE-2025-38004 Référence CVE CVE-2025-38005 https://www.cve.org/CVERecord?id=CVE-2025-38005 Référence CVE CVE-2025-38009 https://www.cve.org/CVERecord?id=CVE-2025-38009 Référence CVE CVE-2025-38023 https://www.cve.org/CVERecord?id=CVE-2025-38023 Référence CVE CVE-2025-38024 https://www.cve.org/CVERecord?id=CVE-2025-38024 Référence CVE CVE-2025-38031 https://www.cve.org/CVERecord?id=CVE-2025-38031 Référence CVE CVE-2025-38034 https://www.cve.org/CVERecord?id=CVE-2025-38034 Référence CVE CVE-2025-38035 https://www.cve.org/CVERecord?id=CVE-2025-38035 Référence CVE CVE-2025-38037 https://www.cve.org/CVERecord?id=CVE-2025-38037 Référence CVE CVE-2025-38043 https://www.cve.org/CVERecord?id=CVE-2025-38043 Référence CVE CVE-2025-38044 https://www.cve.org/CVERecord?id=CVE-2025-38044 Référence CVE CVE-2025-38048 https://www.cve.org/CVERecord?id=CVE-2025-38048 Référence CVE CVE-2025-38051 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-37994 Référence CVE CVE-2025-37995 https://www.cve.org/CVERecord?id=CVE-2025-37995 Référence CVE CVE-2025-37997 https://www.cve.org/CVERecord?id=CVE-2025-37997 Référence CVE CVE-2025-37998 https://www.cve.org/CVERecord?id=CVE-2025-37998 Référence CVE CVE-2025-38000 https://www.cve.org/CVERecord?id=CVE-2025-38000 Référence CVE CVE-2025-38001 https://www.cve.org/CVERecord?id=CVE-2025-38001 Référence CVE CVE-2025-38005 https://www.cve.org/CVERecord?id=CVE-2025-38005 Référence CVE CVE-2025-38009 https://www.cve.org/CVERecord?id=CVE-2025-38009 Référence CVE CVE-2025-38023 https://www.cve.org/CVERecord?id=CVE-2025-38023 Référence CVE CVE-2025-38024 https://www.cve.org/CVERecord?id=CVE-2025-38024 Référence CVE CVE-2025-38083 https://www.cve.org/CVERecord?id=CVE-2025-38083 Référence CVE CVE-2025-38094 https://www.cve.org/CVERecord?id=CVE-2025-38094 Référence CVE CVE-2025-38152 https://www.cve.org/CVERecord?id=CVE-2025-38152 Référence CVE CVE-2025-38177 https://www.cve.org/CVERecord?id=CVE-2025-38177 Référence CVE CVE-2025-38575 https://www.cve.org/CVERecord?id=CVE-2025-38575 Référence CVE CVE-2025-38637 https://www.cve.org/CVERecord?id=CVE-2025-38637 Référence CVE CVE-2025-39728 https://www.cve.org/CVERecord?id=CVE-2025-39728 Référence CVE CVE-2025-39735 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-37997 Référence CVE CVE-2025-37998 https://www.cve.org/CVERecord?id=CVE-2025-37998 Référence CVE CVE-2025-38000 https://www.cve.org/CVERecord?id=CVE-2025-38000 Référence CVE CVE-2025-38001 https://www.cve.org/CVERecord?id=CVE-2025-38001 Référence CVE CVE-2025-38003 https://www.cve.org/CVERecord?id=CVE-2025-38003 Référence CVE CVE-2025-38004 https://www.cve.org/CVERecord?id=CVE-2025-38004 Référence CVE CVE-2025-38005 https://www.cve.org/CVERecord?id=CVE-2025-38005 Référence CVE CVE-2025-38009 https://www.cve.org/CVERecord?id=CVE-2025-38009 Référence CVE CVE-2025-38023 https://www.cve.org/CVERecord?id=CVE-2025-38023 Référence CVE CVE-2025-38024 https://www.cve.org/CVERecord?id=CVE-2025-38024 Référence CVE CVE-2025-38031 https://www.cve.org/CVERecord?id=CVE-2025-38031 Référence CVE CVE-2025-38034 https://www.cve.org/CVERecord?id=CVE-2025-38034 Référence CVE CVE-2025-38035 https://www.cve.org/CVERecord?id=CVE-2025-38035 Référence CVE CVE-2025-38037 https://www.cve.org/CVERecord?id=CVE-2025-38037 Référence CVE CVE-2025-38043 https://www.cve.org/CVERecord?id=CVE-2025-38043 Référence CVE CVE-2025-38044 https://www.cve.org/CVERecord?id=CVE-2025-38044 Référence CVE CVE-2025-38048 https://www.cve.org/CVERecord?id=CVE-2025-38048 Référence CVE CVE-2025-38051 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38010 Référence CVE CVE-2025-38011 https://www.cve.org/CVERecord?id=CVE-2025-38011 Référence CVE CVE-2025-38013 https://www.cve.org/CVERecord?id=CVE-2025-38013 Référence CVE CVE-2025-38014 https://www.cve.org/CVERecord?id=CVE-2025-38014 Référence CVE CVE-2025-38015 https://www.cve.org/CVERecord?id=CVE-2025-38015 Référence CVE CVE-2025-38018 https://www.cve.org/CVERecord?id=CVE-2025-38018 Référence CVE CVE-2025-38020 https://www.cve.org/CVERecord?id=CVE-2025-38020 Référence CVE CVE-2025-38022 https://www.cve.org/CVERecord?id=CVE-2025-38022 Référence CVE CVE-2025-38023 https://www.cve.org/CVERecord?id=CVE-2025-38023 Référence CVE CVE-2025-38024 https://www.cve.org/CVERecord?id=CVE-2025-38024 Référence CVE CVE-2025-38027 https://www.cve.org/CVERecord?id=CVE-2025-38027 Référence CVE CVE-2025-38031 https://www.cve.org/CVERecord?id=CVE-2025-38031 Référence CVE CVE-2025-38034 https://www.cve.org/CVERecord?id=CVE-2025-38034 Référence CVE CVE-2025-38035 https://www.cve.org/CVERecord?id=CVE-2025-38035 Référence CVE CVE-2025-38040 https://www.cve.org/CVERecord?id=CVE-2025-38040 Référence CVE CVE-2025-38043 https://www.cve.org/CVERecord?id=CVE-2025-38043 Référence CVE CVE-2025-38044 https://www.cve.org/CVERecord?id=CVE-2025-38044 Référence CVE CVE-2025-38045 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38014 Référence CVE CVE-2025-38015 https://www.cve.org/CVERecord?id=CVE-2025-38015 Référence CVE CVE-2025-38016 https://www.cve.org/CVERecord?id=CVE-2025-38016 Référence CVE CVE-2025-38018 https://www.cve.org/CVERecord?id=CVE-2025-38018 Référence CVE CVE-2025-38019 https://www.cve.org/CVERecord?id=CVE-2025-38019 Référence CVE CVE-2025-38020 https://www.cve.org/CVERecord?id=CVE-2025-38020 Référence CVE CVE-2025-38021 https://www.cve.org/CVERecord?id=CVE-2025-38021 Référence CVE CVE-2025-38022 https://www.cve.org/CVERecord?id=CVE-2025-38022 Référence CVE CVE-2025-38023 https://www.cve.org/CVERecord?id=CVE-2025-38023 Référence CVE CVE-2025-38024 https://www.cve.org/CVERecord?id=CVE-2025-38024 Référence CVE CVE-2025-38025 https://www.cve.org/CVERecord?id=CVE-2025-38025 Référence CVE CVE-2025-38027 https://www.cve.org/CVERecord?id=CVE-2025-38027 Référence CVE CVE-2025-38028 https://www.cve.org/CVERecord?id=CVE-2025-38028 Référence CVE CVE-2025-38031 https://www.cve.org/CVERecord?id=CVE-2025-38031 Référence CVE CVE-2025-38034 https://www.cve.org/CVERecord?id=CVE-2025-38034 Référence CVE CVE-2025-38035 https://www.cve.org/CVERecord?id=CVE-2025-38035 Référence CVE CVE-2025-38037 https://www.cve.org/CVERecord?id=CVE-2025-38037 Référence CVE CVE-2025-38043 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-37997 Référence CVE CVE-2025-37998 https://www.cve.org/CVERecord?id=CVE-2025-37998 Référence CVE CVE-2025-38005 https://www.cve.org/CVERecord?id=CVE-2025-38005 Référence CVE CVE-2025-38007 https://www.cve.org/CVERecord?id=CVE-2025-38007 Référence CVE CVE-2025-38009 https://www.cve.org/CVERecord?id=CVE-2025-38009 Référence CVE CVE-2025-38015 https://www.cve.org/CVERecord?id=CVE-2025-38015 Référence CVE CVE-2025-38018 https://www.cve.org/CVERecord?id=CVE-2025-38018 Référence CVE CVE-2025-38020 https://www.cve.org/CVERecord?id=CVE-2025-38020 Référence CVE CVE-2025-38023 https://www.cve.org/CVERecord?id=CVE-2025-38023 Référence CVE CVE-2025-38024 https://www.cve.org/CVERecord?id=CVE-2025-38024 Référence CVE CVE-2025-38027 https://www.cve.org/CVERecord?id=CVE-2025-38027 Référence CVE CVE-2025-38094 https://www.cve.org/CVERecord?id=CVE-2025-38094 Référence CVE CVE-2025-38095 https://www.cve.org/CVERecord?id=CVE-2025-38095 Référence CVE CVE-2025-38177 https://www.cve.org/CVERecord?id=CVE-2025-38177 Gestion détaillée du document le 14 août 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

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

d?id=CVE-2025-37994 Référence CVE CVE-2025-37995 https://www.cve.org/CVERecord?id=CVE-2025-37995 Référence CVE CVE-2025-37997 https://www.cve.org/CVERecord?id=CVE-2025-37997 Référence CVE CVE-2025-37998 https://www.cve.org/CVERecord?id=CVE-2025-37998 Référence CVE CVE-2025-38000 https://www.cve.org/CVERecord?id=CVE-2025-38000 Référence CVE CVE-2025-38001 https://www.cve.org/CVERecord?id=CVE-2025-38001 Référence CVE CVE-2025-38005 https://www.cve.org/CVERecord?id=CVE-2025-38005 Référence CVE CVE-2025-38009 https://www.cve.org/CVERecord?id=CVE-2025-38009 Référence CVE CVE-2025-38023 https://www.cve.org/CVERecord?id=CVE-2025-38023 Référence CVE CVE-2025-38024 https://www.cve.org/CVERecord?id=CVE-2025-38024 Référence CVE CVE-2025-38083 https://www.cve.org/CVERecord?id=CVE-2025-38083 Référence CVE CVE-2025-38094 https://www.cve.org/CVERecord?id=CVE-2025-38094 Référence CVE CVE-2025-38177 https://www.cve.org/CVERecord?id=CVE-2025-38177 Gestion détaillée du document le 08 août 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 sy

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

d?id=CVE-2025-37994 Référence CVE CVE-2025-37995 https://www.cve.org/CVERecord?id=CVE-2025-37995 Référence CVE CVE-2025-37997 https://www.cve.org/CVERecord?id=CVE-2025-37997 Référence CVE CVE-2025-37998 https://www.cve.org/CVERecord?id=CVE-2025-37998 Référence CVE CVE-2025-38000 https://www.cve.org/CVERecord?id=CVE-2025-38000 Référence CVE CVE-2025-38001 https://www.cve.org/CVERecord?id=CVE-2025-38001 Référence CVE CVE-2025-38005 https://www.cve.org/CVERecord?id=CVE-2025-38005 Référence CVE CVE-2025-38009 https://www.cve.org/CVERecord?id=CVE-2025-38009 Référence CVE CVE-2025-38023 https://www.cve.org/CVERecord?id=CVE-2025-38023 Référence CVE CVE-2025-38024 https://www.cve.org/CVERecord?id=CVE-2025-38024 Référence CVE CVE-2025-38083 https://www.cve.org/CVERecord?id=CVE-2025-38083 Référence CVE CVE-2025-38094 https://www.cve.org/CVERecord?id=CVE-2025-38094 Référence CVE CVE-2025-38177 https://www.cve.org/CVERecord?id=CVE-2025-38177 Gestion détaillée du document le 01 août 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 sy

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

d?id=CVE-2025-38010 Référence CVE CVE-2025-38011 https://www.cve.org/CVERecord?id=CVE-2025-38011 Référence CVE CVE-2025-38013 https://www.cve.org/CVERecord?id=CVE-2025-38013 Référence CVE CVE-2025-38014 https://www.cve.org/CVERecord?id=CVE-2025-38014 Référence CVE CVE-2025-38015 https://www.cve.org/CVERecord?id=CVE-2025-38015 Référence CVE CVE-2025-38018 https://www.cve.org/CVERecord?id=CVE-2025-38018 Référence CVE CVE-2025-38020 https://www.cve.org/CVERecord?id=CVE-2025-38020 Référence CVE CVE-2025-38022 https://www.cve.org/CVERecord?id=CVE-2025-38022 Référence CVE CVE-2025-38023 https://www.cve.org/CVERecord?id=CVE-2025-38023 Référence CVE CVE-2025-38024 https://www.cve.org/CVERecord?id=CVE-2025-38024 Référence CVE CVE-2025-38027 https://www.cve.org/CVERecord?id=CVE-2025-38027 Référence CVE CVE-2025-38031 https://www.cve.org/CVERecord?id=CVE-2025-38031 Référence CVE CVE-2025-38040 https://www.cve.org/CVERecord?id=CVE-2025-38040 Référence CVE CVE-2025-38043 https://www.cve.org/CVERecord?id=CVE-2025-38043 Référence CVE CVE-2025-38044 https://www.cve.org/CVERecord?id=CVE-2025-38044 Référence CVE CVE-2025-38045 https://www.cve.org/CVERecord?id=CVE-2025-38045 Référence CVE CVE-2025-38053 https://www.cve.org/CVERecord?id=CVE-2025-38053 Référence CVE CVE-2025-38057 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-37994 Référence CVE CVE-2025-37995 https://www.cve.org/CVERecord?id=CVE-2025-37995 Référence CVE CVE-2025-37997 https://www.cve.org/CVERecord?id=CVE-2025-37997 Référence CVE CVE-2025-37998 https://www.cve.org/CVERecord?id=CVE-2025-37998 Référence CVE CVE-2025-38000 https://www.cve.org/CVERecord?id=CVE-2025-38000 Référence CVE CVE-2025-38001 https://www.cve.org/CVERecord?id=CVE-2025-38001 Référence CVE CVE-2025-38005 https://www.cve.org/CVERecord?id=CVE-2025-38005 Référence CVE CVE-2025-38009 https://www.cve.org/CVERecord?id=CVE-2025-38009 Référence CVE CVE-2025-38023 https://www.cve.org/CVERecord?id=CVE-2025-38023 Référence CVE CVE-2025-38024 https://www.cve.org/CVERecord?id=CVE-2025-38024 Référence CVE CVE-2025-38094 https://www.cve.org/CVERecord?id=CVE-2025-38094 Référence CVE CVE-2025-38152 https://www.cve.org/CVERecord?id=CVE-2025-38152 Référence CVE CVE-2025-38177 https://www.cve.org/CVERecord?id=CVE-2025-38177 Référence CVE CVE-2025-38216 https://www.cve.org/CVERecord?id=CVE-2025-38216 Référence CVE CVE-2025-38575 https://www.cve.org/CVERecord?id=CVE-2025-38575 Référence CVE CVE-2025-38637 https://www.cve.org/CVERecord?id=CVE-2025-38637 Référence CVE CVE-2025-39728 https://www.cve.org/CVERecord?id=CVE-2025-39728 Référence CVE CVE-2025-39735 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-2025-38010 Référence CVE CVE-2025-38011 https://www.cve.org/CVERecord?id=CVE-2025-38011 Référence CVE CVE-2025-38013 https://www.cve.org/CVERecord?id=CVE-2025-38013 Référence CVE CVE-2025-38014 https://www.cve.org/CVERecord?id=CVE-2025-38014 Référence CVE CVE-2025-38015 https://www.cve.org/CVERecord?id=CVE-2025-38015 Référence CVE CVE-2025-38018 https://www.cve.org/CVERecord?id=CVE-2025-38018 Référence CVE CVE-2025-38020 https://www.cve.org/CVERecord?id=CVE-2025-38020 Référence CVE CVE-2025-38022 https://www.cve.org/CVERecord?id=CVE-2025-38022 Référence CVE CVE-2025-38023 https://www.cve.org/CVERecord?id=CVE-2025-38023 Référence CVE CVE-2025-38024 https://www.cve.org/CVERecord?id=CVE-2025-38024 Référence CVE CVE-2025-38027 https://www.cve.org/CVERecord?id=CVE-2025-38027 Référence CVE CVE-2025-38031 https://www.cve.org/CVERecord?id=CVE-2025-38031 Référence CVE CVE-2025-38040 https://www.cve.org/CVERecord?id=CVE-2025-38040 Référence CVE CVE-2025-38043 https://www.cve.org/CVERecord?id=CVE-2025-38043 Référence CVE CVE-2025-38044 https://www.cve.org/CVERecord?id=CVE-2025-38044 Référence CVE CVE-2025-38045 https://www.cve.org/CVERecord?id=CVE-2025-38045 Référence CVE CVE-2025-38053 https://www.cve.org/CVERecord?id=CVE-2025-38053 Référence CVE CVE-2025-38055 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-2025-38010 Référence CVE CVE-2025-38011 https://www.cve.org/CVERecord?id=CVE-2025-38011 Référence CVE CVE-2025-38013 https://www.cve.org/CVERecord?id=CVE-2025-38013 Référence CVE CVE-2025-38014 https://www.cve.org/CVERecord?id=CVE-2025-38014 Référence CVE CVE-2025-38015 https://www.cve.org/CVERecord?id=CVE-2025-38015 Référence CVE CVE-2025-38018 https://www.cve.org/CVERecord?id=CVE-2025-38018 Référence CVE CVE-2025-38020 https://www.cve.org/CVERecord?id=CVE-2025-38020 Référence CVE CVE-2025-38022 https://www.cve.org/CVERecord?id=CVE-2025-38022 Référence CVE CVE-2025-38023 https://www.cve.org/CVERecord?id=CVE-2025-38023 Référence CVE CVE-2025-38024 https://www.cve.org/CVERecord?id=CVE-2025-38024 Référence CVE CVE-2025-38027 https://www.cve.org/CVERecord?id=CVE-2025-38027 Référence CVE CVE-2025-38031 https://www.cve.org/CVERecord?id=CVE-2025-38031 Référence CVE CVE-2025-38040 https://www.cve.org/CVERecord?id=CVE-2025-38040 Référence CVE CVE-2025-38043 https://www.cve.org/CVERecord?id=CVE-2025-38043 Référence CVE CVE-2025-38044 https://www.cve.org/CVERecord?id=CVE-2025-38044 Référence CVE CVE-2025-38045 https://www.cve.org/CVERecord?id=CVE-2025-38045 Référence CVE CVE-2025-38053 https://www.cve.org/CVERecord?id=CVE-2025-38053 Référence CVE CVE-2025-38055 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2025-022699Linux の Linux Kernel 等複数ベンダの製品における解放済みメモリの使用に関する脆弱性

Linux の Linux Kernel 等複数ベンダの製品には、解放済みメモリの使用に関する脆弱性が存在します。

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.
Fix availability varies by product
Affected
Fixed
Linux: < 4.8, 5.4.294 ≤ 5.4.*, 5.10.238 ≤ 5.10.*, 5.15.184 ≤ 5.15.*, 6.1.140 ≤ 6.1.*, 6.6.92 ≤ 6.6.*, 6.12.30 ≤ 6.12.*, 6.14.8 ≤ 6.14.*, 6.15 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
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 5 Aug 2026, 11:59 UTC · CWE-416 · Use After Free

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-27876
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2025-27876↗Vendor CSAF · SUSE Product Security Team↗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-2025-38024 · cve.blacktree.nl