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

net/sched: Return NULL when htb_lookup_leaf encounters an empty rbtree

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Scheduled

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

Patch available
Distribution package intelligence

Ubuntu vendor package status

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

21 package states
Repository candidate not checked

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

Ubuntu releaseSource packageVendor stateFixed versionEvidence
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-tegraAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 11 Sept 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
SSA-082556 · CSAF 2.0 · revision 7 · interimSiemens ProductCERTSSA-082556: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP V3.1.5
5 known affected

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

  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0) >= V3.1.5
  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0) >= V3.1.5
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0) >= V3.1.5
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0) >= V3.1.5
  • SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0) >= V3.1.5
Summary
In the Linux kernel, the following vulnerability has been resolved: net/sched: Return NULL when htb_lookup_leaf encounters an empty rbtree htb_lookup_leaf has a BUG_ON that can trigger with the following: tc qdisc del dev lo root tc qdisc add dev lo root handle 1: htb default 1 tc class add dev lo parent 1: classid 1:1 htb rate 64bit tc qdisc add dev lo parent 1:1 handle 2: netem tc qdisc add dev lo parent 2:1 handle 3: blackhole ping -I lo -c1 -W0.001 127.0.0.1 The root cause is the following: 1. htb_dequeue calls htb_dequeue_tree which calls the dequeue handler on the selected leaf qdisc 2. netem_dequeue calls enqueue on the child qdisc 3. blackhole_enqueue drops the packet and returns a value that is not just NET_XMIT_SUCCESS 4. Because of this, netem_dequeue calls qdisc_tree_reduce_backlog, and since qlen is now 0, it calls htb_qlen_notify -> htb_deactivate -> htb_deactiviate_prios -> htb_remove_class_from_row -> htb_safe_rb_erase 5. As this is the only class in the selected hprio rbtree, __rb_change_child in __rb_erase_augmented sets the rb_root pointer to NULL 6. Because blackhole_dequeue returns NULL, netem_dequeue returns NULL, which causes htb_dequeue_tree to call htb_lookup_leaf with the same hprio rbtree, and fail the BUG_ON The function graph for this scenario is shown here: 0) | htb_enqueue() { 0) + 13.635 us | netem_enqueue(); 0) 4.719 us | htb_activate_prios(); 0) # 2249.199 us | } 0) | htb_dequeue() { 0) 2.355 us | htb_lookup_leaf(); 0) | netem_dequeue() { 0) + 11.061 us | blackhole_enqueue(); 0) | qdisc_tree_reduce_backlog() { 0) | qdisc_lookup_rcu() { 0) 1.873 us | qdisc_match_from_root(); 0) 6.292 us | } 0) 1.894 us | htb_search(); 0) | htb_qlen_notify() { 0) 2.655 us | htb_deactivate_prios(); 0) 6.933 us | } 0) + 25.227 us | } 0) 1.983 us | blackhole_dequeue(); 0) + 86.553 us | } 0) # 2932.761 us | qdisc_warn_nonwc(); 0) | htb_lookup_leaf() { 0) | BUG_ON(); ------------------------------------------ The full original bug report can be seen here [1]. We can fix this just by returning NULL instead of the BUG_ON, as htb_dequeue_tree returns NULL when htb_lookup_leaf returns NULL. [1] https://lore.kernel.org/netdev/pF5XOOIim0IuEfhI-SOxTgRvNoDwuux7UHKnE_Y5-zVd4wmGvNk2ceHjKb8ORnzw0cGwfmVu42g9dL7XyJLf1NEzaztboTWcm0Ogxuojoeo=@willsroot.io/
Remediation
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
Optional official sources

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

Select the national-authority views to include. The exact source language is shown on each matched advisory. Your choice is remembered on this device and encoded in the shareable URL.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2025-22894

No EUVD known-exploited evidence

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

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

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

Patch available
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: net/sched: Return NULL when htb_lookup_leaf encounters an empty rbtree htb_lookup_leaf has a BUG_ON that can trigger with the following: tc qdisc del dev lo root tc qdisc add dev lo root handle 1: htb default 1 tc class add dev lo parent 1: classid 1:1 htb rate 64bit tc qdisc add dev lo parent 1:1 handle 2: netem tc qdisc add dev lo parent 2:1 handle 3: blackhole ping -I lo -c1 -W0.001 127.0.0.1 The root cause is the following: 1. htb_dequeue calls htb_dequeue_tree which calls the dequeue handler on the selected leaf qdisc 2. netem_dequeue calls enqueue on the child qdisc 3. blackhole_enqueue drops the packet and returns a value that is not just NET_XMIT_SUCCESS 4. Because of this, netem_dequeue calls qdisc_tree_reduce_backlog, and since qlen is now 0, it calls htb_qlen_notify -> htb_deactivate -> htb_deactiviate_prios -> htb_remove_class_from_row -> htb_safe_rb_erase 5. As this is the only class in the selected hprio rbtree, __rb_change_child in __rb_erase_augmented sets the rb_root pointer to NULL 6. Because blackhole_dequeue returns NULL, netem_dequeue returns NULL, which causes htb_dequeue_tree to call htb_lookup_leaf with the same hprio rbtree, and fail the BUG_ON The function graph for this scenario is shown here: 0) | htb_enqueue() { 0) + 13.635 us | netem_enqueue(); 0) 4.719 us | htb_activate_prios(); 0) # 2249.199 us | } 0) | htb_dequeue() { 0) 2.355 us | htb_lookup_leaf(); 0) | netem_dequeue() { 0) + 11.061 us | blackhole_enqueue(); 0) | qdisc_tree_reduce_backlog() { 0) | qdisc_lookup_rcu() { 0) 1.873 us | qdisc_match_from_root(); 0) 6.292 us | } 0) 1.894 us | htb_search(); 0) | htb_qlen_notify() { 0) 2.655 us | htb_deactivate_prios(); 0) 6.933 us | } 0) + 25.227 us | } 0) 1.983 us | blackhole_dequeue(); 0) + 86.553 us | } 0) # 2932.761 us | qdisc_warn_nonwc(); 0) | htb_lookup_leaf() { 0) | BUG_ON(); ------------------------------------------ The full original bug report can be seen here [1]. We can fix this just by returning NULL instead of the BUG_ON, as htb_dequeue_tree returns NULL when htb_lookup_leaf returns NULL. [1] https://lore.kernel.org/netdev/pF5XOOIim0IuEfhI-SOxTgRvNoDwuux7UHKnE_Y5-zVd4wmGvNk2ceHjKb8ORnzw0cGwfmVu42g9dL7XyJLf1NEzaztboTWcm0Ogxuojoeo=@willsroot.io/

