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

arm64/ptrace: Fix stack-out-of-bounds read in regs_get_kernel_stack_nth()

Linux · Linux

7.1HighCVSS 3.1
Recommended action
Within 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
Distribution package intelligence

Ubuntu vendor package status

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

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 10 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 10 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 10 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 10 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 10 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 10 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 10 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 10 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 10 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 10 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 10 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 10 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 10 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 10 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 10 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 10 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 10 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 10 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 10 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 10 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 10 Sept 2026
Optional official sources

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

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

Official European source

ENISA European Vulnerability Database

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

1 current
ENISA EUVD identifier

EUVD-2025-20926

No EUVD known-exploited evidence

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

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

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: arm64/ptrace: Fix stack-out-of-bounds read in regs_get_kernel_stack_nth() KASAN reports a stack-out-of-bounds read in regs_get_kernel_stack_nth(). Call Trace: [ 97.283505] BUG: KASAN: stack-out-of-bounds in regs_get_kernel_stack_nth+0xa8/0xc8 [ 97.284677] Read of size 8 at addr ffff800089277c10 by task 1.sh/2550 [ 97.285732] [ 97.286067] CPU: 7 PID: 2550 Comm: 1.sh Not tainted 6.6.0+ #11 [ 97.287032] Hardware name: linux,dummy-virt (DT) [ 97.287815] Call trace: [ 97.288279] dump_backtrace+0xa0/0x128 [ 97.288946] show_stack+0x20/0x38 [ 97.289551] dump_stack_lvl+0x78/0xc8 [ 97.290203] print_address_description.constprop.0+0x84/0x3c8 [ 97.291159] print_report+0xb0/0x280 [ 97.291792] kasan_report+0x84/0xd0 [ 97.292421] __asan_load8+0x9c/0xc0 [ 97.293042] regs_get_kernel_stack_nth+0xa8/0xc8 [ 97.293835] process_fetch_insn+0x770/0xa30 [ 97.294562] kprobe_trace_func+0x254/0x3b0 [ 97.295271] kprobe_dispatcher+0x98/0xe0 [ 97.295955] kprobe_breakpoint_handler+0x1b0/0x210 [ 97.296774] call_break_hook+0xc4/0x100 [ 97.297451] brk_handler+0x24/0x78 [ 97.298073] do_debug_exception+0xac/0x178 [ 97.298785] el1_dbg+0x70/0x90 [ 97.299344] el1h_64_sync_handler+0xcc/0xe8 [ 97.300066] el1h_64_sync+0x78/0x80 [ 97.300699] kernel_clone+0x0/0x500 [ 97.301331] __arm64_sys_clone+0x70/0x90 [ 97.302084] invoke_syscall+0x68/0x198 [ 97.302746] el0_svc_common.constprop.0+0x11c/0x150 [ 97.303569] do_el0_svc+0x38/0x50 [ 97.304164] el0_svc+0x44/0x1d8 [ 97.304749] el0t_64_sync_handler+0x100/0x130 [ 97.305500] el0t_64_sync+0x188/0x190 [ 97.306151] [ 97.306475] The buggy address belongs to stack of task 1.sh/2550 [ 97.307461] and is located at offset 0 in frame: [ 97.308257] __se_sys_clone+0x0/0x138 [ 97.308910] [ 97.309241] This frame has 1 object: [ 97.309873] [48, 184) 'args' [ 97.309876] [ 97.310749] The buggy address belongs to the virtual mapping at [ 97.310749] [ffff800089270000, ffff800089279000) created by: [ 97.310749] dup_task_struct+0xc0/0x2e8 [ 97.313347] [ 97.313674] The buggy address belongs to the physical page: [ 97.314604] page: refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x14f69a [ 97.315885] flags: 0x15ffffe00000000(node=1|zone=2|lastcpupid=0xfffff) [ 97.316957] raw: 015ffffe00000000 0000000000000000 dead000000000122 0000000000000000 [ 97.318207] raw: 0000000000000000 0000000000000000 00000001ffffffff 0000000000000000 [ 97.319445] page dumped because: kasan: bad access detected [ 97.320371] [ 97.320694] Memory state around the buggy address: [ 97.321511] ffff800089277b00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [ 97.322681] ffff800089277b80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [ 97.323846] >ffff800089277c00: 00 00 f1 f1 f1 f1 f1 f1 00 00 00 00 00 00 00 00 [ 97.325023] ^ [ 97.325683] ffff800089277c80: 00 00 00 00 00 00 00 00 00 f3 f3 f3 f3 f3 f3 f3 [ 97.326856] ffff800089277d00: f3 f3 00 00 00 00 00 00 00 00 00 00 00 00 00 00 This issue seems to be related to the behavior of some gcc compilers and was also fixed on the s390 architecture before: commit d93a855c31b7 ("s390/ptrace: Avoid KASAN false positives in regs_get_kernel_stack_nth()") As described in that commit, regs_get_kernel_stack_nth() has confirmed that `addr` is on the stack, so reading the value at `*addr` should be allowed. Use READ_ONCE_NOCHECK() helper to silence the KASAN check for this case. [will: Use '*addr' as the argument to READ_ONCE_NOCHECK()]

What

