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

net/tipc: fix slab-use-after-free Read in tipc_aead_encrypt_done

Linux · Linux

8.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:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.54% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • 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: Within 30 daysRemediation target: Within 180 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.32-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.147-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.32-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.32-1Debian Security Tracker ↗Source updated 6 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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 5 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-38052 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: net/tipc: fix slab-use-after-free Read in tipc_aead_encrypt_done
22 known affected

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

  • kernel-rt as a component of Red Hat Enterprise Linux 9
  • kernel-rt-core as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-core as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-devel as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-devel-matched as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-kvm as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-modules as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-modules-core as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-modules-extra as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-modules-internal as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-modules-partner as a component of Red Hat Enterprise Linux 9
Summary
A vulnerability was found in the Linux kernel's management of network namespaces. By manipulating the lifecycle of network namespaces, an attacker could exploit this vulnerability to cause a system crash or leak sensitive system memory. Exploitation of this vulnerability requires that a user has access to the system and the ability to create or destroy network namespaces. This typically requires administrative privileges, but could be exposed to an unprivileged user who has control over container lifecycles or a user who has administrative privileges within a container.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.
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-18601

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: net/tipc: fix slab-use-after-free Read in tipc_aead_encrypt_done Syzbot reported a slab-use-after-free with the following call trace: ================================================================== BUG: KASAN: slab-use-after-free in tipc_aead_encrypt_done+0x4bd/0x510 net/tipc/crypto.c:840 Read of size 8 at addr ffff88807a733000 by task kworker/1:0/25 Call Trace: kasan_report+0xd9/0x110 mm/kasan/report.c:601 tipc_aead_encrypt_done+0x4bd/0x510 net/tipc/crypto.c:840 crypto_request_complete include/crypto/algapi.h:266 aead_request_complete include/crypto/internal/aead.h:85 cryptd_aead_crypt+0x3b8/0x750 crypto/cryptd.c:772 crypto_request_complete include/crypto/algapi.h:266 cryptd_queue_worker+0x131/0x200 crypto/cryptd.c:181 process_one_work+0x9fb/0x1b60 kernel/workqueue.c:3231 Allocated by task 8355: kzalloc_noprof include/linux/slab.h:778 tipc_crypto_start+0xcc/0x9e0 net/tipc/crypto.c:1466 tipc_init_net+0x2dd/0x430 net/tipc/core.c:72 ops_init+0xb9/0x650 net/core/net_namespace.c:139 setup_net+0x435/0xb40 net/core/net_namespace.c:343 copy_net_ns+0x2f0/0x670 net/core/net_namespace.c:508 create_new_namespaces+0x3ea/0xb10 kernel/nsproxy.c:110 unshare_nsproxy_namespaces+0xc0/0x1f0 kernel/nsproxy.c:228 ksys_unshare+0x419/0x970 kernel/fork.c:3323 __do_sys_unshare kernel/fork.c:3394 Freed by task 63: kfree+0x12a/0x3b0 mm/slub.c:4557 tipc_crypto_stop+0x23c/0x500 net/tipc/crypto.c:1539 tipc_exit_net+0x8c/0x110 net/tipc/core.c:119 ops_exit_list+0xb0/0x180 net/core/net_namespace.c:173 cleanup_net+0x5b7/0xbf0 net/core/net_namespace.c:640 process_one_work+0x9fb/0x1b60 kernel/workqueue.c:3231 After freed the tipc_crypto tx by delete namespace, tipc_aead_encrypt_done may still visit it in cryptd_queue_worker workqueue. I reproduce this issue by: ip netns add ns1 ip link add veth1 type veth peer name veth2 ip link set veth1 netns ns1 ip netns exec ns1 tipc bearer enable media eth dev veth1 ip netns exec ns1 tipc node set key this_is_a_master_key master ip netns exec ns1 tipc bearer disable media eth dev veth1 ip netns del ns1 The key of reproduction is that, simd_aead_encrypt is interrupted, leading to crypto_simd_usable() return false. Thus, the cryptd_queue_worker is triggered, and the tipc_crypto tx will be visited. tipc_disc_timeout tipc_bearer_xmit_skb tipc_crypto_xmit tipc_aead_encrypt crypto_aead_encrypt // encrypt() simd_aead_encrypt // crypto_simd_usable() is false child = &ctx->cryptd_tfm->base; simd_aead_encrypt crypto_aead_encrypt // encrypt() cryptd_aead_encrypt_enqueue cryptd_aead_enqueue cryptd_enqueue_request // trigger cryptd_queue_worker queue_work_on(smp_processor_id(), cryptd_wq, &cpu_queue->work) Fix this by holding net reference count before encrypt.

What