What

In the Linux kernel, the following vulnerability has been resolved: net/sched: Return NULL when htb_lookup_leaf encounters an empty rbtree htb_lookup_leaf has a BUG_ON that can trigger with the following: tc qdisc del dev lo root tc qdisc add dev lo root handle 1: htb default 1 tc class add dev lo parent 1: classid 1:1 htb rate 64bit tc qdisc add dev lo parent 1:1 handle 2: netem tc qdisc add dev lo parent 2:1 handle 3: blackhole ping -I lo -c1 -W0.001 127.0.0.1 The root cause is the following: 1. htb_dequeue calls htb_dequeue_tree which calls the dequeue handler on the selected leaf qdisc 2. netem_dequeue calls enqueue on the child qdisc 3. blackhole_enqueue drops the packet and returns a value that is not just NET_XMIT_SUCCESS 4. Because of this, netem_dequeue calls qdisc_tree_reduce_backlog, and since qlen is now 0, it calls htb_qlen_notify -> htb_deactivate -> htb_deactiviate_prios -> htb_remove_class_from_row -> htb_safe_rb_erase 5. As this is the only class in the selected hprio rbtree, __rb_change_child in __rb_erase_augmented sets the rb_root pointer to NULL 6. Because blackhole_dequeue returns NULL, netem_dequeue returns NULL, which causes htb_dequeue_tree to call htb_lookup_leaf with the same hprio rbtree, and fail the BUG_ON The function graph for this scenario is shown here: 0) | htb_enqueue() { 0) + 13.635 us | netem_enqueue(); 0) 4.719 us | htb_activate_prios(); 0) # 2249.199 us | } 0) | htb_dequeue() { 0) 2.355 us | htb_lookup_leaf(); 0) | netem_dequeue() { 0) + 11.061 us | blackhole_enqueue(); 0) | qdisc_tree_reduce_backlog() { 0) | qdisc_lookup_rcu() { 0) 1.873 us | qdisc_match_from_root(); 0) 6.292 us | } 0) 1.894 us | htb_search(); 0) | htb_qlen_notify() { 0) 2.655 us | htb_deactivate_prios(); 0) 6.933 us | } 0) + 25.227 us | } 0) 1.983 us | blackhole_dequeue(); 0) + 86.553 us | } 0) # 2932.761 us | qdisc_warn_nonwc(); 0) | htb_lookup_leaf() { 0) | BUG_ON(); ------------------------------------------ The full original bug report can be seen here [1]. We can fix this just by returning NULL instead of the BUG_ON, as htb_dequeue_tree returns NULL when htb_lookup_leaf returns NULL. [1] https://lore.kernel.org/netdev/pF5XOOIim0IuEfhI-SOxTgRvNoDwuux7UHKnE_Y5-zVd4wmGvNk2ceHjKb8ORnzw0cGwfmVu42g9dL7XyJLf1NEzaztboTWcm0Ogxuojoeo=@willsroot.io/

Why