In the Linux kernel, the following vulnerability has been resolved: arm64/ptrace: Fix stack-out-of-bounds read in regs_get_kernel_stack_nth() KASAN reports a stack-out-of-bounds read in regs_get_kernel_stack_nth(). Call Trace: [ 97.283505] BUG: KASAN: stack-out-of-bounds in regs_get_kernel_stack_nth+0xa8/0xc8 [ 97.284677] Read of size 8 at addr ffff800089277c10 by task 1.sh/2550 [ 97.285732] [ 97.286067] CPU: 7 PID: 2550 Comm: 1.sh Not tainted 6.6.0+ #11 [ 97.287032] Hardware name: linux,dummy-virt (DT) [ 97.287815] Call trace: [ 97.288279] dump_backtrace+0xa0/0x128 [ 97.288946] show_stack+0x20/0x38 [ 97.289551] dump_stack_lvl+0x78/0xc8 [ 97.290203] print_address_description.constprop.0+0x84/0x3c8 [ 97.291159] print_report+0xb0/0x280 [ 97.291792] kasan_report+0x84/0xd0 [ 97.292421] __asan_load8+0x9c/0xc0 [ 97.293042] regs_get_kernel_stack_nth+0xa8/0xc8 [ 97.293835] process_fetch_insn+0x770/0xa30 [ 97.294562] kprobe_trace_func+0x254/0x3b0 [ 97.295271] kprobe_dispatcher+0x98/0xe0 [ 97.295955] kprobe_breakpoint_handler+0x1b0/0x210 [ 97.296774] call_break_hook+0xc4/0x100 [ 97.297451] brk_handler+0x24/0x78 [ 97.298073] do_debug_exception+0xac/0x178 [ 97.298785] el1_dbg+0x70/0x90 [ 97.299344] el1h_64_sync_handler+0xcc/0xe8 [ 97.300066] el1h_64_sync+0x78/0x80 [ 97.300699] kernel_clone+0x0/0x500 [ 97.301331] __arm64_sys_clone+0x70/0x90 [ 97.302084] invoke_syscall+0x68/0x198 [ 97.302746] el0_svc_common.constprop.0+0x11c/0x150 [ 97.303569] do_el0_svc+0x38/0x50 [ 97.304164] el0_svc+0x44/0x1d8 [ 97.304749] el0t_64_sync_handler+0x100/0x130 [ 97.305500] el0t_64_sync+0x188/0x190 [ 97.306151] [ 97.306475] The buggy address belongs to stack of task 1.sh/2550 [ 97.307461] and is located at offset 0 in frame: [ 97.308257] __se_sys_clone+0x0/0x138 [ 97.308910] [ 97.309241] This frame has 1 object: [ 97.309873] [48, 184) 'args' [ 97.309876] [ 97.310749] The buggy address belongs to the virtual mapping at [ 97.310749] [ffff800089270000, ffff800089279000) created by: [ 97.310749] dup_task_struct+0xc0/0x2e8 [ 97.313347] [ 97.313674] The buggy address belongs to the physical page: [ 97.314604] page: refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x14f69a [ 97.315885] flags: 0x15ffffe00000000(node=1|zone=2|lastcpupid=0xfffff) [ 97.316957] raw: 015ffffe00000000 0000000000000000 dead000000000122 0000000000000000 [ 97.318207] raw: 0000000000000000 0000000000000000 00000001ffffffff 0000000000000000 [ 97.319445] page dumped because: kasan: bad access detected [ 97.320371] [ 97.320694] Memory state around the buggy address: [ 97.321511] ffff800089277b00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [ 97.322681] ffff800089277b80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [ 97.323846] >ffff800089277c00: 00 00 f1 f1 f1 f1 f1 f1 00 00 00 00 00 00 00 00 [ 97.325023] ^ [ 97.325683] ffff800089277c80: 00 00 00 00 00 00 00 00 00 f3 f3 f3 f3 f3 f3 f3 [ 97.326856] ffff800089277d00: f3 f3 00 00 00 00 00 00 00 00 00 00 00 00 00 00 This issue seems to be related to the behavior of some gcc compilers and was also fixed on the s390 architecture before: commit d93a855c31b7 ("s390/ptrace: Avoid KASAN false positives in regs_get_kernel_stack_nth()") As described in that commit, regs_get_kernel_stack_nth() has confirmed that `addr` is on the stack, so reading the value at `*addr` should be allowed. Use READ_ONCE_NOCHECK() helper to silence the KASAN check for this case. [will: Use '*addr' as the argument to READ_ONCE_NOCHECK()]

Why