In the Linux kernel, the following vulnerability has been resolved: net/tipc: fix slab-use-after-free Read in tipc_aead_encrypt_done Syzbot reported a slab-use-after-free with the following call trace: ================================================================== BUG: KASAN: slab-use-after-free in tipc_aead_encrypt_done+0x4bd/0x510 net/tipc/crypto.c:840 Read of size 8 at addr ffff88807a733000 by task kworker/1:0/25 Call Trace: kasan_report+0xd9/0x110 mm/kasan/report.c:601 tipc_aead_encrypt_done+0x4bd/0x510 net/tipc/crypto.c:840 crypto_request_complete include/crypto/algapi.h:266 aead_request_complete include/crypto/internal/aead.h:85 cryptd_aead_crypt+0x3b8/0x750 crypto/cryptd.c:772 crypto_request_complete include/crypto/algapi.h:266 cryptd_queue_worker+0x131/0x200 crypto/cryptd.c:181 process_one_work+0x9fb/0x1b60 kernel/workqueue.c:3231 Allocated by task 8355: kzalloc_noprof include/linux/slab.h:778 tipc_crypto_start+0xcc/0x9e0 net/tipc/crypto.c:1466 tipc_init_net+0x2dd/0x430 net/tipc/core.c:72 ops_init+0xb9/0x650 net/core/net_namespace.c:139 setup_net+0x435/0xb40 net/core/net_namespace.c:343 copy_net_ns+0x2f0/0x670 net/core/net_namespace.c:508 create_new_namespaces+0x3ea/0xb10 kernel/nsproxy.c:110 unshare_nsproxy_namespaces+0xc0/0x1f0 kernel/nsproxy.c:228 ksys_unshare+0x419/0x970 kernel/fork.c:3323 __do_sys_unshare kernel/fork.c:3394 Freed by task 63: kfree+0x12a/0x3b0 mm/slub.c:4557 tipc_crypto_stop+0x23c/0x500 net/tipc/crypto.c:1539 tipc_exit_net+0x8c/0x110 net/tipc/core.c:119 ops_exit_list+0xb0/0x180 net/core/net_namespace.c:173 cleanup_net+0x5b7/0xbf0 net/core/net_namespace.c:640 process_one_work+0x9fb/0x1b60 kernel/workqueue.c:3231 After freed the tipc_crypto tx by delete namespace, tipc_aead_encrypt_done may still visit it in cryptd_queue_worker workqueue. I reproduce this issue by: ip netns add ns1 ip link add veth1 type veth peer name veth2 ip link set veth1 netns ns1 ip netns exec ns1 tipc bearer enable media eth dev veth1 ip netns exec ns1 tipc node set key this_is_a_master_key master ip netns exec ns1 tipc bearer disable media eth dev veth1 ip netns del ns1 The key of reproduction is that, simd_aead_encrypt is interrupted, leading to crypto_simd_usable() return false. Thus, the cryptd_queue_worker is triggered, and the tipc_crypto tx will be visited. tipc_disc_timeout tipc_bearer_xmit_skb tipc_crypto_xmit tipc_aead_encrypt crypto_aead_encrypt // encrypt() simd_aead_encrypt // crypto_simd_usable() is false child = &ctx->cryptd_tfm->base; simd_aead_encrypt crypto_aead_encrypt // encrypt() cryptd_aead_encrypt_enqueue cryptd_aead_enqueue cryptd_enqueue_request // trigger cryptd_queue_worker queue_work_on(smp_processor_id(), cryptd_wq, &cpu_queue->work) Fix this by holding net reference count before encrypt.

Why

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

How