The product dereferences a pointer that it expects to be valid but is NULL.

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: net/sched: Return NULL when htb_lookup_leaf encounters an empty rbtree htb_lookup_leaf has a BUG_ON that can trigger with the following: tc qdisc del dev lo root tc qdisc add dev lo root handle 1: htb default 1 tc class add dev lo parent 1: classid 1:1 htb rate 64bit tc qdisc add dev lo parent 1:1 handle 2: netem tc qdisc add dev lo parent 2:1 handle 3: blackhole ping -I lo -c1 -W0.001 127.0.0.1 The root cause is the following: 1. htb_dequeue calls htb_dequeue_tree which calls the dequeue handler on the selected leaf qdisc 2. netem_dequeue calls enqueue on the child qdisc 3. blackhole_enqueue drops the packet and returns a value that is not just NET_XMIT_SUCCESS 4. Because of this, netem_dequeue calls qdisc_tree_reduce_backlog, and since qlen is now 0, it calls htb_qlen_notify -> htb_deactivate -> htb_deactiviate_prios -> htb_remove_class_from_row -> htb_safe_rb_erase 5. As this is the only class in the selected hprio rbtree, __rb_change_child in __rb_erase_augmented sets the rb_root pointer to NULL 6. Because blackhole_dequeue returns NULL, netem_dequeue returns NULL, which causes htb_dequeue_tree to call htb_lookup_leaf with the same hprio rbtree, and fail the BUG_ON The function graph for this scenario is shown here: 0) | htb_enqueue() { 0) + 13.635 us | netem_enqueue(); 0) 4.719 us | htb_activate_prios(); 0) # 2249.199 us | } 0) | htb_dequeue() { 0) 2.355 us | htb_lookup_leaf(); 0) | netem_dequeue() { 0) + 11.061 us | blackhole_enqueue(); 0) | qdisc_tree_reduce_backlog() { 0) | qdisc_lookup_rcu() { 0) 1.873 us | qdisc_match_from_root(); 0) 6.292 us | } 0) 1.894 us | htb_search(); 0) | htb_qlen_notify() { 0) 2.655 us | htb_deactivate_prios(); 0) 6.933 us | } 0) + 25.227 us | } 0) 1.983 us | blackhole_dequeue(); 0) + 86.553 us | } 0) # 2932.761 us | qdisc_warn_nonwc(); 0) | htb_lookup_leaf() { 0) | BUG_ON(); ------------------------------------------ The full original bug report can be seen here [1]. We can fix this just by returning NULL instead of the BUG_ON, as htb_dequeue_tree returns NULL when htb_lookup_leaf returns NULL. [1] https://lore.kernel.org/netdev/pF5XOOIim0IuEfhI-SOxTgRvNoDwuux7UHKnE_Y5-zVd4wmGvNk2ceHjKb8ORnzw0cGwfmVu42g9dL7XyJLf1NEzaztboTWcm0Ogxuojoeo=@willsroot.io/

Why

The product dereferences a pointer that it expects to be valid but is NULL.

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 → NULL Pointer Dereference → 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-476

CWE-476: NULL Pointer Dereference. The product dereferences a pointer that it expects to be valid but is NULL.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

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

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
CWE-476
A

Official authority intelligence

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