The product reads data past the end, or before the beginning, of the intended buffer.

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: arm64/ptrace: Fix stack-out-of-bounds read in regs_get_kernel_stack_nth() KASAN reports a stack-out-of-bounds read in regs_get_kernel_stack_nth(). Call Trace: [ 97.283505] BUG: KASAN: stack-out-of-bounds in regs_get_kernel_stack_nth+0xa8/0xc8 [ 97.284677] Read of size 8 at addr ffff800089277c10 by task 1.sh/2550 [ 97.285732] [ 97.286067] CPU: 7 PID: 2550 Comm: 1.sh Not tainted 6.6.0+ #11 [ 97.287032] Hardware name: linux,dummy-virt (DT) [ 97.287815] Call trace: [ 97.288279] dump_backtrace+0xa0/0x128 [ 97.288946] show_stack+0x20/0x38 [ 97.289551] dump_stack_lvl+0x78/0xc8 [ 97.290203] print_address_description.constprop.0+0x84/0x3c8 [ 97.291159] print_report+0xb0/0x280 [ 97.291792] kasan_report+0x84/0xd0 [ 97.292421] __asan_load8+0x9c/0xc0 [ 97.293042] regs_get_kernel_stack_nth+0xa8/0xc8 [ 97.293835] process_fetch_insn+0x770/0xa30 [ 97.294562] kprobe_trace_func+0x254/0x3b0 [ 97.295271] kprobe_dispatcher+0x98/0xe0 [ 97.295955] kprobe_breakpoint_handler+0x1b0/0x210 [ 97.296774] call_break_hook+0xc4/0x100 [ 97.297451] brk_handler+0x24/0x78 [ 97.298073] do_debug_exception+0xac/0x178 [ 97.298785] el1_dbg+0x70/0x90 [ 97.299344] el1h_64_sync_handler+0xcc/0xe8 [ 97.300066] el1h_64_sync+0x78/0x80 [ 97.300699] kernel_clone+0x0/0x500 [ 97.301331] __arm64_sys_clone+0x70/0x90 [ 97.302084] invoke_syscall+0x68/0x198 [ 97.302746] el0_svc_common.constprop.0+0x11c/0x150 [ 97.303569] do_el0_svc+0x38/0x50 [ 97.304164] el0_svc+0x44/0x1d8 [ 97.304749] el0t_64_sync_handler+0x100/0x130 [ 97.305500] el0t_64_sync+0x188/0x190 [ 97.306151] [ 97.306475] The buggy address belongs to stack of task 1.sh/2550 [ 97.307461] and is located at offset 0 in frame: [ 97.308257] __se_sys_clone+0x0/0x138 [ 97.308910] [ 97.309241] This frame has 1 object: [ 97.309873] [48, 184) 'args' [ 97.309876] [ 97.310749] The buggy address belongs to the virtual mapping at [ 97.310749] [ffff800089270000, ffff800089279000) created by: [ 97.310749] dup_task_struct+0xc0/0x2e8 [ 97.313347] [ 97.313674] The buggy address belongs to the physical page: [ 97.314604] page: refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x14f69a [ 97.315885] flags: 0x15ffffe00000000(node=1|zone=2|lastcpupid=0xfffff) [ 97.316957] raw: 015ffffe00000000 0000000000000000 dead000000000122 0000000000000000 [ 97.318207] raw: 0000000000000000 0000000000000000 00000001ffffffff 0000000000000000 [ 97.319445] page dumped because: kasan: bad access detected [ 97.320371] [ 97.320694] Memory state around the buggy address: [ 97.321511] ffff800089277b00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [ 97.322681] ffff800089277b80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [ 97.323846] >ffff800089277c00: 00 00 f1 f1 f1 f1 f1 f1 00 00 00 00 00 00 00 00 [ 97.325023] ^ [ 97.325683] ffff800089277c80: 00 00 00 00 00 00 00 00 00 f3 f3 f3 f3 f3 f3 f3 [ 97.326856] ffff800089277d00: f3 f3 00 00 00 00 00 00 00 00 00 00 00 00 00 00 This issue seems to be related to the behavior of some gcc compilers and was also fixed on the s390 architecture before: commit d93a855c31b7 ("s390/ptrace: Avoid KASAN false positives in regs_get_kernel_stack_nth()") As described in that commit, regs_get_kernel_stack_nth() has confirmed that `addr` is on the stack, so reading the value at `*addr` should be allowed. Use READ_ONCE_NOCHECK() helper to silence the KASAN check for this case. [will: Use '*addr' as the argument to READ_ONCE_NOCHECK()]

Why

The product reads data past the end, or before the beginning, of the intended buffer.

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 → Out-of-bounds Read → 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-125

CWE-125: Out-of-bounds Read. The product reads data past the end, or before the beginning, of the intended buffer.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I: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.CHighConfidentiality impact: A successful attack can cause a major loss.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-125
A

Official authority intelligence

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

BSI · German · WID-SEC-W-2025-1522Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service

Ein entfernter Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht spezifizierte Auswirkungen zu verursachen.

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