An attacker operating through a network path 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: net/tipc: fix slab-use-after-free Read in tipc_aead_encrypt_done Syzbot reported a slab-use-after-free with the following call trace: ================================================================== BUG: KASAN: slab-use-after-free in tipc_aead_encrypt_done+0x4bd/0x510 net/tipc/crypto.c:840 Read of size 8 at addr ffff88807a733000 by task kworker/1:0/25 Call Trace: kasan_report+0xd9/0x110 mm/kasan/report.c:601 tipc_aead_encrypt_done+0x4bd/0x510 net/tipc/crypto.c:840 crypto_request_complete include/crypto/algapi.h:266 aead_request_complete include/crypto/internal/aead.h:85 cryptd_aead_crypt+0x3b8/0x750 crypto/cryptd.c:772 crypto_request_complete include/crypto/algapi.h:266 cryptd_queue_worker+0x131/0x200 crypto/cryptd.c:181 process_one_work+0x9fb/0x1b60 kernel/workqueue.c:3231 Allocated by task 8355: kzalloc_noprof include/linux/slab.h:778 tipc_crypto_start+0xcc/0x9e0 net/tipc/crypto.c:1466 tipc_init_net+0x2dd/0x430 net/tipc/core.c:72 ops_init+0xb9/0x650 net/core/net_namespace.c:139 setup_net+0x435/0xb40 net/core/net_namespace.c:343 copy_net_ns+0x2f0/0x670 net/core/net_namespace.c:508 create_new_namespaces+0x3ea/0xb10 kernel/nsproxy.c:110 unshare_nsproxy_namespaces+0xc0/0x1f0 kernel/nsproxy.c:228 ksys_unshare+0x419/0x970 kernel/fork.c:3323 __do_sys_unshare kernel/fork.c:3394 Freed by task 63: kfree+0x12a/0x3b0 mm/slub.c:4557 tipc_crypto_stop+0x23c/0x500 net/tipc/crypto.c:1539 tipc_exit_net+0x8c/0x110 net/tipc/core.c:119 ops_exit_list+0xb0/0x180 net/core/net_namespace.c:173 cleanup_net+0x5b7/0xbf0 net/core/net_namespace.c:640 process_one_work+0x9fb/0x1b60 kernel/workqueue.c:3231 After freed the tipc_crypto tx by delete namespace, tipc_aead_encrypt_done may still visit it in cryptd_queue_worker workqueue. I reproduce this issue by: ip netns add ns1 ip link add veth1 type veth peer name veth2 ip link set veth1 netns ns1 ip netns exec ns1 tipc bearer enable media eth dev veth1 ip netns exec ns1 tipc node set key this_is_a_master_key master ip netns exec ns1 tipc bearer disable media eth dev veth1 ip netns del ns1 The key of reproduction is that, simd_aead_encrypt is interrupted, leading to crypto_simd_usable() return false. Thus, the cryptd_queue_worker is triggered, and the tipc_crypto tx will be visited. tipc_disc_timeout tipc_bearer_xmit_skb tipc_crypto_xmit tipc_aead_encrypt crypto_aead_encrypt // encrypt() simd_aead_encrypt // crypto_simd_usable() is false child = &ctx->cryptd_tfm->base; simd_aead_encrypt crypto_aead_encrypt // encrypt() cryptd_aead_encrypt_enqueue cryptd_aead_enqueue cryptd_enqueue_request // trigger cryptd_queue_worker queue_work_on(smp_processor_id(), cryptd_wq, &cpu_queue->work) Fix this by holding net reference count before encrypt.

Why

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

How

An attacker operating through a network path 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
a network path → Use After Free → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
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:N/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.

AVNetworkAttack vector: The vulnerable component can be reached over a network.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
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.
NetworkCWE-416
A

Official authority intelligence

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