BSI · German · WID-SEC-2025-1665Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere nicht spezifizierte Angriffe durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20250730Security Bulletin 30 Jul 2025 [827KB]

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 30 Jul 2025 [827KB], published on 30 July 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-38459 Référence CVE CVE-2025-38460 https://www.cve.org/CVERecord?id=CVE-2025-38460 Référence CVE CVE-2025-38461 https://www.cve.org/CVERecord?id=CVE-2025-38461 Référence CVE CVE-2025-38462 https://www.cve.org/CVERecord?id=CVE-2025-38462 Référence CVE CVE-2025-38463 https://www.cve.org/CVERecord?id=CVE-2025-38463 Référence CVE CVE-2025-38464 https://www.cve.org/CVERecord?id=CVE-2025-38464 Référence CVE CVE-2025-38465 https://www.cve.org/CVERecord?id=CVE-2025-38465 Référence CVE CVE-2025-38466 https://www.cve.org/CVERecord?id=CVE-2025-38466 Référence CVE CVE-2025-38467 https://www.cve.org/CVERecord?id=CVE-2025-38467 Référence CVE CVE-2025-38468 https://www.cve.org/CVERecord?id=CVE-2025-38468 Référence CVE CVE-2025-38469 https://www.cve.org/CVERecord?id=CVE-2025-38469 Référence CVE CVE-2025-38470 https://www.cve.org/CVERecord?id=CVE-2025-38470 Référence CVE CVE-2025-38471 https://www.cve.org/CVERecord?id=CVE-2025-38471 Référence CVE CVE-2025-38472 https://www.cve.org/CVERecord?id=CVE-2025-38472 Référence CVE CVE-2025-38473 https://www.cve.org/CVERecord?id=CVE-2025-38473 Référence CVE CVE-2025-38474 https://www.cve.org/CVERecord?id=CVE-2025-38474 Référence CVE CVE-2025-38476 https://www.cve.org/CVERecord?id=CVE-2025-38476 Référence CVE CVE-2025-38478 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-38459 Référence CVE CVE-2025-38460 https://www.cve.org/CVERecord?id=CVE-2025-38460 Référence CVE CVE-2025-38461 https://www.cve.org/CVERecord?id=CVE-2025-38461 Référence CVE CVE-2025-38462 https://www.cve.org/CVERecord?id=CVE-2025-38462 Référence CVE CVE-2025-38463 https://www.cve.org/CVERecord?id=CVE-2025-38463 Référence CVE CVE-2025-38464 https://www.cve.org/CVERecord?id=CVE-2025-38464 Référence CVE CVE-2025-38465 https://www.cve.org/CVERecord?id=CVE-2025-38465 Référence CVE CVE-2025-38466 https://www.cve.org/CVERecord?id=CVE-2025-38466 Référence CVE CVE-2025-38467 https://www.cve.org/CVERecord?id=CVE-2025-38467 Référence CVE CVE-2025-38468 https://www.cve.org/CVERecord?id=CVE-2025-38468 Référence CVE CVE-2025-38469 https://www.cve.org/CVERecord?id=CVE-2025-38469 Référence CVE CVE-2025-38470 https://www.cve.org/CVERecord?id=CVE-2025-38470 Référence CVE CVE-2025-38471 https://www.cve.org/CVERecord?id=CVE-2025-38471 Référence CVE CVE-2025-38472 https://www.cve.org/CVERecord?id=CVE-2025-38472 Référence CVE CVE-2025-38473 https://www.cve.org/CVERecord?id=CVE-2025-38473 Référence CVE CVE-2025-38474 https://www.cve.org/CVERecord?id=CVE-2025-38474 Référence CVE CVE-2025-38476 https://www.cve.org/CVERecord?id=CVE-2025-38476 Référence CVE CVE-2025-38478 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-38459 Référence CVE CVE-2025-38460 https://www.cve.org/CVERecord?id=CVE-2025-38460 Référence CVE CVE-2025-38461 https://www.cve.org/CVERecord?id=CVE-2025-38461 Référence CVE CVE-2025-38462 https://www.cve.org/CVERecord?id=CVE-2025-38462 Référence CVE CVE-2025-38463 https://www.cve.org/CVERecord?id=CVE-2025-38463 Référence CVE CVE-2025-38464 https://www.cve.org/CVERecord?id=CVE-2025-38464 Référence CVE CVE-2025-38465 https://www.cve.org/CVERecord?id=CVE-2025-38465 Référence CVE CVE-2025-38466 https://www.cve.org/CVERecord?id=CVE-2025-38466 Référence CVE CVE-2025-38467 https://www.cve.org/CVERecord?id=CVE-2025-38467 Référence CVE CVE-2025-38468 https://www.cve.org/CVERecord?id=CVE-2025-38468 Référence CVE CVE-2025-38469 https://www.cve.org/CVERecord?id=CVE-2025-38469 Référence CVE CVE-2025-38470 https://www.cve.org/CVERecord?id=CVE-2025-38470 Référence CVE CVE-2025-38471 https://www.cve.org/CVERecord?id=CVE-2025-38471 Référence CVE CVE-2025-38472 https://www.cve.org/CVERecord?id=CVE-2025-38472 Référence CVE CVE-2025-38473 https://www.cve.org/CVERecord?id=CVE-2025-38473 Référence CVE CVE-2025-38474 https://www.cve.org/CVERecord?id=CVE-2025-38474 Référence CVE CVE-2025-38476 https://www.cve.org/CVERecord?id=CVE-2025-38476 Référence CVE CVE-2025-38478 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-38459 Référence CVE CVE-2025-38460 https://www.cve.org/CVERecord?id=CVE-2025-38460 Référence CVE CVE-2025-38461 https://www.cve.org/CVERecord?id=CVE-2025-38461 Référence CVE CVE-2025-38462 https://www.cve.org/CVERecord?id=CVE-2025-38462 Référence CVE CVE-2025-38463 https://www.cve.org/CVERecord?id=CVE-2025-38463 Référence CVE CVE-2025-38464 https://www.cve.org/CVERecord?id=CVE-2025-38464 Référence CVE CVE-2025-38465 https://www.cve.org/CVERecord?id=CVE-2025-38465 Référence CVE CVE-2025-38466 https://www.cve.org/CVERecord?id=CVE-2025-38466 Référence CVE CVE-2025-38467 https://www.cve.org/CVERecord?id=CVE-2025-38467 Référence CVE CVE-2025-38468 https://www.cve.org/CVERecord?id=CVE-2025-38468 Référence CVE CVE-2025-38469 https://www.cve.org/CVERecord?id=CVE-2025-38469 Référence CVE CVE-2025-38470 https://www.cve.org/CVERecord?id=CVE-2025-38470 Référence CVE CVE-2025-38471 https://www.cve.org/CVERecord?id=CVE-2025-38471 Référence CVE CVE-2025-38472 https://www.cve.org/CVERecord?id=CVE-2025-38472 Référence CVE CVE-2025-38473 https://www.cve.org/CVERecord?id=CVE-2025-38473 Référence CVE CVE-2025-38474 https://www.cve.org/CVERecord?id=CVE-2025-38474 Référence CVE CVE-2025-38476 https://www.cve.org/CVERecord?id=CVE-2025-38476 Référence CVE CVE-2025-38478 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-38459 Référence CVE CVE-2025-38460 https://www.cve.org/CVERecord?id=CVE-2025-38460 Référence CVE CVE-2025-38461 https://www.cve.org/CVERecord?id=CVE-2025-38461 Référence CVE CVE-2025-38462 https://www.cve.org/CVERecord?id=CVE-2025-38462 Référence CVE CVE-2025-38463 https://www.cve.org/CVERecord?id=CVE-2025-38463 Référence CVE CVE-2025-38464 https://www.cve.org/CVERecord?id=CVE-2025-38464 Référence CVE CVE-2025-38465 https://www.cve.org/CVERecord?id=CVE-2025-38465 Référence CVE CVE-2025-38466 https://www.cve.org/CVERecord?id=CVE-2025-38466 Référence CVE CVE-2025-38467 https://www.cve.org/CVERecord?id=CVE-2025-38467 Référence CVE CVE-2025-38468 https://www.cve.org/CVERecord?id=CVE-2025-38468 Référence CVE CVE-2025-38469 https://www.cve.org/CVERecord?id=CVE-2025-38469 Référence CVE CVE-2025-38470 https://www.cve.org/CVERecord?id=CVE-2025-38470 Référence CVE CVE-2025-38471 https://www.cve.org/CVERecord?id=CVE-2025-38471 Référence CVE CVE-2025-38472 https://www.cve.org/CVERecord?id=CVE-2025-38472 Référence CVE CVE-2025-38473 https://www.cve.org/CVERecord?id=CVE-2025-38473 Référence CVE CVE-2025-38474 https://www.cve.org/CVERecord?id=CVE-2025-38474 Référence CVE CVE-2025-38476 https://www.cve.org/CVERecord?id=CVE-2025-38476 Référence CVE CVE-2025-38478 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38459 Référence CVE CVE-2025-38460 https://www.cve.org/CVERecord?id=CVE-2025-38460 Référence CVE CVE-2025-38461 https://www.cve.org/CVERecord?id=CVE-2025-38461 Référence CVE CVE-2025-38462 https://www.cve.org/CVERecord?id=CVE-2025-38462 Référence CVE CVE-2025-38463 https://www.cve.org/CVERecord?id=CVE-2025-38463 Référence CVE CVE-2025-38464 https://www.cve.org/CVERecord?id=CVE-2025-38464 Référence CVE CVE-2025-38465 https://www.cve.org/CVERecord?id=CVE-2025-38465 Référence CVE CVE-2025-38466 https://www.cve.org/CVERecord?id=CVE-2025-38466 Référence CVE CVE-2025-38467 https://www.cve.org/CVERecord?id=CVE-2025-38467 Référence CVE CVE-2025-38468 https://www.cve.org/CVERecord?id=CVE-2025-38468 Référence CVE CVE-2025-38469 https://www.cve.org/CVERecord?id=CVE-2025-38469 Référence CVE CVE-2025-38470 https://www.cve.org/CVERecord?id=CVE-2025-38470 Référence CVE CVE-2025-38471 https://www.cve.org/CVERecord?id=CVE-2025-38471 Référence CVE CVE-2025-38472 https://www.cve.org/CVERecord?id=CVE-2025-38472 Référence CVE CVE-2025-38473 https://www.cve.org/CVERecord?id=CVE-2025-38473 Référence CVE CVE-2025-38474 https://www.cve.org/CVERecord?id=CVE-2025-38474 Référence CVE CVE-2025-38475 https://www.cve.org/CVERecord?id=CVE-2025-38475 Référence CVE CVE-2025-38476 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-38459 Référence CVE CVE-2025-38460 https://www.cve.org/CVERecord?id=CVE-2025-38460 Référence CVE CVE-2025-38461 https://www.cve.org/CVERecord?id=CVE-2025-38461 Référence CVE CVE-2025-38462 https://www.cve.org/CVERecord?id=CVE-2025-38462 Référence CVE CVE-2025-38463 https://www.cve.org/CVERecord?id=CVE-2025-38463 Référence CVE CVE-2025-38464 https://www.cve.org/CVERecord?id=CVE-2025-38464 Référence CVE CVE-2025-38465 https://www.cve.org/CVERecord?id=CVE-2025-38465 Référence CVE CVE-2025-38466 https://www.cve.org/CVERecord?id=CVE-2025-38466 Référence CVE CVE-2025-38467 https://www.cve.org/CVERecord?id=CVE-2025-38467 Référence CVE CVE-2025-38468 https://www.cve.org/CVERecord?id=CVE-2025-38468 Référence CVE CVE-2025-38470 https://www.cve.org/CVERecord?id=CVE-2025-38470 Référence CVE CVE-2025-38472 https://www.cve.org/CVERecord?id=CVE-2025-38472 Référence CVE CVE-2025-38473 https://www.cve.org/CVERecord?id=CVE-2025-38473 Référence CVE CVE-2025-38474 https://www.cve.org/CVERecord?id=CVE-2025-38474 Référence CVE CVE-2025-38475 https://www.cve.org/CVERecord?id=CVE-2025-38475 Référence CVE CVE-2025-38476 https://www.cve.org/CVERecord?id=CVE-2025-38476 Référence CVE CVE-2025-38477 https://www.cve.org/CVERecord?id=CVE-2025-38477 Référence CVE CVE-2025-38478 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38459 Référence CVE CVE-2025-38460 https://www.cve.org/CVERecord?id=CVE-2025-38460 Référence CVE CVE-2025-38461 https://www.cve.org/CVERecord?id=CVE-2025-38461 Référence CVE CVE-2025-38462 https://www.cve.org/CVERecord?id=CVE-2025-38462 Référence CVE CVE-2025-38463 https://www.cve.org/CVERecord?id=CVE-2025-38463 Référence CVE CVE-2025-38464 https://www.cve.org/CVERecord?id=CVE-2025-38464 Référence CVE CVE-2025-38465 https://www.cve.org/CVERecord?id=CVE-2025-38465 Référence CVE CVE-2025-38466 https://www.cve.org/CVERecord?id=CVE-2025-38466 Référence CVE CVE-2025-38467 https://www.cve.org/CVERecord?id=CVE-2025-38467 Référence CVE CVE-2025-38468 https://www.cve.org/CVERecord?id=CVE-2025-38468 Référence CVE CVE-2025-38469 https://www.cve.org/CVERecord?id=CVE-2025-38469 Référence CVE CVE-2025-38470 https://www.cve.org/CVERecord?id=CVE-2025-38470 Référence CVE CVE-2025-38471 https://www.cve.org/CVERecord?id=CVE-2025-38471 Référence CVE CVE-2025-38472 https://www.cve.org/CVERecord?id=CVE-2025-38472 Référence CVE CVE-2025-38473 https://www.cve.org/CVERecord?id=CVE-2025-38473 Référence CVE CVE-2025-38474 https://www.cve.org/CVERecord?id=CVE-2025-38474 Référence CVE CVE-2025-38475 https://www.cve.org/CVERecord?id=CVE-2025-38475 Référence CVE CVE-2025-38476 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38459 Référence CVE CVE-2025-38460 https://www.cve.org/CVERecord?id=CVE-2025-38460 Référence CVE CVE-2025-38461 https://www.cve.org/CVERecord?id=CVE-2025-38461 Référence CVE CVE-2025-38462 https://www.cve.org/CVERecord?id=CVE-2025-38462 Référence CVE CVE-2025-38463 https://www.cve.org/CVERecord?id=CVE-2025-38463 Référence CVE CVE-2025-38464 https://www.cve.org/CVERecord?id=CVE-2025-38464 Référence CVE CVE-2025-38465 https://www.cve.org/CVERecord?id=CVE-2025-38465 Référence CVE CVE-2025-38466 https://www.cve.org/CVERecord?id=CVE-2025-38466 Référence CVE CVE-2025-38467 https://www.cve.org/CVERecord?id=CVE-2025-38467 Référence CVE CVE-2025-38468 https://www.cve.org/CVERecord?id=CVE-2025-38468 Référence CVE CVE-2025-38469 https://www.cve.org/CVERecord?id=CVE-2025-38469 Référence CVE CVE-2025-38470 https://www.cve.org/CVERecord?id=CVE-2025-38470 Référence CVE CVE-2025-38471 https://www.cve.org/CVERecord?id=CVE-2025-38471 Référence CVE CVE-2025-38472 https://www.cve.org/CVERecord?id=CVE-2025-38472 Référence CVE CVE-2025-38473 https://www.cve.org/CVERecord?id=CVE-2025-38473 Référence CVE CVE-2025-38474 https://www.cve.org/CVERecord?id=CVE-2025-38474 Référence CVE CVE-2025-38475 https://www.cve.org/CVERecord?id=CVE-2025-38475 Référence CVE CVE-2025-38476 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-38458 Référence CVE CVE-2025-38459 https://www.cve.org/CVERecord?id=CVE-2025-38459 Référence CVE CVE-2025-38460 https://www.cve.org/CVERecord?id=CVE-2025-38460 Référence CVE CVE-2025-38461 https://www.cve.org/CVERecord?id=CVE-2025-38461 Référence CVE CVE-2025-38462 https://www.cve.org/CVERecord?id=CVE-2025-38462 Référence CVE CVE-2025-38464 https://www.cve.org/CVERecord?id=CVE-2025-38464 Référence CVE CVE-2025-38465 https://www.cve.org/CVERecord?id=CVE-2025-38465 Référence CVE CVE-2025-38466 https://www.cve.org/CVERecord?id=CVE-2025-38466 Référence CVE CVE-2025-38467 https://www.cve.org/CVERecord?id=CVE-2025-38467 Référence CVE CVE-2025-38468 https://www.cve.org/CVERecord?id=CVE-2025-38468 Référence CVE CVE-2025-38470 https://www.cve.org/CVERecord?id=CVE-2025-38470 Référence CVE CVE-2025-38471 https://www.cve.org/CVERecord?id=CVE-2025-38471 Référence CVE CVE-2025-38472 https://www.cve.org/CVERecord?id=CVE-2025-38472 Référence CVE CVE-2025-38473 https://www.cve.org/CVERecord?id=CVE-2025-38473 Référence CVE CVE-2025-38474 https://www.cve.org/CVERecord?id=CVE-2025-38474 Référence CVE CVE-2025-38476 https://www.cve.org/CVERecord?id=CVE-2025-38476 Référence CVE CVE-2025-38477 https://www.cve.org/CVERecord?id=CVE-2025-38477 Référence CVE CVE-2025-38478 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38439 Référence CVE CVE-2025-38440 https://www.cve.org/CVERecord?id=CVE-2025-38440 Référence CVE CVE-2025-38441 https://www.cve.org/CVERecord?id=CVE-2025-38441 Référence CVE CVE-2025-38444 https://www.cve.org/CVERecord?id=CVE-2025-38444 Référence CVE CVE-2025-38445 https://www.cve.org/CVERecord?id=CVE-2025-38445 Référence CVE CVE-2025-38458 https://www.cve.org/CVERecord?id=CVE-2025-38458 Référence CVE CVE-2025-38459 https://www.cve.org/CVERecord?id=CVE-2025-38459 Référence CVE CVE-2025-38460 https://www.cve.org/CVERecord?id=CVE-2025-38460 Référence CVE CVE-2025-38464 https://www.cve.org/CVERecord?id=CVE-2025-38464 Référence CVE CVE-2025-38468 https://www.cve.org/CVERecord?id=CVE-2025-38468 Référence CVE CVE-2025-38472 https://www.cve.org/CVERecord?id=CVE-2025-38472 Référence CVE CVE-2025-38477 https://www.cve.org/CVERecord?id=CVE-2025-38477 Référence CVE CVE-2025-38490 https://www.cve.org/CVERecord?id=CVE-2025-38490 Référence CVE CVE-2025-38491 https://www.cve.org/CVERecord?id=CVE-2025-38491 Référence CVE CVE-2025-38498 https://www.cve.org/CVERecord?id=CVE-2025-38498 Référence CVE CVE-2025-38499 https://www.cve.org/CVERecord?id=CVE-2025-38499 Référence CVE CVE-2025-38500 https://www.cve.org/CVERecord?id=CVE-2025-38500 Référence CVE CVE-2025-38503 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38360 Référence CVE CVE-2025-38439 https://www.cve.org/CVERecord?id=CVE-2025-38439 Référence CVE CVE-2025-38441 https://www.cve.org/CVERecord?id=CVE-2025-38441 Référence CVE CVE-2025-38444 https://www.cve.org/CVERecord?id=CVE-2025-38444 Référence CVE CVE-2025-38445 https://www.cve.org/CVERecord?id=CVE-2025-38445 Référence CVE CVE-2025-38458 https://www.cve.org/CVERecord?id=CVE-2025-38458 Référence CVE CVE-2025-38459 https://www.cve.org/CVERecord?id=CVE-2025-38459 Référence CVE CVE-2025-38460 https://www.cve.org/CVERecord?id=CVE-2025-38460 Référence CVE CVE-2025-38464 https://www.cve.org/CVERecord?id=CVE-2025-38464 Référence CVE CVE-2025-38468 https://www.cve.org/CVERecord?id=CVE-2025-38468 Référence CVE CVE-2025-38472 https://www.cve.org/CVERecord?id=CVE-2025-38472 Référence CVE CVE-2025-38477 https://www.cve.org/CVERecord?id=CVE-2025-38477 Référence CVE CVE-2025-38490 https://www.cve.org/CVERecord?id=CVE-2025-38490 Référence CVE CVE-2025-38491 https://www.cve.org/CVERecord?id=CVE-2025-38491 Référence CVE CVE-2025-38494 https://www.cve.org/CVERecord?id=CVE-2025-38494 Référence CVE CVE-2025-38495 https://www.cve.org/CVERecord?id=CVE-2025-38495 Référence CVE CVE-2025-38497 https://www.cve.org/CVERecord?id=CVE-2025-38497 Référence CVE CVE-2025-38498 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-38449 Référence CVE CVE-2025-38455 https://www.cve.org/CVERecord?id=CVE-2025-38455 Référence CVE CVE-2025-38457 https://www.cve.org/CVERecord?id=CVE-2025-38457 Référence CVE CVE-2025-38460 https://www.cve.org/CVERecord?id=CVE-2025-38460 Référence CVE CVE-2025-38461 https://www.cve.org/CVERecord?id=CVE-2025-38461 Référence CVE CVE-2025-38462 https://www.cve.org/CVERecord?id=CVE-2025-38462 Référence CVE CVE-2025-38463 https://www.cve.org/CVERecord?id=CVE-2025-38463 Référence CVE CVE-2025-38465 https://www.cve.org/CVERecord?id=CVE-2025-38465 Référence CVE CVE-2025-38467 https://www.cve.org/CVERecord?id=CVE-2025-38467 Référence CVE CVE-2025-38468 https://www.cve.org/CVERecord?id=CVE-2025-38468 Référence CVE CVE-2025-38470 https://www.cve.org/CVERecord?id=CVE-2025-38470 Référence CVE CVE-2025-38471 https://www.cve.org/CVERecord?id=CVE-2025-38471 Référence CVE CVE-2025-38473 https://www.cve.org/CVERecord?id=CVE-2025-38473 Référence CVE CVE-2025-38474 https://www.cve.org/CVERecord?id=CVE-2025-38474 Référence CVE CVE-2025-38476 https://www.cve.org/CVERecord?id=CVE-2025-38476 Référence CVE CVE-2025-38477 https://www.cve.org/CVERecord?id=CVE-2025-38477 Référence CVE CVE-2025-38478 https://www.cve.org/CVERecord?id=CVE-2025-38478 Référence CVE CVE-2025-38480 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38453 Référence CVE CVE-2025-38455 https://www.cve.org/CVERecord?id=CVE-2025-38455 Référence CVE CVE-2025-38457 https://www.cve.org/CVERecord?id=CVE-2025-38457 Référence CVE CVE-2025-38460 https://www.cve.org/CVERecord?id=CVE-2025-38460 Référence CVE CVE-2025-38461 https://www.cve.org/CVERecord?id=CVE-2025-38461 Référence CVE CVE-2025-38462 https://www.cve.org/CVERecord?id=CVE-2025-38462 Référence CVE CVE-2025-38463 https://www.cve.org/CVERecord?id=CVE-2025-38463 Référence CVE CVE-2025-38465 https://www.cve.org/CVERecord?id=CVE-2025-38465 Référence CVE CVE-2025-38467 https://www.cve.org/CVERecord?id=CVE-2025-38467 Référence CVE CVE-2025-38468 https://www.cve.org/CVERecord?id=CVE-2025-38468 Référence CVE CVE-2025-38470 https://www.cve.org/CVERecord?id=CVE-2025-38470 Référence CVE CVE-2025-38471 https://www.cve.org/CVERecord?id=CVE-2025-38471 Référence CVE CVE-2025-38473 https://www.cve.org/CVERecord?id=CVE-2025-38473 Référence CVE CVE-2025-38474 https://www.cve.org/CVERecord?id=CVE-2025-38474 Référence CVE CVE-2025-38475 https://www.cve.org/CVERecord?id=CVE-2025-38475 Référence CVE CVE-2025-38476 https://www.cve.org/CVERecord?id=CVE-2025-38476 Référence CVE CVE-2025-38477 https://www.cve.org/CVERecord?id=CVE-2025-38477 Référence CVE CVE-2025-38478 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-38453 Référence CVE CVE-2025-38455 https://www.cve.org/CVERecord?id=CVE-2025-38455 Référence CVE CVE-2025-38457 https://www.cve.org/CVERecord?id=CVE-2025-38457 Référence CVE CVE-2025-38460 https://www.cve.org/CVERecord?id=CVE-2025-38460 Référence CVE CVE-2025-38461 https://www.cve.org/CVERecord?id=CVE-2025-38461 Référence CVE CVE-2025-38462 https://www.cve.org/CVERecord?id=CVE-2025-38462 Référence CVE CVE-2025-38463 https://www.cve.org/CVERecord?id=CVE-2025-38463 Référence CVE CVE-2025-38465 https://www.cve.org/CVERecord?id=CVE-2025-38465 Référence CVE CVE-2025-38467 https://www.cve.org/CVERecord?id=CVE-2025-38467 Référence CVE CVE-2025-38468 https://www.cve.org/CVERecord?id=CVE-2025-38468 Référence CVE CVE-2025-38470 https://www.cve.org/CVERecord?id=CVE-2025-38470 Référence CVE CVE-2025-38471 https://www.cve.org/CVERecord?id=CVE-2025-38471 Référence CVE CVE-2025-38473 https://www.cve.org/CVERecord?id=CVE-2025-38473 Référence CVE CVE-2025-38474 https://www.cve.org/CVERecord?id=CVE-2025-38474 Référence CVE CVE-2025-38475 https://www.cve.org/CVERecord?id=CVE-2025-38475 Référence CVE CVE-2025-38476 https://www.cve.org/CVERecord?id=CVE-2025-38476 Référence CVE CVE-2025-38477 https://www.cve.org/CVERecord?id=CVE-2025-38477 Référence CVE CVE-2025-38478 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-38459 Référence CVE CVE-2025-38460 https://www.cve.org/CVERecord?id=CVE-2025-38460 Référence CVE CVE-2025-38461 https://www.cve.org/CVERecord?id=CVE-2025-38461 Référence CVE CVE-2025-38462 https://www.cve.org/CVERecord?id=CVE-2025-38462 Référence CVE CVE-2025-38463 https://www.cve.org/CVERecord?id=CVE-2025-38463 Référence CVE CVE-2025-38464 https://www.cve.org/CVERecord?id=CVE-2025-38464 Référence CVE CVE-2025-38465 https://www.cve.org/CVERecord?id=CVE-2025-38465 Référence CVE CVE-2025-38466 https://www.cve.org/CVERecord?id=CVE-2025-38466 Référence CVE CVE-2025-38467 https://www.cve.org/CVERecord?id=CVE-2025-38467 Référence CVE CVE-2025-38468 https://www.cve.org/CVERecord?id=CVE-2025-38468 Référence CVE CVE-2025-38469 https://www.cve.org/CVERecord?id=CVE-2025-38469 Référence CVE CVE-2025-38470 https://www.cve.org/CVERecord?id=CVE-2025-38470 Référence CVE CVE-2025-38471 https://www.cve.org/CVERecord?id=CVE-2025-38471 Référence CVE CVE-2025-38472 https://www.cve.org/CVERecord?id=CVE-2025-38472 Référence CVE CVE-2025-38473 https://www.cve.org/CVERecord?id=CVE-2025-38473 Référence CVE CVE-2025-38474 https://www.cve.org/CVERecord?id=CVE-2025-38474 Référence CVE CVE-2025-38475 https://www.cve.org/CVERecord?id=CVE-2025-38475 Référence CVE CVE-2025-38476 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2025-023012Linux の Linux Kernel 等複数ベンダの製品における NULL ポインタデリファレンスに関する脆弱性

Linux の Linux Kernel 等複数ベンダの製品には、NULL ポインタデリファレンスに関する脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
Fixed
Linux: < 2.6.29, 5.4.297 ≤ 5.4.*, 5.10.241 ≤ 5.10.*, 5.15.190 ≤ 5.15.*, 6.1.147 ≤ 6.1.*, 6.6.100 ≤ 6.6.*, 6.12.40 ≤ 6.12.*, 6.15.8 ≤ 6.15.*, 6.16 ≤ *
Action
Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
04

Evidence and provenance

Published 28 Jul 2025 · Last source change 14 Jul 2026, 12:42 UTC · CWE-476 · NULL Pointer Dereference

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2025-22894
Product sourceVendor CSAF · Siemens ProductCERT
Remediation sourceVendor CSAF · Siemens ProductCERT
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
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-38468 · cve.blacktree.nl