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

net: libwx: properly reset Rx ring descriptor

Linux · Linux

7.8HighCVSS 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 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
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-27887

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: net: libwx: properly reset Rx ring descriptor When device reset is triggered by feature changes such as toggling Rx VLAN offload, wx->do_reset() is called to reinitialize Rx rings. The hardware descriptor ring may retain stale values from previous sessions. And only set the length to 0 in rx_desc[0] would result in building malformed SKBs. Fix it to ensure a clean slate after device reset. [ 549.186435] [ C16] ------------[ cut here ]------------ [ 549.186457] [ C16] kernel BUG at net/core/skbuff.c:2814! [ 549.186468] [ C16] Oops: invalid opcode: 0000 [#1] SMP NOPTI [ 549.186472] [ C16] CPU: 16 UID: 0 PID: 0 Comm: swapper/16 Kdump: loaded Not tainted 6.16.0-rc4+ #23 PREEMPT(voluntary) [ 549.186476] [ C16] Hardware name: Micro-Star International Co., Ltd. MS-7E16/X670E GAMING PLUS WIFI (MS-7E16), BIOS 1.90 12/31/2024 [ 549.186478] [ C16] RIP: 0010:__pskb_pull_tail+0x3ff/0x510 [ 549.186484] [ C16] Code: 06 f0 ff 4f 34 74 7b 4d 8b 8c 24 c8 00 00 00 45 8b 84 24 c0 00 00 00 e9 c8 fd ff ff 48 c7 44 24 08 00 00 00 00 e9 5e fe ff ff <0f> 0b 31 c0 e9 23 90 5b ff 41 f7 c6 ff 0f 00 00 75 bf 49 8b 06 a8 [ 549.186487] [ C16] RSP: 0018:ffffb391c0640d70 EFLAGS: 00010282 [ 549.186490] [ C16] RAX: 00000000fffffff2 RBX: ffff8fe7e4d40200 RCX: 00000000fffffff2 [ 549.186492] [ C16] RDX: ffff8fe7c3a4bf8e RSI: 0000000000000180 RDI: ffff8fe7c3a4bf40 [ 549.186494] [ C16] RBP: ffffb391c0640da8 R08: ffff8fe7c3a4c0c0 R09: 000000000000000e [ 549.186496] [ C16] R10: ffffb391c0640d88 R11: 000000000000000e R12: ffff8fe7e4d40200 [ 549.186497] [ C16] R13: 00000000fffffff2 R14: ffff8fe7fa01a000 R15: 00000000fffffff2 [ 549.186499] [ C16] FS: 0000000000000000(0000) GS:ffff8fef5ae40000(0000) knlGS:0000000000000000 [ 549.186502] [ C16] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 549.186503] [ C16] CR2: 00007f77d81d6000 CR3: 000000051a032000 CR4: 0000000000750ef0 [ 549.186505] [ C16] PKRU: 55555554 [ 549.186507] [ C16] Call Trace: [ 549.186510] [ C16] <IRQ> [ 549.186513] [ C16] ? srso_alias_return_thunk+0x5/0xfbef5 [ 549.186517] [ C16] __skb_pad+0xc7/0xf0 [ 549.186523] [ C16] wx_clean_rx_irq+0x355/0x3b0 [libwx] [ 549.186533] [ C16] wx_poll+0x92/0x120 [libwx] [ 549.186540] [ C16] __napi_poll+0x28/0x190 [ 549.186544] [ C16] net_rx_action+0x301/0x3f0 [ 549.186548] [ C16] ? srso_alias_return_thunk+0x5/0xfbef5 [ 549.186551] [ C16] ? __raw_spin_lock_irqsave+0x1e/0x50 [ 549.186554] [ C16] ? srso_alias_return_thunk+0x5/0xfbef5 [ 549.186557] [ C16] ? wake_up_nohz_cpu+0x35/0x160 [ 549.186559] [ C16] ? srso_alias_return_thunk+0x5/0xfbef5 [ 549.186563] [ C16] handle_softirqs+0xf9/0x2c0 [ 549.186568] [ C16] __irq_exit_rcu+0xc7/0x130 [ 549.186572] [ C16] common_interrupt+0xb8/0xd0 [ 549.186576] [ C16] </IRQ> [ 549.186577] [ C16] <TASK> [ 549.186579] [ C16] asm_common_interrupt+0x22/0x40 [ 549.186582] [ C16] RIP: 0010:cpuidle_enter_state+0xc2/0x420 [ 549.186585] [ C16] Code: 00 00 e8 11 0e 5e ff e8 ac f0 ff ff 49 89 c5 0f 1f 44 00 00 31 ff e8 0d ed 5c ff 45 84 ff 0f 85 40 02 00 00 fb 0f 1f 44 00 00 <45> 85 f6 0f 88 84 01 00 00 49 63 d6 48 8d 04 52 48 8d 04 82 49 8d [ 549.186587] [ C16] RSP: 0018:ffffb391c0277e78 EFLAGS: 00000246 [ 549.186590] [ C16] RAX: ffff8fef5ae40000 RBX: 0000000000000003 RCX: 0000000000000000 [ 549.186591] [ C16] RDX: 0000007fde0faac5 RSI: ffffffff826e53f6 RDI: ffffffff826fa9b3 [ 549.186593] [ C16] RBP: ffff8fe7c3a20800 R08: 0000000000000002 R09: 0000000000000000 [ 549.186595] [ C16] R10: 0000000000000000 R11: 000000000000ffff R12: ffffffff82ed7a40 [ 549.186596] [ C16] R13: 0000007fde0faac5 R14: 0000000000000003 R15: 0000000000000000 [ 549.186601] [ C16] ? cpuidle_enter_state+0xb3/0x420 [ 549.186605] [ C16] cpuidle_en ---truncated---

What

In the Linux kernel, the following vulnerability has been resolved: net: libwx: properly reset Rx ring descriptor When device reset is triggered by feature changes such as toggling Rx VLAN offload, wx->do_reset() is called to reinitialize Rx rings. The hardware descriptor ring may retain stale values from previous sessions. And only set the length to 0 in rx_desc[0] would result in building malformed SKBs. Fix it to ensure a clean slate after device reset. [ 549.186435] [ C16] ------------[ cut here ]------------ [ 549.186457] [ C16] kernel BUG at net/core/skbuff.c:2814! [ 549.186468] [ C16] Oops: invalid opcode: 0000 [#1] SMP NOPTI [ 549.186472] [ C16] CPU: 16 UID: 0 PID: 0 Comm: swapper/16 Kdump: loaded Not tainted 6.16.0-rc4+ #23 PREEMPT(voluntary) [ 549.186476] [ C16] Hardware name: Micro-Star International Co., Ltd. MS-7E16/X670E GAMING PLUS WIFI (MS-7E16), BIOS 1.90 12/31/2024 [ 549.186478] [ C16] RIP: 0010:__pskb_pull_tail+0x3ff/0x510 [ 549.186484] [ C16] Code: 06 f0 ff 4f 34 74 7b 4d 8b 8c 24 c8 00 00 00 45 8b 84 24 c0 00 00 00 e9 c8 fd ff ff 48 c7 44 24 08 00 00 00 00 e9 5e fe ff ff <0f> 0b 31 c0 e9 23 90 5b ff 41 f7 c6 ff 0f 00 00 75 bf 49 8b 06 a8 [ 549.186487] [ C16] RSP: 0018:ffffb391c0640d70 EFLAGS: 00010282 [ 549.186490] [ C16] RAX: 00000000fffffff2 RBX: ffff8fe7e4d40200 RCX: 00000000fffffff2 [ 549.186492] [ C16] RDX: ffff8fe7c3a4bf8e RSI: 0000000000000180 RDI: ffff8fe7c3a4bf40 [ 549.186494] [ C16] RBP: ffffb391c0640da8 R08: ffff8fe7c3a4c0c0 R09: 000000000000000e [ 549.186496] [ C16] R10: ffffb391c0640d88 R11: 000000000000000e R12: ffff8fe7e4d40200 [ 549.186497] [ C16] R13: 00000000fffffff2 R14: ffff8fe7fa01a000 R15: 00000000fffffff2 [ 549.186499] [ C16] FS: 0000000000000000(0000) GS:ffff8fef5ae40000(0000) knlGS:0000000000000000 [ 549.186502] [ C16] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 549.186503] [ C16] CR2: 00007f77d81d6000 CR3: 000000051a032000 CR4: 0000000000750ef0 [ 549.186505] [ C16] PKRU: 55555554 [ 549.186507] [ C16] Call Trace: [ 549.186510] [ C16] <IRQ> [ 549.186513] [ C16] ? srso_alias_return_thunk+0x5/0xfbef5 [ 549.186517] [ C16] __skb_pad+0xc7/0xf0 [ 549.186523] [ C16] wx_clean_rx_irq+0x355/0x3b0 [libwx] [ 549.186533] [ C16] wx_poll+0x92/0x120 [libwx] [ 549.186540] [ C16] __napi_poll+0x28/0x190 [ 549.186544] [ C16] net_rx_action+0x301/0x3f0 [ 549.186548] [ C16] ? srso_alias_return_thunk+0x5/0xfbef5 [ 549.186551] [ C16] ? __raw_spin_lock_irqsave+0x1e/0x50 [ 549.186554] [ C16] ? srso_alias_return_thunk+0x5/0xfbef5 [ 549.186557] [ C16] ? wake_up_nohz_cpu+0x35/0x160 [ 549.186559] [ C16] ? srso_alias_return_thunk+0x5/0xfbef5 [ 549.186563] [ C16] handle_softirqs+0xf9/0x2c0 [ 549.186568] [ C16] __irq_exit_rcu+0xc7/0x130 [ 549.186572] [ C16] common_interrupt+0xb8/0xd0 [ 549.186576] [ C16] </IRQ> [ 549.186577] [ C16] <TASK> [ 549.186579] [ C16] asm_common_interrupt+0x22/0x40 [ 549.186582] [ C16] RIP: 0010:cpuidle_enter_state+0xc2/0x420 [ 549.186585] [ C16] Code: 00 00 e8 11 0e 5e ff e8 ac f0 ff ff 49 89 c5 0f 1f 44 00 00 31 ff e8 0d ed 5c ff 45 84 ff 0f 85 40 02 00 00 fb 0f 1f 44 00 00 <45> 85 f6 0f 88 84 01 00 00 49 63 d6 48 8d 04 52 48 8d 04 82 49 8d [ 549.186587] [ C16] RSP: 0018:ffffb391c0277e78 EFLAGS: 00000246 [ 549.186590] [ C16] RAX: ffff8fef5ae40000 RBX: 0000000000000003 RCX: 0000000000000000 [ 549.186591] [ C16] RDX: 0000007fde0faac5 RSI: ffffffff826e53f6 RDI: ffffffff826fa9b3 [ 549.186593] [ C16] RBP: ffff8fe7c3a20800 R08: 0000000000000002 R09: 0000000000000000 [ 549.186595] [ C16] R10: 0000000000000000 R11: 000000000000ffff R12: ffffffff82ed7a40 [ 549.186596] [ C16] R13: 0000007fde0faac5 R14: 0000000000000003 R15: 0000000000000000 [ 549.186601] [ C16] ? cpuidle_enter_state+0xb3/0x420 [ 549.186605] [ C16] cpuidle_en ---truncated---

Why

The product does not initialize a critical resource.

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: libwx: properly reset Rx ring descriptor When device reset is triggered by feature changes such as toggling Rx VLAN offload, wx->do_reset() is called to reinitialize Rx rings. The hardware descriptor ring may retain stale values from previous sessions. And only set the length to 0 in rx_desc[0] would result in building malformed SKBs. Fix it to ensure a clean slate after device reset. [ 549.186435] [ C16] ------------[ cut here ]------------ [ 549.186457] [ C16] kernel BUG at net/core/skbuff.c:2814! [ 549.186468] [ C16] Oops: invalid opcode: 0000 [#1] SMP NOPTI [ 549.186472] [ C16] CPU: 16 UID: 0 PID: 0 Comm: swapper/16 Kdump: loaded Not tainted 6.16.0-rc4+ #23 PREEMPT(voluntary) [ 549.186476] [ C16] Hardware name: Micro-Star International Co., Ltd. MS-7E16/X670E GAMING PLUS WIFI (MS-7E16), BIOS 1.90 12/31/2024 [ 549.186478] [ C16] RIP: 0010:__pskb_pull_tail+0x3ff/0x510 [ 549.186484] [ C16] Code: 06 f0 ff 4f 34 74 7b 4d 8b 8c 24 c8 00 00 00 45 8b 84 24 c0 00 00 00 e9 c8 fd ff ff 48 c7 44 24 08 00 00 00 00 e9 5e fe ff ff <0f> 0b 31 c0 e9 23 90 5b ff 41 f7 c6 ff 0f 00 00 75 bf 49 8b 06 a8 [ 549.186487] [ C16] RSP: 0018:ffffb391c0640d70 EFLAGS: 00010282 [ 549.186490] [ C16] RAX: 00000000fffffff2 RBX: ffff8fe7e4d40200 RCX: 00000000fffffff2 [ 549.186492] [ C16] RDX: ffff8fe7c3a4bf8e RSI: 0000000000000180 RDI: ffff8fe7c3a4bf40 [ 549.186494] [ C16] RBP: ffffb391c0640da8 R08: ffff8fe7c3a4c0c0 R09: 000000000000000e [ 549.186496] [ C16] R10: ffffb391c0640d88 R11: 000000000000000e R12: ffff8fe7e4d40200 [ 549.186497] [ C16] R13: 00000000fffffff2 R14: ffff8fe7fa01a000 R15: 00000000fffffff2 [ 549.186499] [ C16] FS: 0000000000000000(0000) GS:ffff8fef5ae40000(0000) knlGS:0000000000000000 [ 549.186502] [ C16] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 549.186503] [ C16] CR2: 00007f77d81d6000 CR3: 000000051a032000 CR4: 0000000000750ef0 [ 549.186505] [ C16] PKRU: 55555554 [ 549.186507] [ C16] Call Trace: [ 549.186510] [ C16] <IRQ> [ 549.186513] [ C16] ? srso_alias_return_thunk+0x5/0xfbef5 [ 549.186517] [ C16] __skb_pad+0xc7/0xf0 [ 549.186523] [ C16] wx_clean_rx_irq+0x355/0x3b0 [libwx] [ 549.186533] [ C16] wx_poll+0x92/0x120 [libwx] [ 549.186540] [ C16] __napi_poll+0x28/0x190 [ 549.186544] [ C16] net_rx_action+0x301/0x3f0 [ 549.186548] [ C16] ? srso_alias_return_thunk+0x5/0xfbef5 [ 549.186551] [ C16] ? __raw_spin_lock_irqsave+0x1e/0x50 [ 549.186554] [ C16] ? srso_alias_return_thunk+0x5/0xfbef5 [ 549.186557] [ C16] ? wake_up_nohz_cpu+0x35/0x160 [ 549.186559] [ C16] ? srso_alias_return_thunk+0x5/0xfbef5 [ 549.186563] [ C16] handle_softirqs+0xf9/0x2c0 [ 549.186568] [ C16] __irq_exit_rcu+0xc7/0x130 [ 549.186572] [ C16] common_interrupt+0xb8/0xd0 [ 549.186576] [ C16] </IRQ> [ 549.186577] [ C16] <TASK> [ 549.186579] [ C16] asm_common_interrupt+0x22/0x40 [ 549.186582] [ C16] RIP: 0010:cpuidle_enter_state+0xc2/0x420 [ 549.186585] [ C16] Code: 00 00 e8 11 0e 5e ff e8 ac f0 ff ff 49 89 c5 0f 1f 44 00 00 31 ff e8 0d ed 5c ff 45 84 ff 0f 85 40 02 00 00 fb 0f 1f 44 00 00 <45> 85 f6 0f 88 84 01 00 00 49 63 d6 48 8d 04 52 48 8d 04 82 49 8d [ 549.186587] [ C16] RSP: 0018:ffffb391c0277e78 EFLAGS: 00000246 [ 549.186590] [ C16] RAX: ffff8fef5ae40000 RBX: 0000000000000003 RCX: 0000000000000000 [ 549.186591] [ C16] RDX: 0000007fde0faac5 RSI: ffffffff826e53f6 RDI: ffffffff826fa9b3 [ 549.186593] [ C16] RBP: ffff8fe7c3a20800 R08: 0000000000000002 R09: 0000000000000000 [ 549.186595] [ C16] R10: 0000000000000000 R11: 000000000000ffff R12: ffffffff82ed7a40 [ 549.186596] [ C16] R13: 0000007fde0faac5 R14: 0000000000000003 R15: 0000000000000000 [ 549.186601] [ C16] ? cpuidle_enter_state+0xb3/0x420 [ 549.186605] [ C16] cpuidle_en ---truncated---

Why

The product does not initialize a critical resource.

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 → Missing Initialization of Resource → 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-909 ↗

CWE-909: Missing Initialization of Resource. The product does not initialize a critical resource.

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

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

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

Official authority intelligence

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

BSI · German · WID-SEC-2025-1858Linux 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
CERT-FR · French · CERTFR-2026-AVI-0246Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2025-38520 Référence CVE CVE-2025-38521 https://www.cve.org/CVERecord?id=CVE-2025-38521 Référence CVE CVE-2025-38524 https://www.cve.org/CVERecord?id=CVE-2025-38524 Référence CVE CVE-2025-38526 https://www.cve.org/CVERecord?id=CVE-2025-38526 Référence CVE CVE-2025-38527 https://www.cve.org/CVERecord?id=CVE-2025-38527 Référence CVE CVE-2025-38528 https://www.cve.org/CVERecord?id=CVE-2025-38528 Référence CVE CVE-2025-38529 https://www.cve.org/CVERecord?id=CVE-2025-38529 Référence CVE CVE-2025-38530 https://www.cve.org/CVERecord?id=CVE-2025-38530 Référence CVE CVE-2025-38531 https://www.cve.org/CVERecord?id=CVE-2025-38531 Référence CVE CVE-2025-38532 https://www.cve.org/CVERecord?id=CVE-2025-38532 Référence CVE CVE-2025-38533 https://www.cve.org/CVERecord?id=CVE-2025-38533 Référence CVE CVE-2025-38535 https://www.cve.org/CVERecord?id=CVE-2025-38535 Référence CVE CVE-2025-38537 https://www.cve.org/CVERecord?id=CVE-2025-38537 Référence CVE CVE-2025-38538 https://www.cve.org/CVERecord?id=CVE-2025-38538 Référence CVE CVE-2025-38539 https://www.cve.org/CVERecord?id=CVE-2025-38539 Référence CVE CVE-2025-38540 https://www.cve.org/CVERecord?id=CVE-2025-38540 Référence CVE CVE-2025-38542 https://www.cve.org/CVERecord?id=CVE-2025-38542 Référence CVE CVE-2025-38543 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-38520 Référence CVE CVE-2025-38521 https://www.cve.org/CVERecord?id=CVE-2025-38521 Référence CVE CVE-2025-38524 https://www.cve.org/CVERecord?id=CVE-2025-38524 Référence CVE CVE-2025-38526 https://www.cve.org/CVERecord?id=CVE-2025-38526 Référence CVE CVE-2025-38527 https://www.cve.org/CVERecord?id=CVE-2025-38527 Référence CVE CVE-2025-38528 https://www.cve.org/CVERecord?id=CVE-2025-38528 Référence CVE CVE-2025-38529 https://www.cve.org/CVERecord?id=CVE-2025-38529 Référence CVE CVE-2025-38530 https://www.cve.org/CVERecord?id=CVE-2025-38530 Référence CVE CVE-2025-38531 https://www.cve.org/CVERecord?id=CVE-2025-38531 Référence CVE CVE-2025-38532 https://www.cve.org/CVERecord?id=CVE-2025-38532 Référence CVE CVE-2025-38533 https://www.cve.org/CVERecord?id=CVE-2025-38533 Référence CVE CVE-2025-38535 https://www.cve.org/CVERecord?id=CVE-2025-38535 Référence CVE CVE-2025-38537 https://www.cve.org/CVERecord?id=CVE-2025-38537 Référence CVE CVE-2025-38538 https://www.cve.org/CVERecord?id=CVE-2025-38538 Référence CVE CVE-2025-38539 https://www.cve.org/CVERecord?id=CVE-2025-38539 Référence CVE CVE-2025-38540 https://www.cve.org/CVERecord?id=CVE-2025-38540 Référence CVE CVE-2025-38542 https://www.cve.org/CVERecord?id=CVE-2025-38542 Référence CVE CVE-2025-38543 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-38520 Référence CVE CVE-2025-38521 https://www.cve.org/CVERecord?id=CVE-2025-38521 Référence CVE CVE-2025-38524 https://www.cve.org/CVERecord?id=CVE-2025-38524 Référence CVE CVE-2025-38526 https://www.cve.org/CVERecord?id=CVE-2025-38526 Référence CVE CVE-2025-38527 https://www.cve.org/CVERecord?id=CVE-2025-38527 Référence CVE CVE-2025-38528 https://www.cve.org/CVERecord?id=CVE-2025-38528 Référence CVE CVE-2025-38529 https://www.cve.org/CVERecord?id=CVE-2025-38529 Référence CVE CVE-2025-38530 https://www.cve.org/CVERecord?id=CVE-2025-38530 Référence CVE CVE-2025-38531 https://www.cve.org/CVERecord?id=CVE-2025-38531 Référence CVE CVE-2025-38532 https://www.cve.org/CVERecord?id=CVE-2025-38532 Référence CVE CVE-2025-38533 https://www.cve.org/CVERecord?id=CVE-2025-38533 Référence CVE CVE-2025-38535 https://www.cve.org/CVERecord?id=CVE-2025-38535 Référence CVE CVE-2025-38537 https://www.cve.org/CVERecord?id=CVE-2025-38537 Référence CVE CVE-2025-38538 https://www.cve.org/CVERecord?id=CVE-2025-38538 Référence CVE CVE-2025-38539 https://www.cve.org/CVERecord?id=CVE-2025-38539 Référence CVE CVE-2025-38540 https://www.cve.org/CVERecord?id=CVE-2025-38540 Référence CVE CVE-2025-38542 https://www.cve.org/CVERecord?id=CVE-2025-38542 Référence CVE CVE-2025-38543 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-38520 Référence CVE CVE-2025-38521 https://www.cve.org/CVERecord?id=CVE-2025-38521 Référence CVE CVE-2025-38524 https://www.cve.org/CVERecord?id=CVE-2025-38524 Référence CVE CVE-2025-38526 https://www.cve.org/CVERecord?id=CVE-2025-38526 Référence CVE CVE-2025-38527 https://www.cve.org/CVERecord?id=CVE-2025-38527 Référence CVE CVE-2025-38528 https://www.cve.org/CVERecord?id=CVE-2025-38528 Référence CVE CVE-2025-38529 https://www.cve.org/CVERecord?id=CVE-2025-38529 Référence CVE CVE-2025-38530 https://www.cve.org/CVERecord?id=CVE-2025-38530 Référence CVE CVE-2025-38531 https://www.cve.org/CVERecord?id=CVE-2025-38531 Référence CVE CVE-2025-38532 https://www.cve.org/CVERecord?id=CVE-2025-38532 Référence CVE CVE-2025-38533 https://www.cve.org/CVERecord?id=CVE-2025-38533 Référence CVE CVE-2025-38535 https://www.cve.org/CVERecord?id=CVE-2025-38535 Référence CVE CVE-2025-38537 https://www.cve.org/CVERecord?id=CVE-2025-38537 Référence CVE CVE-2025-38538 https://www.cve.org/CVERecord?id=CVE-2025-38538 Référence CVE CVE-2025-38539 https://www.cve.org/CVERecord?id=CVE-2025-38539 Référence CVE CVE-2025-38540 https://www.cve.org/CVERecord?id=CVE-2025-38540 Référence CVE CVE-2025-38542 https://www.cve.org/CVERecord?id=CVE-2025-38542 Référence CVE CVE-2025-38543 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-38520 Référence CVE CVE-2025-38521 https://www.cve.org/CVERecord?id=CVE-2025-38521 Référence CVE CVE-2025-38524 https://www.cve.org/CVERecord?id=CVE-2025-38524 Référence CVE CVE-2025-38526 https://www.cve.org/CVERecord?id=CVE-2025-38526 Référence CVE CVE-2025-38527 https://www.cve.org/CVERecord?id=CVE-2025-38527 Référence CVE CVE-2025-38528 https://www.cve.org/CVERecord?id=CVE-2025-38528 Référence CVE CVE-2025-38529 https://www.cve.org/CVERecord?id=CVE-2025-38529 Référence CVE CVE-2025-38530 https://www.cve.org/CVERecord?id=CVE-2025-38530 Référence CVE CVE-2025-38531 https://www.cve.org/CVERecord?id=CVE-2025-38531 Référence CVE CVE-2025-38532 https://www.cve.org/CVERecord?id=CVE-2025-38532 Référence CVE CVE-2025-38533 https://www.cve.org/CVERecord?id=CVE-2025-38533 Référence CVE CVE-2025-38535 https://www.cve.org/CVERecord?id=CVE-2025-38535 Référence CVE CVE-2025-38537 https://www.cve.org/CVERecord?id=CVE-2025-38537 Référence CVE CVE-2025-38538 https://www.cve.org/CVERecord?id=CVE-2025-38538 Référence CVE CVE-2025-38539 https://www.cve.org/CVERecord?id=CVE-2025-38539 Référence CVE CVE-2025-38540 https://www.cve.org/CVERecord?id=CVE-2025-38540 Référence CVE CVE-2025-38542 https://www.cve.org/CVERecord?id=CVE-2025-38542 Référence CVE CVE-2025-38543 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-38521 Référence CVE CVE-2025-38524 https://www.cve.org/CVERecord?id=CVE-2025-38524 Référence CVE CVE-2025-38525 https://www.cve.org/CVERecord?id=CVE-2025-38525 Référence CVE CVE-2025-38526 https://www.cve.org/CVERecord?id=CVE-2025-38526 Référence CVE CVE-2025-38527 https://www.cve.org/CVERecord?id=CVE-2025-38527 Référence CVE CVE-2025-38528 https://www.cve.org/CVERecord?id=CVE-2025-38528 Référence CVE CVE-2025-38529 https://www.cve.org/CVERecord?id=CVE-2025-38529 Référence CVE CVE-2025-38530 https://www.cve.org/CVERecord?id=CVE-2025-38530 Référence CVE CVE-2025-38531 https://www.cve.org/CVERecord?id=CVE-2025-38531 Référence CVE CVE-2025-38532 https://www.cve.org/CVERecord?id=CVE-2025-38532 Référence CVE CVE-2025-38533 https://www.cve.org/CVERecord?id=CVE-2025-38533 Référence CVE CVE-2025-38534 https://www.cve.org/CVERecord?id=CVE-2025-38534 Référence CVE CVE-2025-38535 https://www.cve.org/CVERecord?id=CVE-2025-38535 Référence CVE CVE-2025-38537 https://www.cve.org/CVERecord?id=CVE-2025-38537 Référence CVE CVE-2025-38538 https://www.cve.org/CVERecord?id=CVE-2025-38538 Référence CVE CVE-2025-38539 https://www.cve.org/CVERecord?id=CVE-2025-38539 Référence CVE CVE-2025-38540 https://www.cve.org/CVERecord?id=CVE-2025-38540 Référence CVE CVE-2025-38542 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-38521 Référence CVE CVE-2025-38524 https://www.cve.org/CVERecord?id=CVE-2025-38524 Référence CVE CVE-2025-38525 https://www.cve.org/CVERecord?id=CVE-2025-38525 Référence CVE CVE-2025-38526 https://www.cve.org/CVERecord?id=CVE-2025-38526 Référence CVE CVE-2025-38527 https://www.cve.org/CVERecord?id=CVE-2025-38527 Référence CVE CVE-2025-38528 https://www.cve.org/CVERecord?id=CVE-2025-38528 Référence CVE CVE-2025-38529 https://www.cve.org/CVERecord?id=CVE-2025-38529 Référence CVE CVE-2025-38530 https://www.cve.org/CVERecord?id=CVE-2025-38530 Référence CVE CVE-2025-38531 https://www.cve.org/CVERecord?id=CVE-2025-38531 Référence CVE CVE-2025-38532 https://www.cve.org/CVERecord?id=CVE-2025-38532 Référence CVE CVE-2025-38533 https://www.cve.org/CVERecord?id=CVE-2025-38533 Référence CVE CVE-2025-38534 https://www.cve.org/CVERecord?id=CVE-2025-38534 Référence CVE CVE-2025-38535 https://www.cve.org/CVERecord?id=CVE-2025-38535 Référence CVE CVE-2025-38537 https://www.cve.org/CVERecord?id=CVE-2025-38537 Référence CVE CVE-2025-38538 https://www.cve.org/CVERecord?id=CVE-2025-38538 Référence CVE CVE-2025-38539 https://www.cve.org/CVERecord?id=CVE-2025-38539 Référence CVE CVE-2025-38540 https://www.cve.org/CVERecord?id=CVE-2025-38540 Référence CVE CVE-2025-38542 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-38521 Référence CVE CVE-2025-38524 https://www.cve.org/CVERecord?id=CVE-2025-38524 Référence CVE CVE-2025-38525 https://www.cve.org/CVERecord?id=CVE-2025-38525 Référence CVE CVE-2025-38526 https://www.cve.org/CVERecord?id=CVE-2025-38526 Référence CVE CVE-2025-38527 https://www.cve.org/CVERecord?id=CVE-2025-38527 Référence CVE CVE-2025-38528 https://www.cve.org/CVERecord?id=CVE-2025-38528 Référence CVE CVE-2025-38529 https://www.cve.org/CVERecord?id=CVE-2025-38529 Référence CVE CVE-2025-38530 https://www.cve.org/CVERecord?id=CVE-2025-38530 Référence CVE CVE-2025-38531 https://www.cve.org/CVERecord?id=CVE-2025-38531 Référence CVE CVE-2025-38532 https://www.cve.org/CVERecord?id=CVE-2025-38532 Référence CVE CVE-2025-38533 https://www.cve.org/CVERecord?id=CVE-2025-38533 Référence CVE CVE-2025-38534 https://www.cve.org/CVERecord?id=CVE-2025-38534 Référence CVE CVE-2025-38535 https://www.cve.org/CVERecord?id=CVE-2025-38535 Référence CVE CVE-2025-38537 https://www.cve.org/CVERecord?id=CVE-2025-38537 Référence CVE CVE-2025-38538 https://www.cve.org/CVERecord?id=CVE-2025-38538 Référence CVE CVE-2025-38539 https://www.cve.org/CVERecord?id=CVE-2025-38539 Référence CVE CVE-2025-38540 https://www.cve.org/CVERecord?id=CVE-2025-38540 Référence CVE CVE-2025-38542 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
Linux: 3c47e8ae113a68da47987750d9896e325d0aeedd < d510116c80b37efb100ce8d5ee326214b0157293, 3c47e8ae113a68da47987750d9896e325d0aeedd < 10e27b2a6ebeda49e9c2897a699d3ce1ded565ee, 3c47e8ae113a68da47987750d9896e325d0aeedd < ee527d3fba4dae1d619d2d0438624002c8e99e24, 3c47e8ae113a68da47987750d9896e325d0aeedd < d992ed7e1b687ad7df0763d3e015a5358646210b, 6.3
Fixed
Linux: < 6.3, 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
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 16 Aug 2025 · Last source change 5 Aug 2026, 12:02 UTC · CWE-909 · Missing Initialization of Resource

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2025-27887
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

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

Material change intelligence

What changed after publication

View recent updates →

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

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2025-27887↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2025-38532 · cve.blacktree.nl