BSI · German · WID-SEC-2025-1905IBM QRadar SIEM Komponente: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM QRadar SIEM Komponenten ausnutzen, um Daten zu manipulieren, um einen Denial of Service Angriff durchzuführen, um beliebigen Programmcode auszuführen, um Sicherheitsvorkehrungen zu umgehen, und um Informationen offenzulegen.

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-0246Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?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=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-38048 https://www.cve.org/CVERecord?id=CVE-2025-38048 Référence CVE CVE-2025-38051 https://www.cve.org/CVERecord?id=CVE-2025-38051 Référence CVE CVE-2025-38052 https://www.cve.org/CVERecord?id=CVE-2025-38052 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=CVE-2025-38055 Référence CVE CVE-2025-38057 https://www.cve.org/CVERecord?id=CVE-2025-38057 Référence CVE CVE-2025-38058 https://www.cve.org/CVERecord?id=CVE-2025-38058 Référence CVE CVE-2025-38059 https://www.cve.org/CVERecord?id=CVE-2025-38059 Référence CVE CVE-2025-38060 https://www.cve.org/CVERecord?id=CVE-2025-38060 Référence CVE CVE-2025-38061 https://www.cve.org/CVERecord?id=CVE-2025-38061 Référence CVE CVE-2025-38062 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-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=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-38048 https://www.cve.org/CVERecord?id=CVE-2025-38048 Référence CVE CVE-2025-38051 https://www.cve.org/CVERecord?id=CVE-2025-38051 Référence CVE CVE-2025-38052 https://www.cve.org/CVERecord?id=CVE-2025-38052 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=CVE-2025-38055 Référence CVE CVE-2025-38057 https://www.cve.org/CVERecord?id=CVE-2025-38057 Référence CVE CVE-2025-38058 https://www.cve.org/CVERecord?id=CVE-2025-38058 Référence CVE CVE-2025-38059 https://www.cve.org/CVERecord?id=CVE-2025-38059 Référence CVE CVE-2025-38060 https://www.cve.org/CVERecord?id=CVE-2025-38060 Référence CVE CVE-2025-38061 https://www.cve.org/CVERecord?id=CVE-2025-38061 Référence CVE CVE-2025-38062 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-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=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-38048 https://www.cve.org/CVERecord?id=CVE-2025-38048 Référence CVE CVE-2025-38051 https://www.cve.org/CVERecord?id=CVE-2025-38051 Référence CVE CVE-2025-38052 https://www.cve.org/CVERecord?id=CVE-2025-38052 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=CVE-2025-38055 Référence CVE CVE-2025-38057 https://www.cve.org/CVERecord?id=CVE-2025-38057 Référence CVE CVE-2025-38058 https://www.cve.org/CVERecord?id=CVE-2025-38058 Référence CVE CVE-2025-38059 https://www.cve.org/CVERecord?id=CVE-2025-38059 Référence CVE CVE-2025-38060 https://www.cve.org/CVERecord?id=CVE-2025-38060 Référence CVE CVE-2025-38061 https://www.cve.org/CVERecord?id=CVE-2025-38061 Référence CVE CVE-2025-38062 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-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=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-38048 https://www.cve.org/CVERecord?id=CVE-2025-38048 Référence CVE CVE-2025-38051 https://www.cve.org/CVERecord?id=CVE-2025-38051 Référence CVE CVE-2025-38052 https://www.cve.org/CVERecord?id=CVE-2025-38052 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=CVE-2025-38055 Référence CVE CVE-2025-38057 https://www.cve.org/CVERecord?id=CVE-2025-38057 Référence CVE CVE-2025-38058 https://www.cve.org/CVERecord?id=CVE-2025-38058 Référence CVE CVE-2025-38059 https://www.cve.org/CVERecord?id=CVE-2025-38059 Référence CVE CVE-2025-38060 https://www.cve.org/CVERecord?id=CVE-2025-38060 Référence CVE CVE-2025-38061 https://www.cve.org/CVERecord?id=CVE-2025-38061 Référence CVE CVE-2025-38062 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-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=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-38048 https://www.cve.org/CVERecord?id=CVE-2025-38048 Référence CVE CVE-2025-38051 https://www.cve.org/CVERecord?id=CVE-2025-38051 Référence CVE CVE-2025-38052 https://www.cve.org/CVERecord?id=CVE-2025-38052 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=CVE-2025-38055 Référence CVE CVE-2025-38057 https://www.cve.org/CVERecord?id=CVE-2025-38057 Référence CVE CVE-2025-38058 https://www.cve.org/CVERecord?id=CVE-2025-38058 Référence CVE CVE-2025-38059 https://www.cve.org/CVERecord?id=CVE-2025-38059 Référence CVE CVE-2025-38060 https://www.cve.org/CVERecord?id=CVE-2025-38060 Référence CVE CVE-2025-38061 https://www.cve.org/CVERecord?id=CVE-2025-38061 Référence CVE CVE-2025-38062 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-37856 Référence CVE CVE-2025-37861 https://www.cve.org/CVERecord?id=CVE-2025-37861 Référence CVE CVE-2025-37864 https://www.cve.org/CVERecord?id=CVE-2025-37864 Référence CVE CVE-2025-37885 https://www.cve.org/CVERecord?id=CVE-2025-37885 Référence CVE CVE-2025-38006 https://www.cve.org/CVERecord?id=CVE-2025-38006 Référence CVE CVE-2025-38008 https://www.cve.org/CVERecord?id=CVE-2025-38008 Référence CVE CVE-2025-38019 https://www.cve.org/CVERecord?id=CVE-2025-38019 Référence CVE CVE-2025-38034 https://www.cve.org/CVERecord?id=CVE-2025-38034 Référence CVE CVE-2025-38038 https://www.cve.org/CVERecord?id=CVE-2025-38038 Référence CVE CVE-2025-38052 https://www.cve.org/CVERecord?id=CVE-2025-38052 Référence CVE CVE-2025-38058 https://www.cve.org/CVERecord?id=CVE-2025-38058 Référence CVE CVE-2025-38062 https://www.cve.org/CVERecord?id=CVE-2025-38062 Référence CVE CVE-2025-38075 https://www.cve.org/CVERecord?id=CVE-2025-38075 Référence CVE CVE-2025-38084 https://www.cve.org/CVERecord?id=CVE-2025-38084 Référence CVE CVE-2025-38085 https://www.cve.org/CVERecord?id=CVE-2025-38085 Référence CVE CVE-2025-38087 https://www.cve.org/CVERecord?id=CVE-2025-38087 Référence CVE CVE-2025-38088 https://www.cve.org/CVERecord?id=CVE-2025-38088 Référence CVE CVE-2025-38089 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-38004 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=CVE-2025-38051 Référence CVE CVE-2025-38052 https://www.cve.org/CVERecord?id=CVE-2025-38052 Référence CVE CVE-2025-38058 https://www.cve.org/CVERecord?id=CVE-2025-38058 Référence CVE CVE-2025-38061 https://www.cve.org/CVERecord?id=CVE-2025-38061 Référence CVE CVE-2025-38065 https://www.cve.org/CVERecord?id=CVE-2025-38065 Référence CVE CVE-2025-38066 https://www.cve.org/CVERecord?id=CVE-2025-38066 Référence CVE CVE-2025-38067 https://www.cve.org/CVERecord?id=CVE-2025-38067 Référence CVE CVE-2025-38068 https://www.cve.org/CVERecord?id=CVE-2025-38068 Référence CVE CVE-2025-38072 https://www.cve.org/CVERecord?id=CVE-2025-38072 Référence CVE CVE-2025-38074 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-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=CVE-2025-38048 Référence CVE CVE-2025-38051 https://www.cve.org/CVERecord?id=CVE-2025-38051 Référence CVE CVE-2025-38052 https://www.cve.org/CVERecord?id=CVE-2025-38052 Référence CVE CVE-2025-38058 https://www.cve.org/CVERecord?id=CVE-2025-38058 Référence CVE CVE-2025-38061 https://www.cve.org/CVERecord?id=CVE-2025-38061 Référence CVE CVE-2025-38062 https://www.cve.org/CVERecord?id=CVE-2025-38062 Référence CVE CVE-2025-38063 https://www.cve.org/CVERecord?id=CVE-2025-38063 Référence CVE CVE-2025-38065 https://www.cve.org/CVERecord?id=CVE-2025-38065 Référence CVE CVE-2025-38066 https://www.cve.org/CVERecord?id=CVE-2025-38066 Référence CVE CVE-2025-38067 https://www.cve.org/CVERecord?id=CVE-2025-38067 Référence CVE CVE-2025-38068 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38041 Référence CVE CVE-2025-38042 https://www.cve.org/CVERecord?id=CVE-2025-38042 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-38047 https://www.cve.org/CVERecord?id=CVE-2025-38047 Référence CVE CVE-2025-38048 https://www.cve.org/CVERecord?id=CVE-2025-38048 Référence CVE CVE-2025-38050 https://www.cve.org/CVERecord?id=CVE-2025-38050 Référence CVE CVE-2025-38051 https://www.cve.org/CVERecord?id=CVE-2025-38051 Référence CVE CVE-2025-38052 https://www.cve.org/CVERecord?id=CVE-2025-38052 Référence CVE CVE-2025-38053 https://www.cve.org/CVERecord?id=CVE-2025-38053 Référence CVE CVE-2025-38054 https://www.cve.org/CVERecord?id=CVE-2025-38054 Référence CVE CVE-2025-38055 https://www.cve.org/CVERecord?id=CVE-2025-38055 Référence CVE CVE-2025-38057 https://www.cve.org/CVERecord?id=CVE-2025-38057 Référence CVE CVE-2025-38058 https://www.cve.org/CVERecord?id=CVE-2025-38058 Référence CVE CVE-2025-38059 https://www.cve.org/CVERecord?id=CVE-2025-38059 Référence CVE CVE-2025-38060 https://www.cve.org/CVERecord?id=CVE-2025-38060 Référence CVE CVE-2025-38061 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38041 Référence CVE CVE-2025-38042 https://www.cve.org/CVERecord?id=CVE-2025-38042 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-38047 https://www.cve.org/CVERecord?id=CVE-2025-38047 Référence CVE CVE-2025-38048 https://www.cve.org/CVERecord?id=CVE-2025-38048 Référence CVE CVE-2025-38050 https://www.cve.org/CVERecord?id=CVE-2025-38050 Référence CVE CVE-2025-38051 https://www.cve.org/CVERecord?id=CVE-2025-38051 Référence CVE CVE-2025-38052 https://www.cve.org/CVERecord?id=CVE-2025-38052 Référence CVE CVE-2025-38053 https://www.cve.org/CVERecord?id=CVE-2025-38053 Référence CVE CVE-2025-38054 https://www.cve.org/CVERecord?id=CVE-2025-38054 Référence CVE CVE-2025-38055 https://www.cve.org/CVERecord?id=CVE-2025-38055 Référence CVE CVE-2025-38057 https://www.cve.org/CVERecord?id=CVE-2025-38057 Référence CVE CVE-2025-38058 https://www.cve.org/CVERecord?id=CVE-2025-38058 Référence CVE CVE-2025-38059 https://www.cve.org/CVERecord?id=CVE-2025-38059 Référence CVE CVE-2025-38060 https://www.cve.org/CVERecord?id=CVE-2025-38060 Référence CVE CVE-2025-38061 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38041 Référence CVE CVE-2025-38042 https://www.cve.org/CVERecord?id=CVE-2025-38042 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-38047 https://www.cve.org/CVERecord?id=CVE-2025-38047 Référence CVE CVE-2025-38048 https://www.cve.org/CVERecord?id=CVE-2025-38048 Référence CVE CVE-2025-38050 https://www.cve.org/CVERecord?id=CVE-2025-38050 Référence CVE CVE-2025-38051 https://www.cve.org/CVERecord?id=CVE-2025-38051 Référence CVE CVE-2025-38052 https://www.cve.org/CVERecord?id=CVE-2025-38052 Référence CVE CVE-2025-38053 https://www.cve.org/CVERecord?id=CVE-2025-38053 Référence CVE CVE-2025-38054 https://www.cve.org/CVERecord?id=CVE-2025-38054 Référence CVE CVE-2025-38055 https://www.cve.org/CVERecord?id=CVE-2025-38055 Référence CVE CVE-2025-38057 https://www.cve.org/CVERecord?id=CVE-2025-38057 Référence CVE CVE-2025-38058 https://www.cve.org/CVERecord?id=CVE-2025-38058 Référence CVE CVE-2025-38059 https://www.cve.org/CVERecord?id=CVE-2025-38059 Référence CVE CVE-2025-38060 https://www.cve.org/CVERecord?id=CVE-2025-38060 Référence CVE CVE-2025-38061 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-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=CVE-2025-38051 Référence CVE CVE-2025-38052 https://www.cve.org/CVERecord?id=CVE-2025-38052 Référence CVE CVE-2025-38058 https://www.cve.org/CVERecord?id=CVE-2025-38058 Référence CVE CVE-2025-38061 https://www.cve.org/CVERecord?id=CVE-2025-38061 Référence CVE CVE-2025-38065 https://www.cve.org/CVERecord?id=CVE-2025-38065 Référence CVE CVE-2025-38066 https://www.cve.org/CVERecord?id=CVE-2025-38066 Référence CVE CVE-2025-38068 https://www.cve.org/CVERecord?id=CVE-2025-38068 Référence CVE CVE-2025-38072 https://www.cve.org/CVERecord?id=CVE-2025-38072 Référence CVE CVE-2025-38075 https://www.cve.org/CVERecord?id=CVE-2025-38075 Référence CVE CVE-2025-38077 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-37798 Référence CVE CVE-2025-37856 https://www.cve.org/CVERecord?id=CVE-2025-37856 Référence CVE CVE-2025-37864 https://www.cve.org/CVERecord?id=CVE-2025-37864 Référence CVE CVE-2025-37885 https://www.cve.org/CVERecord?id=CVE-2025-37885 Référence CVE CVE-2025-37920 https://www.cve.org/CVERecord?id=CVE-2025-37920 Référence CVE CVE-2025-37984 https://www.cve.org/CVERecord?id=CVE-2025-37984 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-38051 https://www.cve.org/CVERecord?id=CVE-2025-38051 Référence CVE CVE-2025-38052 https://www.cve.org/CVERecord?id=CVE-2025-38052 Référence CVE CVE-2025-38058 https://www.cve.org/CVERecord?id=CVE-2025-38058 Référence CVE CVE-2025-38061 https://www.cve.org/CVERecord?id=CVE-2025-38061 Référence CVE CVE-2025-38062 https://www.cve.org/CVERecord?id=CVE-2025-38062 Référence CVE CVE-2025-38063 https://www.cve.org/CVERecord?id=CVE-2025-38063 Référence CVE CVE-2025-38064 https://www.cve.org/CVERecord?id=CVE-2025-38064 Référence CVE CVE-2025-38074 https://www.cve.org/CVERecord?id=CVE-2025-38074 Référence CVE CVE-2025-38084 https://www.cve.org/CVERecord?id=CVE-2025-38084 Référence CVE CVE-2025-38085 https://www.cve.org/CVERecord?id=

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