d?id=CVE-2025-38300 Référence CVE CVE-2025-38303 https://www.cve.org/CVERecord?id=CVE-2025-38303 Référence CVE CVE-2025-38304 https://www.cve.org/CVERecord?id=CVE-2025-38304 Référence CVE CVE-2025-38305 https://www.cve.org/CVERecord?id=CVE-2025-38305 Référence CVE CVE-2025-38307 https://www.cve.org/CVERecord?id=CVE-2025-38307 Référence CVE CVE-2025-38310 https://www.cve.org/CVERecord?id=CVE-2025-38310 Référence CVE CVE-2025-38312 https://www.cve.org/CVERecord?id=CVE-2025-38312 Référence CVE CVE-2025-38313 https://www.cve.org/CVERecord?id=CVE-2025-38313 Référence CVE CVE-2025-38319 https://www.cve.org/CVERecord?id=CVE-2025-38319 Référence CVE CVE-2025-38320 https://www.cve.org/CVERecord?id=CVE-2025-38320 Référence CVE CVE-2025-38321 https://www.cve.org/CVERecord?id=CVE-2025-38321 Référence CVE CVE-2025-38322 https://www.cve.org/CVERecord?id=CVE-2025-38322 Référence CVE CVE-2025-38323 https://www.cve.org/CVERecord?id=CVE-2025-38323 Référence CVE CVE-2025-38324 https://www.cve.org/CVERecord?id=CVE-2025-38324 Référence CVE CVE-2025-38326 https://www.cve.org/CVERecord?id=CVE-2025-38326 Référence CVE CVE-2025-38328 https://www.cve.org/CVERecord?id=CVE-2025-38328 Référence CVE CVE-2025-38331 https://www.cve.org/CVERecord?id=CVE-2025-38331 Référence CVE CVE-2025-38332 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-38300 Référence CVE CVE-2025-38303 https://www.cve.org/CVERecord?id=CVE-2025-38303 Référence CVE CVE-2025-38304 https://www.cve.org/CVERecord?id=CVE-2025-38304 Référence CVE CVE-2025-38305 https://www.cve.org/CVERecord?id=CVE-2025-38305 Référence CVE CVE-2025-38307 https://www.cve.org/CVERecord?id=CVE-2025-38307 Référence CVE CVE-2025-38310 https://www.cve.org/CVERecord?id=CVE-2025-38310 Référence CVE CVE-2025-38312 https://www.cve.org/CVERecord?id=CVE-2025-38312 Référence CVE CVE-2025-38313 https://www.cve.org/CVERecord?id=CVE-2025-38313 Référence CVE CVE-2025-38319 https://www.cve.org/CVERecord?id=CVE-2025-38319 Référence CVE CVE-2025-38320 https://www.cve.org/CVERecord?id=CVE-2025-38320 Référence CVE CVE-2025-38321 https://www.cve.org/CVERecord?id=CVE-2025-38321 Référence CVE CVE-2025-38322 https://www.cve.org/CVERecord?id=CVE-2025-38322 Référence CVE CVE-2025-38323 https://www.cve.org/CVERecord?id=CVE-2025-38323 Référence CVE CVE-2025-38324 https://www.cve.org/CVERecord?id=CVE-2025-38324 Référence CVE CVE-2025-38326 https://www.cve.org/CVERecord?id=CVE-2025-38326 Référence CVE CVE-2025-38328 https://www.cve.org/CVERecord?id=CVE-2025-38328 Référence CVE CVE-2025-38331 https://www.cve.org/CVERecord?id=CVE-2025-38331 Référence CVE CVE-2025-38332 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-38300 Référence CVE CVE-2025-38303 https://www.cve.org/CVERecord?id=CVE-2025-38303 Référence CVE CVE-2025-38304 https://www.cve.org/CVERecord?id=CVE-2025-38304 Référence CVE CVE-2025-38305 https://www.cve.org/CVERecord?id=CVE-2025-38305 Référence CVE CVE-2025-38307 https://www.cve.org/CVERecord?id=CVE-2025-38307 Référence CVE CVE-2025-38310 https://www.cve.org/CVERecord?id=CVE-2025-38310 Référence CVE CVE-2025-38312 https://www.cve.org/CVERecord?id=CVE-2025-38312 Référence CVE CVE-2025-38313 https://www.cve.org/CVERecord?id=CVE-2025-38313 Référence CVE CVE-2025-38319 https://www.cve.org/CVERecord?id=CVE-2025-38319 Référence CVE CVE-2025-38320 https://www.cve.org/CVERecord?id=CVE-2025-38320 Référence CVE CVE-2025-38321 https://www.cve.org/CVERecord?id=CVE-2025-38321 Référence CVE CVE-2025-38322 https://www.cve.org/CVERecord?id=CVE-2025-38322 Référence CVE CVE-2025-38323 https://www.cve.org/CVERecord?id=CVE-2025-38323 Référence CVE CVE-2025-38324 https://www.cve.org/CVERecord?id=CVE-2025-38324 Référence CVE CVE-2025-38326 https://www.cve.org/CVERecord?id=CVE-2025-38326 Référence CVE CVE-2025-38328 https://www.cve.org/CVERecord?id=CVE-2025-38328 Référence CVE CVE-2025-38331 https://www.cve.org/CVERecord?id=CVE-2025-38331 Référence CVE CVE-2025-38332 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-38300 Référence CVE CVE-2025-38303 https://www.cve.org/CVERecord?id=CVE-2025-38303 Référence CVE CVE-2025-38304 https://www.cve.org/CVERecord?id=CVE-2025-38304 Référence CVE CVE-2025-38305 https://www.cve.org/CVERecord?id=CVE-2025-38305 Référence CVE CVE-2025-38307 https://www.cve.org/CVERecord?id=CVE-2025-38307 Référence CVE CVE-2025-38310 https://www.cve.org/CVERecord?id=CVE-2025-38310 Référence CVE CVE-2025-38312 https://www.cve.org/CVERecord?id=CVE-2025-38312 Référence CVE CVE-2025-38313 https://www.cve.org/CVERecord?id=CVE-2025-38313 Référence CVE CVE-2025-38319 https://www.cve.org/CVERecord?id=CVE-2025-38319 Référence CVE CVE-2025-38320 https://www.cve.org/CVERecord?id=CVE-2025-38320 Référence CVE CVE-2025-38321 https://www.cve.org/CVERecord?id=CVE-2025-38321 Référence CVE CVE-2025-38322 https://www.cve.org/CVERecord?id=CVE-2025-38322 Référence CVE CVE-2025-38323 https://www.cve.org/CVERecord?id=CVE-2025-38323 Référence CVE CVE-2025-38324 https://www.cve.org/CVERecord?id=CVE-2025-38324 Référence CVE CVE-2025-38326 https://www.cve.org/CVERecord?id=CVE-2025-38326 Référence CVE CVE-2025-38328 https://www.cve.org/CVERecord?id=CVE-2025-38328 Référence CVE CVE-2025-38331 https://www.cve.org/CVERecord?id=CVE-2025-38331 Référence CVE CVE-2025-38332 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-38300 Référence CVE CVE-2025-38303 https://www.cve.org/CVERecord?id=CVE-2025-38303 Référence CVE CVE-2025-38304 https://www.cve.org/CVERecord?id=CVE-2025-38304 Référence CVE CVE-2025-38305 https://www.cve.org/CVERecord?id=CVE-2025-38305 Référence CVE CVE-2025-38307 https://www.cve.org/CVERecord?id=CVE-2025-38307 Référence CVE CVE-2025-38310 https://www.cve.org/CVERecord?id=CVE-2025-38310 Référence CVE CVE-2025-38312 https://www.cve.org/CVERecord?id=CVE-2025-38312 Référence CVE CVE-2025-38313 https://www.cve.org/CVERecord?id=CVE-2025-38313 Référence CVE CVE-2025-38319 https://www.cve.org/CVERecord?id=CVE-2025-38319 Référence CVE CVE-2025-38320 https://www.cve.org/CVERecord?id=CVE-2025-38320 Référence CVE CVE-2025-38321 https://www.cve.org/CVERecord?id=CVE-2025-38321 Référence CVE CVE-2025-38322 https://www.cve.org/CVERecord?id=CVE-2025-38322 Référence CVE CVE-2025-38323 https://www.cve.org/CVERecord?id=CVE-2025-38323 Référence CVE CVE-2025-38324 https://www.cve.org/CVERecord?id=CVE-2025-38324 Référence CVE CVE-2025-38326 https://www.cve.org/CVERecord?id=CVE-2025-38326 Référence CVE CVE-2025-38328 https://www.cve.org/CVERecord?id=CVE-2025-38328 Référence CVE CVE-2025-38331 https://www.cve.org/CVERecord?id=CVE-2025-38331 Référence CVE CVE-2025-38332 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38285 Référence CVE CVE-2025-38286 https://www.cve.org/CVERecord?id=CVE-2025-38286 Référence CVE CVE-2025-38293 https://www.cve.org/CVERecord?id=CVE-2025-38293 Référence CVE CVE-2025-38298 https://www.cve.org/CVERecord?id=CVE-2025-38298 Référence CVE CVE-2025-38305 https://www.cve.org/CVERecord?id=CVE-2025-38305 Référence CVE CVE-2025-38310 https://www.cve.org/CVERecord?id=CVE-2025-38310 Référence CVE CVE-2025-38312 https://www.cve.org/CVERecord?id=CVE-2025-38312 Référence CVE CVE-2025-38313 https://www.cve.org/CVERecord?id=CVE-2025-38313 Référence CVE CVE-2025-38319 https://www.cve.org/CVERecord?id=CVE-2025-38319 Référence CVE CVE-2025-38320 https://www.cve.org/CVERecord?id=CVE-2025-38320 Référence CVE CVE-2025-38323 https://www.cve.org/CVERecord?id=CVE-2025-38323 Référence CVE CVE-2025-38324 https://www.cve.org/CVERecord?id=CVE-2025-38324 Référence CVE CVE-2025-38326 https://www.cve.org/CVERecord?id=CVE-2025-38326 Référence CVE CVE-2025-38328 https://www.cve.org/CVERecord?id=CVE-2025-38328 Référence CVE CVE-2025-38332 https://www.cve.org/CVERecord?id=CVE-2025-38332 Référence CVE CVE-2025-38336 https://www.cve.org/CVERecord?id=CVE-2025-38336 Référence CVE CVE-2025-38337 https://www.cve.org/CVERecord?id=CVE-2025-38337 Référence CVE CVE-2025-38342 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38256 Référence CVE CVE-2025-38257 https://www.cve.org/CVERecord?id=CVE-2025-38257 Référence CVE CVE-2025-38258 https://www.cve.org/CVERecord?id=CVE-2025-38258 Référence CVE CVE-2025-38259 https://www.cve.org/CVERecord?id=CVE-2025-38259 Référence CVE CVE-2025-38260 https://www.cve.org/CVERecord?id=CVE-2025-38260 Référence CVE CVE-2025-38261 https://www.cve.org/CVERecord?id=CVE-2025-38261 Référence CVE CVE-2025-38262 https://www.cve.org/CVERecord?id=CVE-2025-38262 Référence CVE CVE-2025-38263 https://www.cve.org/CVERecord?id=CVE-2025-38263 Référence CVE CVE-2025-38264 https://www.cve.org/CVERecord?id=CVE-2025-38264 Référence CVE CVE-2025-38320 https://www.cve.org/CVERecord?id=CVE-2025-38320 Référence CVE CVE-2025-38321 https://www.cve.org/CVERecord?id=CVE-2025-38321 Référence CVE CVE-2025-38322 https://www.cve.org/CVERecord?id=CVE-2025-38322 Référence CVE CVE-2025-38323 https://www.cve.org/CVERecord?id=CVE-2025-38323 Référence CVE CVE-2025-38324 https://www.cve.org/CVERecord?id=CVE-2025-38324 Référence CVE CVE-2025-38325 https://www.cve.org/CVERecord?id=CVE-2025-38325 Référence CVE CVE-2025-38326 https://www.cve.org/CVERecord?id=CVE-2025-38326 Référence CVE CVE-2025-38328 https://www.cve.org/CVERecord?id=CVE-2025-38328 Référence CVE CVE-2025-38329 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-38285 Référence CVE CVE-2025-38286 https://www.cve.org/CVERecord?id=CVE-2025-38286 Référence CVE CVE-2025-38293 https://www.cve.org/CVERecord?id=CVE-2025-38293 Référence CVE CVE-2025-38298 https://www.cve.org/CVERecord?id=CVE-2025-38298 Référence CVE CVE-2025-38305 https://www.cve.org/CVERecord?id=CVE-2025-38305 Référence CVE CVE-2025-38310 https://www.cve.org/CVERecord?id=CVE-2025-38310 Référence CVE CVE-2025-38312 https://www.cve.org/CVERecord?id=CVE-2025-38312 Référence CVE CVE-2025-38313 https://www.cve.org/CVERecord?id=CVE-2025-38313 Référence CVE CVE-2025-38319 https://www.cve.org/CVERecord?id=CVE-2025-38319 Référence CVE CVE-2025-38320 https://www.cve.org/CVERecord?id=CVE-2025-38320 Référence CVE CVE-2025-38324 https://www.cve.org/CVERecord?id=CVE-2025-38324 Référence CVE CVE-2025-38326 https://www.cve.org/CVERecord?id=CVE-2025-38326 Référence CVE CVE-2025-38328 https://www.cve.org/CVERecord?id=CVE-2025-38328 Référence CVE CVE-2025-38332 https://www.cve.org/CVERecord?id=CVE-2025-38332 Référence CVE CVE-2025-38336 https://www.cve.org/CVERecord?id=CVE-2025-38336 Référence CVE CVE-2025-38337 https://www.cve.org/CVERecord?id=CVE-2025-38337 Référence CVE CVE-2025-38342 https://www.cve.org/CVERecord?id=CVE-2025-38342 Référence CVE CVE-2025-38344 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38256 Référence CVE CVE-2025-38257 https://www.cve.org/CVERecord?id=CVE-2025-38257 Référence CVE CVE-2025-38258 https://www.cve.org/CVERecord?id=CVE-2025-38258 Référence CVE CVE-2025-38259 https://www.cve.org/CVERecord?id=CVE-2025-38259 Référence CVE CVE-2025-38260 https://www.cve.org/CVERecord?id=CVE-2025-38260 Référence CVE CVE-2025-38261 https://www.cve.org/CVERecord?id=CVE-2025-38261 Référence CVE CVE-2025-38262 https://www.cve.org/CVERecord?id=CVE-2025-38262 Référence CVE CVE-2025-38263 https://www.cve.org/CVERecord?id=CVE-2025-38263 Référence CVE CVE-2025-38264 https://www.cve.org/CVERecord?id=CVE-2025-38264 Référence CVE CVE-2025-38320 https://www.cve.org/CVERecord?id=CVE-2025-38320 Référence CVE CVE-2025-38321 https://www.cve.org/CVERecord?id=CVE-2025-38321 Référence CVE CVE-2025-38322 https://www.cve.org/CVERecord?id=CVE-2025-38322 Référence CVE CVE-2025-38324 https://www.cve.org/CVERecord?id=CVE-2025-38324 Référence CVE CVE-2025-38325 https://www.cve.org/CVERecord?id=CVE-2025-38325 Référence CVE CVE-2025-38326 https://www.cve.org/CVERecord?id=CVE-2025-38326 Référence CVE CVE-2025-38328 https://www.cve.org/CVERecord?id=CVE-2025-38328 Référence CVE CVE-2025-38329 https://www.cve.org/CVERecord?id=CVE-2025-38329 Référence CVE CVE-2025-38330 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38256 Référence CVE CVE-2025-38257 https://www.cve.org/CVERecord?id=CVE-2025-38257 Référence CVE CVE-2025-38258 https://www.cve.org/CVERecord?id=CVE-2025-38258 Référence CVE CVE-2025-38259 https://www.cve.org/CVERecord?id=CVE-2025-38259 Référence CVE CVE-2025-38260 https://www.cve.org/CVERecord?id=CVE-2025-38260 Référence CVE CVE-2025-38261 https://www.cve.org/CVERecord?id=CVE-2025-38261 Référence CVE CVE-2025-38262 https://www.cve.org/CVERecord?id=CVE-2025-38262 Référence CVE CVE-2025-38263 https://www.cve.org/CVERecord?id=CVE-2025-38263 Référence CVE CVE-2025-38264 https://www.cve.org/CVERecord?id=CVE-2025-38264 Référence CVE CVE-2025-38320 https://www.cve.org/CVERecord?id=CVE-2025-38320 Référence CVE CVE-2025-38321 https://www.cve.org/CVERecord?id=CVE-2025-38321 Référence CVE CVE-2025-38322 https://www.cve.org/CVERecord?id=CVE-2025-38322 Référence CVE CVE-2025-38324 https://www.cve.org/CVERecord?id=CVE-2025-38324 Référence CVE CVE-2025-38325 https://www.cve.org/CVERecord?id=CVE-2025-38325 Référence CVE CVE-2025-38326 https://www.cve.org/CVERecord?id=CVE-2025-38326 Référence CVE CVE-2025-38328 https://www.cve.org/CVERecord?id=CVE-2025-38328 Référence CVE CVE-2025-38329 https://www.cve.org/CVERecord?id=CVE-2025-38329 Référence CVE CVE-2025-38330 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-38293 Référence CVE CVE-2025-38298 https://www.cve.org/CVERecord?id=CVE-2025-38298 Référence CVE CVE-2025-38300 https://www.cve.org/CVERecord?id=CVE-2025-38300 Référence CVE CVE-2025-38304 https://www.cve.org/CVERecord?id=CVE-2025-38304 Référence CVE CVE-2025-38305 https://www.cve.org/CVERecord?id=CVE-2025-38305 Référence CVE CVE-2025-38310 https://www.cve.org/CVERecord?id=CVE-2025-38310 Référence CVE CVE-2025-38312 https://www.cve.org/CVERecord?id=CVE-2025-38312 Référence CVE CVE-2025-38313 https://www.cve.org/CVERecord?id=CVE-2025-38313 Référence CVE CVE-2025-38319 https://www.cve.org/CVERecord?id=CVE-2025-38319 Référence CVE CVE-2025-38320 https://www.cve.org/CVERecord?id=CVE-2025-38320 Référence CVE CVE-2025-38322 https://www.cve.org/CVERecord?id=CVE-2025-38322 Référence CVE CVE-2025-38323 https://www.cve.org/CVERecord?id=CVE-2025-38323 Référence CVE CVE-2025-38324 https://www.cve.org/CVERecord?id=CVE-2025-38324 Référence CVE CVE-2025-38326 https://www.cve.org/CVERecord?id=CVE-2025-38326 Référence CVE CVE-2025-38328 https://www.cve.org/CVERecord?id=CVE-2025-38328 Référence CVE CVE-2025-38331 https://www.cve.org/CVERecord?id=CVE-2025-38331 Référence CVE CVE-2025-38332 https://www.cve.org/CVERecord?id=CVE-2025-38332 Référence CVE CVE-2025-38334 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-38311 Référence CVE CVE-2025-38312 https://www.cve.org/CVERecord?id=CVE-2025-38312 Référence CVE CVE-2025-38313 https://www.cve.org/CVERecord?id=CVE-2025-38313 Référence CVE CVE-2025-38314 https://www.cve.org/CVERecord?id=CVE-2025-38314 Référence CVE CVE-2025-38315 https://www.cve.org/CVERecord?id=CVE-2025-38315 Référence CVE CVE-2025-38316 https://www.cve.org/CVERecord?id=CVE-2025-38316 Référence CVE CVE-2025-38317 https://www.cve.org/CVERecord?id=CVE-2025-38317 Référence CVE CVE-2025-38318 https://www.cve.org/CVERecord?id=CVE-2025-38318 Référence CVE CVE-2025-38319 https://www.cve.org/CVERecord?id=CVE-2025-38319 Référence CVE CVE-2025-38320 https://www.cve.org/CVERecord?id=CVE-2025-38320 Référence CVE CVE-2025-38324 https://www.cve.org/CVERecord?id=CVE-2025-38324 Référence CVE CVE-2025-38326 https://www.cve.org/CVERecord?id=CVE-2025-38326 Référence CVE CVE-2025-38328 https://www.cve.org/CVERecord?id=CVE-2025-38328 Référence CVE CVE-2025-38332 https://www.cve.org/CVERecord?id=CVE-2025-38332 Référence CVE CVE-2025-38336 https://www.cve.org/CVERecord?id=CVE-2025-38336 Référence CVE CVE-2025-38337 https://www.cve.org/CVERecord?id=CVE-2025-38337 Référence CVE CVE-2025-38342 https://www.cve.org/CVERecord?id=CVE-2025-38342 Référence CVE CVE-2025-38344 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-38311 Référence CVE CVE-2025-38312 https://www.cve.org/CVERecord?id=CVE-2025-38312 Référence CVE CVE-2025-38313 https://www.cve.org/CVERecord?id=CVE-2025-38313 Référence CVE CVE-2025-38314 https://www.cve.org/CVERecord?id=CVE-2025-38314 Référence CVE CVE-2025-38315 https://www.cve.org/CVERecord?id=CVE-2025-38315 Référence CVE CVE-2025-38316 https://www.cve.org/CVERecord?id=CVE-2025-38316 Référence CVE CVE-2025-38317 https://www.cve.org/CVERecord?id=CVE-2025-38317 Référence CVE CVE-2025-38318 https://www.cve.org/CVERecord?id=CVE-2025-38318 Référence CVE CVE-2025-38319 https://www.cve.org/CVERecord?id=CVE-2025-38319 Référence CVE CVE-2025-38320 https://www.cve.org/CVERecord?id=CVE-2025-38320 Référence CVE CVE-2025-38324 https://www.cve.org/CVERecord?id=CVE-2025-38324 Référence CVE CVE-2025-38326 https://www.cve.org/CVERecord?id=CVE-2025-38326 Référence CVE CVE-2025-38328 https://www.cve.org/CVERecord?id=CVE-2025-38328 Référence CVE CVE-2025-38332 https://www.cve.org/CVERecord?id=CVE-2025-38332 Référence CVE CVE-2025-38336 https://www.cve.org/CVERecord?id=CVE-2025-38336 Référence CVE CVE-2025-38337 https://www.cve.org/CVERecord?id=CVE-2025-38337 Référence CVE CVE-2025-38342 https://www.cve.org/CVERecord?id=CVE-2025-38342 Référence CVE CVE-2025-38344 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-38311 Référence CVE CVE-2025-38312 https://www.cve.org/CVERecord?id=CVE-2025-38312 Référence CVE CVE-2025-38313 https://www.cve.org/CVERecord?id=CVE-2025-38313 Référence CVE CVE-2025-38314 https://www.cve.org/CVERecord?id=CVE-2025-38314 Référence CVE CVE-2025-38315 https://www.cve.org/CVERecord?id=CVE-2025-38315 Référence CVE CVE-2025-38316 https://www.cve.org/CVERecord?id=CVE-2025-38316 Référence CVE CVE-2025-38317 https://www.cve.org/CVERecord?id=CVE-2025-38317 Référence CVE CVE-2025-38318 https://www.cve.org/CVERecord?id=CVE-2025-38318 Référence CVE CVE-2025-38319 https://www.cve.org/CVERecord?id=CVE-2025-38319 Référence CVE CVE-2025-38320 https://www.cve.org/CVERecord?id=CVE-2025-38320 Référence CVE CVE-2025-38324 https://www.cve.org/CVERecord?id=CVE-2025-38324 Référence CVE CVE-2025-38326 https://www.cve.org/CVERecord?id=CVE-2025-38326 Référence CVE CVE-2025-38328 https://www.cve.org/CVERecord?id=CVE-2025-38328 Référence CVE CVE-2025-38332 https://www.cve.org/CVERecord?id=CVE-2025-38332 Référence CVE CVE-2025-38336 https://www.cve.org/CVERecord?id=CVE-2025-38336 Référence CVE CVE-2025-38337 https://www.cve.org/CVERecord?id=CVE-2025-38337 Référence CVE CVE-2025-38342 https://www.cve.org/CVERecord?id=CVE-2025-38342 Référence CVE CVE-2025-38344 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-38293 Référence CVE CVE-2025-38298 https://www.cve.org/CVERecord?id=CVE-2025-38298 Référence CVE CVE-2025-38300 https://www.cve.org/CVERecord?id=CVE-2025-38300 Référence CVE CVE-2025-38304 https://www.cve.org/CVERecord?id=CVE-2025-38304 Référence CVE CVE-2025-38305 https://www.cve.org/CVERecord?id=CVE-2025-38305 Référence CVE CVE-2025-38310 https://www.cve.org/CVERecord?id=CVE-2025-38310 Référence CVE CVE-2025-38312 https://www.cve.org/CVERecord?id=CVE-2025-38312 Référence CVE CVE-2025-38313 https://www.cve.org/CVERecord?id=CVE-2025-38313 Référence CVE CVE-2025-38319 https://www.cve.org/CVERecord?id=CVE-2025-38319 Référence CVE CVE-2025-38320 https://www.cve.org/CVERecord?id=CVE-2025-38320 Référence CVE CVE-2025-38323 https://www.cve.org/CVERecord?id=CVE-2025-38323 Référence CVE CVE-2025-38324 https://www.cve.org/CVERecord?id=CVE-2025-38324 Référence CVE CVE-2025-38326 https://www.cve.org/CVERecord?id=CVE-2025-38326 Référence CVE CVE-2025-38328 https://www.cve.org/CVERecord?id=CVE-2025-38328 Référence CVE CVE-2025-38331 https://www.cve.org/CVERecord?id=CVE-2025-38331 Référence CVE CVE-2025-38332 https://www.cve.org/CVERecord?id=CVE-2025-38332 Référence CVE CVE-2025-38334 https://www.cve.org/CVERecord?id=CVE-2025-38334 Référence CVE CVE-2025-38335 https://www.cve.org/CVERecord?id=