ord?id=CVE-2025-27614 Référence CVE CVE-2025-2900 https://www.cve.org/CVERecord?id=CVE-2025-2900 Référence CVE CVE-2025-30698 https://www.cve.org/CVERecord?id=CVE-2025-30698 Référence CVE CVE-2025-30749 https://www.cve.org/CVERecord?id=CVE-2025-30749 Référence CVE CVE-2025-30754 https://www.cve.org/CVERecord?id=CVE-2025-30754 Référence CVE CVE-2025-30761 https://www.cve.org/CVERecord?id=CVE-2025-30761 Référence CVE CVE-2025-32415 https://www.cve.org/CVERecord?id=CVE-2025-32415 Référence CVE CVE-2025-37738 https://www.cve.org/CVERecord?id=CVE-2025-37738 Référence CVE CVE-2025-37890 https://www.cve.org/CVERecord?id=CVE-2025-37890 Référence CVE CVE-2025-38052 https://www.cve.org/CVERecord?id=CVE-2025-38052 Référence CVE CVE-2025-38079 https://www.cve.org/CVERecord?id=CVE-2025-38079 Référence CVE CVE-2025-38086 https://www.cve.org/CVERecord?id=CVE-2025-38086 Référence CVE CVE-2025-4373 https://www.cve.org/CVERecord?id=CVE-2025-4373 Référence CVE CVE-2025-4447 https://www.cve.org/CVERecord?id=CVE-2025-4447 Référence CVE CVE-2025-46835 https://www.cve.org/CVERecord?id=CVE-2025-46835 Référence CVE CVE-2025-47273 https://www.cve.org/CVERecord?id=CVE-2025-47273 Référence CVE CVE-2025-47935 https://www.cve.org/CVERecord?id=CVE-2025-47935 Référence CVE CVE-2025-47944 https://www.cve.org/CVERecord?id=CVE-

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

d?id=CVE-2025-37856 Référence CVE CVE-2025-37864 https://www.cve.org/CVERecord?id=CVE-2025-37864 Référence CVE CVE-2025-37885 https://www.cve.org/CVERecord?id=CVE-2025-37885 Référence CVE CVE-2025-37920 https://www.cve.org/CVERecord?id=CVE-2025-37920 Référence CVE CVE-2025-37984 https://www.cve.org/CVERecord?id=CVE-2025-37984 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-38047 https://www.cve.org/CVERecord?id=CVE-2025-38047 Référence CVE CVE-2025-38051 https://www.cve.org/CVERecord?id=CVE-2025-38051 Référence CVE CVE-2025-38052 https://www.cve.org/CVERecord?id=CVE-2025-38052 Référence CVE CVE-2025-38058 https://www.cve.org/CVERecord?id=CVE-2025-38058 Référence CVE CVE-2025-38061 https://www.cve.org/CVERecord?id=CVE-2025-38061 Référence CVE CVE-2025-38062 https://www.cve.org/CVERecord?id=CVE-2025-38062 Référence CVE CVE-2025-38063 https://www.cve.org/CVERecord?id=CVE-2025-38063 Référence CVE CVE-2025-38064 https://www.cve.org/CVERecord?id=CVE-2025-38064 Référence CVE CVE-2025-38074 https://www.cve.org/CVERecord?id=CVE-2025-38074 Référence CVE CVE-2025-38084 https://www.cve.org/CVERecord?id=CVE-2025-38084 Référence CVE CVE-2025-38085 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-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=CVE-2025-38051 Référence CVE CVE-2025-38052 https://www.cve.org/CVERecord?id=CVE-2025-38052 Référence CVE CVE-2025-38058 https://www.cve.org/CVERecord?id=CVE-2025-38058 Référence CVE CVE-2025-38061 https://www.cve.org/CVERecord?id=CVE-2025-38061 Référence CVE CVE-2025-38065 https://www.cve.org/CVERecord?id=CVE-2025-38065 Référence CVE CVE-2025-38066 https://www.cve.org/CVERecord?id=CVE-2025-38066 Référence CVE CVE-2025-38068 https://www.cve.org/CVERecord?id=CVE-2025-38068 Référence CVE CVE-2025-38072 https://www.cve.org/CVERecord?id=CVE-2025-38072 Référence CVE CVE-2025-38075 https://www.cve.org/CVERecord?id=CVE-2025-38075 Référence CVE CVE-2025-38077 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-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=CVE-2025-38045 Référence CVE CVE-2025-38047 https://www.cve.org/CVERecord?id=CVE-2025-38047 Référence CVE CVE-2025-38051 https://www.cve.org/CVERecord?id=CVE-2025-38051 Référence CVE CVE-2025-38052 https://www.cve.org/CVERecord?id=CVE-2025-38052 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=CVE-2025-38057 Référence CVE CVE-2025-38058 https://www.cve.org/CVERecord?id=CVE-2025-38058 Référence CVE CVE-2025-38059 https://www.cve.org/CVERecord?id=CVE-2025-38059 Référence CVE CVE-2025-38060 https://www.cve.org/CVERecord?id=CVE-2025-38060 Référence CVE CVE-2025-38061 https://www.cve.org/CVERecord?id=CVE-2025-38061 Référence CVE CVE-2025-38062 https://www.cve.org/CVERecord?id=CVE-2025-38062 Référence CVE CVE-2025-38063 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-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=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=CVE-2025-38051 Référence CVE CVE-2025-38052 https://www.cve.org/CVERecord?id=CVE-2025-38052 Référence CVE CVE-2025-38056 https://www.cve.org/CVERecord?id=CVE-2025-38056 Référence CVE CVE-2025-38058 https://www.cve.org/CVERecord?id=CVE-2025-38058 Référence CVE CVE-2025-38061 https://www.cve.org/CVERecord?id=CVE-2025-38061 Référence CVE CVE-2025-38065 https://www.cve.org/CVERecord?id=CVE-2025-38065 Référence CVE CVE-2025-38066 https://www.cve.org/CVERecord?id=CVE-2025-38066 Référence CVE CVE-2025-38068 https://www.cve.org/CVERecord?id=CVE-2025-38068 Référence CVE CVE-2025-38072 https://www.cve.org/CVERecord?id=CVE-2025-38072 Référence CVE CVE-2025-38075 https://www.cve.org/CVERecord?id=

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