Official advisory
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
0a8ea52c3eb157dd65e224fc95b7c9c99fcba9f7 < 64773b3ea09235168a549a195cba43bb867c4a17; 0a8ea52c3eb157dd65e224fc95b7c9c99fcba9f7 < 67abac27d806e8f9d4226ec1528540cf73af673a; 0a8ea52c3eb157dd65e224fc95b7c9c99fcba9f7 < 92750bfe7b0d8dbcaf578c091a65eda1c5f9ad38; 0a8ea52c3eb157dd65e224fc95b7c9c99fcba9f7 < 01f91d415a8375d85e0c7d3615cd4a168308bb7c; 0a8ea52c3eb157dd65e224fc95b7c9c99fcba9f7 < 21da6d3561f373898349ca7167c9811c020da695; 0a8ea52c3eb157dd65e224fc95b7c9c99fcba9f7 < 22f935bc86bdfbde04009f05eee191d220cd8c89; 0a8ea52c3eb157dd65e224fc95b7c9c99fcba9f7 < 422e565b7889ebfd9c8705a3fc786642afe61fca; 0a8ea52c3eb157dd65e224fc95b7c9c99fcba9f7 < 39dfc971e42d886e7df01371cd1bef505076d84c
Fixed
< 4.8; 5.4.295 ≤ 5.4.*; 5.10.239 ≤ 5.10.*; 5.15.186 ≤ 5.15.*; 6.1.142 ≤ 6.1.*; 6.6.95 ≤ 6.6.*; 6.12.35 ≤ 6.12.*; 6.15.4 ≤ 6.15.*
Action
Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 10 Jul 2025 · Last source change 11 May 2026, 21:25 UTC · CWE-125 · Out-of-bounds Read

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-20926
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceNIST NVD
NVD statusNVD enriched

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