d?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=CVE-2025-38048 Référence CVE CVE-2025-38051 https://www.cve.org/CVERecord?id=CVE-2025-38051 Référence CVE CVE-2025-38052 https://www.cve.org/CVERecord?id=CVE-2025-38052 Référence CVE CVE-2025-38058 https://www.cve.org/CVERecord?id=CVE-2025-38058 Référence CVE CVE-2025-38061 https://www.cve.org/CVERecord?id=CVE-2025-38061 Référence CVE CVE-2025-38062 https://www.cve.org/CVERecord?id=CVE-2025-38062 Référence CVE CVE-2025-38063 https://www.cve.org/CVERecord?id=CVE-2025-38063 Référence CVE CVE-2025-38065 https://www.cve.org/CVERecord?id=CVE-2025-38065 Référence CVE CVE-2025-38066 https://www.cve.org/CVERecord?id=CVE-2025-38066 Référence CVE CVE-2025-38067 https://www.cve.org/CVERecord?id=CVE-2025-38067 Référence CVE CVE-2025-38068 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0699Multiples 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 atteinte à la confidentialité des données, un contournement de la politique de sécurité et un déni de service.

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

d?id=CVE-2025-21991 Référence CVE CVE-2025-22004 https://www.cve.org/CVERecord?id=CVE-2025-22004 Référence CVE CVE-2025-22020 https://www.cve.org/CVERecord?id=CVE-2025-22020 Référence CVE CVE-2025-22085 https://www.cve.org/CVERecord?id=CVE-2025-22085 Référence CVE CVE-2025-22113 https://www.cve.org/CVERecord?id=CVE-2025-22113 Référence CVE CVE-2025-23150 https://www.cve.org/CVERecord?id=CVE-2025-23150 Référence CVE CVE-2025-37738 https://www.cve.org/CVERecord?id=CVE-2025-37738 Référence CVE CVE-2025-37890 https://www.cve.org/CVERecord?id=CVE-2025-37890 Référence CVE CVE-2025-37958 https://www.cve.org/CVERecord?id=CVE-2025-37958 Référence CVE CVE-2025-38052 https://www.cve.org/CVERecord?id=CVE-2025-38052 Référence CVE CVE-2025-38079 https://www.cve.org/CVERecord?id=CVE-2025-38079 Référence CVE CVE-2025-38086 https://www.cve.org/CVERecord?id=CVE-2025-38086 Référence CVE CVE-2025-38087 https://www.cve.org/CVERecord?id=CVE-2025-38087 Référence CVE CVE-2025-38264 https://www.cve.org/CVERecord?id=CVE-2025-38264 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

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

d?id=CVE-2025-22091 Référence CVE CVE-2025-22104 https://www.cve.org/CVERecord?id=CVE-2025-22104 Référence CVE CVE-2025-22113 https://www.cve.org/CVERecord?id=CVE-2025-22113 Référence CVE CVE-2025-22121 https://www.cve.org/CVERecord?id=CVE-2025-22121 Référence CVE CVE-2025-37738 https://www.cve.org/CVERecord?id=CVE-2025-37738 Référence CVE CVE-2025-37797 https://www.cve.org/CVERecord?id=CVE-2025-37797 Référence CVE CVE-2025-37803 https://www.cve.org/CVERecord?id=CVE-2025-37803 Référence CVE CVE-2025-37958 https://www.cve.org/CVERecord?id=CVE-2025-37958 Référence CVE CVE-2025-38001 https://www.cve.org/CVERecord?id=CVE-2025-38001 Référence CVE CVE-2025-38052 https://www.cve.org/CVERecord?id=CVE-2025-38052 Référence CVE CVE-2025-38086 https://www.cve.org/CVERecord?id=CVE-2025-38086 Référence CVE CVE-2025-38087 https://www.cve.org/CVERecord?id=CVE-2025-38087 Référence CVE CVE-2025-38088 https://www.cve.org/CVERecord?id=CVE-2025-38088 Référence CVE CVE-2025-38089 https://www.cve.org/CVERecord?id=CVE-2025-38089 Référence CVE CVE-2025-38110 https://www.cve.org/CVERecord?id=CVE-2025-38110 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.f

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2025-022701Linux の 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
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. If business-safe, reduce exposure to the affected interface and allow only trusted sources 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-18601
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
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-18601↗Vendor CSAF · Red Hat Product Security↗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-38052 · cve.blacktree.nl