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

bpf, test_run: Fix use-after-free issue in eth_skb_pkt_type()

Linux · Linux

Official source article: Siemens SSA-019113 ↗. Check the applicable product and release in the original source.

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

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

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

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

Evidence used

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

Compensating controls

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

Verification

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

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

Cross-source reconciliation

Remediation availability differs by product scope

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

Distribution package intelligence

Release-specific package status

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

24 package states
Package result overrides the generic status

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

Repository candidate not checked

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

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.17-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.133-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.17-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.17-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-intelAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-tegraAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

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

1 current
SSA-019113 · CSAF 2.0 · revision 2 · interimSiemens ProductCERTSSA-019113: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP V3.1.6
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.6
  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0) >= V3.1.6
  • SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0) >= V3.1.6
Summary
In the Linux kernel, the following vulnerability has been resolved: bpf, test_run: Fix use-after-free issue in eth_skb_pkt_type() KMSAN reported a use-after-free issue in eth_skb_pkt_type()[1]. The cause of the issue was that eth_skb_pkt_type() accessed skb's data that didn't contain an Ethernet header. This occurs when bpf_prog_test_run_xdp() passes an invalid value as the user_data argument to bpf_test_init(). Fix this by returning an error when user_data is less than ETH_HLEN in bpf_test_init(). Additionally, remove the check for "if (user_size > size)" as it is unnecessary. [1] BUG: KMSAN: use-after-free in eth_skb_pkt_type include/linux/etherdevice.h:627 [inline] BUG: KMSAN: use-after-free in eth_type_trans+0x4ee/0x980 net/ethernet/eth.c:165 eth_skb_pkt_type include/linux/etherdevice.h:627 [inline] eth_type_trans+0x4ee/0x980 net/ethernet/eth.c:165 __xdp_build_skb_from_frame+0x5a8/0xa50 net/core/xdp.c:635 xdp_recv_frames net/bpf/test_run.c:272 [inline] xdp_test_run_batch net/bpf/test_run.c:361 [inline] bpf_test_run_xdp_live+0x2954/0x3330 net/bpf/test_run.c:390 bpf_prog_test_run_xdp+0x148e/0x1b10 net/bpf/test_run.c:1318 bpf_prog_test_run+0x5b7/0xa30 kernel/bpf/syscall.c:4371 __sys_bpf+0x6a6/0xe20 kernel/bpf/syscall.c:5777 __do_sys_bpf kernel/bpf/syscall.c:5866 [inline] __se_sys_bpf kernel/bpf/syscall.c:5864 [inline] __x64_sys_bpf+0xa4/0xf0 kernel/bpf/syscall.c:5864 x64_sys_call+0x2ea0/0x3d90 arch/x86/include/generated/asm/syscalls_64.h:322 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xd9/0x1d0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f Uninit was created at: free_pages_prepare mm/page_alloc.c:1056 [inline] free_unref_page+0x156/0x1320 mm/page_alloc.c:2657 __free_pages+0xa3/0x1b0 mm/page_alloc.c:4838 bpf_ringbuf_free kernel/bpf/ringbuf.c:226 [inline] ringbuf_map_free+0xff/0x1e0 kernel/bpf/ringbuf.c:235 bpf_map_free kernel/bpf/syscall.c:838 [inline] bpf_map_free_deferred+0x17c/0x310 kernel/bpf/syscall.c:862 process_one_work kernel/workqueue.c:3229 [inline] process_scheduled_works+0xa2b/0x1b60 kernel/workqueue.c:3310 worker_thread+0xedf/0x1550 kernel/workqueue.c:3391 kthread+0x535/0x6b0 kernel/kthread.c:389 ret_from_fork+0x6e/0x90 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 CPU: 1 UID: 0 PID: 17276 Comm: syz.1.16450 Not tainted 6.12.0-05490-g9bb88c659673 #8 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-3.fc41 04/01/2014
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.

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

Official European source

ENISA European Vulnerability Database

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

1 current
ENISA EUVD identifier

EUVD-2025-8435

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: bpf, test_run: Fix use-after-free issue in eth_skb_pkt_type() KMSAN reported a use-after-free issue in eth_skb_pkt_type()[1]. The cause of the issue was that eth_skb_pkt_type() accessed skb's data that didn't contain an Ethernet header. This occurs when bpf_prog_test_run_xdp() passes an invalid value as the user_data argument to bpf_test_init(). Fix this by returning an error when user_data is less than ETH_HLEN in bpf_test_init(). Additionally, remove the check for "if (user_size > size)" as it is unnecessary. [1] BUG: KMSAN: use-after-free in eth_skb_pkt_type include/linux/etherdevice.h:627 [inline] BUG: KMSAN: use-after-free in eth_type_trans+0x4ee/0x980 net/ethernet/eth.c:165 eth_skb_pkt_type include/linux/etherdevice.h:627 [inline] eth_type_trans+0x4ee/0x980 net/ethernet/eth.c:165 __xdp_build_skb_from_frame+0x5a8/0xa50 net/core/xdp.c:635 xdp_recv_frames net/bpf/test_run.c:272 [inline] xdp_test_run_batch net/bpf/test_run.c:361 [inline] bpf_test_run_xdp_live+0x2954/0x3330 net/bpf/test_run.c:390 bpf_prog_test_run_xdp+0x148e/0x1b10 net/bpf/test_run.c:1318 bpf_prog_test_run+0x5b7/0xa30 kernel/bpf/syscall.c:4371 __sys_bpf+0x6a6/0xe20 kernel/bpf/syscall.c:5777 __do_sys_bpf kernel/bpf/syscall.c:5866 [inline] __se_sys_bpf kernel/bpf/syscall.c:5864 [inline] __x64_sys_bpf+0xa4/0xf0 kernel/bpf/syscall.c:5864 x64_sys_call+0x2ea0/0x3d90 arch/x86/include/generated/asm/syscalls_64.h:322 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xd9/0x1d0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f Uninit was created at: free_pages_prepare mm/page_alloc.c:1056 [inline] free_unref_page+0x156/0x1320 mm/page_alloc.c:2657 __free_pages+0xa3/0x1b0 mm/page_alloc.c:4838 bpf_ringbuf_free kernel/bpf/ringbuf.c:226 [inline] ringbuf_map_free+0xff/0x1e0 kernel/bpf/ringbuf.c:235 bpf_map_free kernel/bpf/syscall.c:838 [inline] bpf_map_free_deferred+0x17c/0x310 kernel/bpf/syscall.c:862 process_one_work kernel/workqueue.c:3229 [inline] process_scheduled_works+0xa2b/0x1b60 kernel/workqueue.c:3310 worker_thread+0xedf/0x1550 kernel/workqueue.c:3391 kthread+0x535/0x6b0 kernel/kthread.c:389 ret_from_fork+0x6e/0x90 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 CPU: 1 UID: 0 PID: 17276 Comm: syz.1.16450 Not tainted 6.12.0-05490-g9bb88c659673 #8 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-3.fc41 04/01/2014

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
7.8 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

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

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: bpf, test_run: Fix use-after-free issue in eth_skb_pkt_type() KMSAN reported a use-after-free issue in eth_skb_pkt_type()[1]. The cause of the issue was that eth_skb_pkt_type() accessed skb's data that didn't contain an Ethernet header. This occurs when bpf_prog_test_run_xdp() passes an invalid value as the user_data argument to bpf_test_init(). Fix this by returning an error when user_data is less than ETH_HLEN in bpf_test_init(). Additionally, remove the check for "if (user_size > size)" as it is unnecessary. [1] BUG: KMSAN: use-after-free in eth_skb_pkt_type include/linux/etherdevice.h:627 [inline] BUG: KMSAN: use-after-free in eth_type_trans+0x4ee/0x980 net/ethernet/eth.c:165 eth_skb_pkt_type include/linux/etherdevice.h:627 [inline] eth_type_trans+0x4ee/0x980 net/ethernet/eth.c:165 __xdp_build_skb_from_frame+0x5a8/0xa50 net/core/xdp.c:635 xdp_recv_frames net/bpf/test_run.c:272 [inline] xdp_test_run_batch net/bpf/test_run.c:361 [inline] bpf_test_run_xdp_live+0x2954/0x3330 net/bpf/test_run.c:390 bpf_prog_test_run_xdp+0x148e/0x1b10 net/bpf/test_run.c:1318 bpf_prog_test_run+0x5b7/0xa30 kernel/bpf/syscall.c:4371 __sys_bpf+0x6a6/0xe20 kernel/bpf/syscall.c:5777 __do_sys_bpf kernel/bpf/syscall.c:5866 [inline] __se_sys_bpf kernel/bpf/syscall.c:5864 [inline] __x64_sys_bpf+0xa4/0xf0 kernel/bpf/syscall.c:5864 x64_sys_call+0x2ea0/0x3d90 arch/x86/include/generated/asm/syscalls_64.h:322 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xd9/0x1d0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f Uninit was created at: free_pages_prepare mm/page_alloc.c:1056 [inline] free_unref_page+0x156/0x1320 mm/page_alloc.c:2657 __free_pages+0xa3/0x1b0 mm/page_alloc.c:4838 bpf_ringbuf_free kernel/bpf/ringbuf.c:226 [inline] ringbuf_map_free+0xff/0x1e0 kernel/bpf/ringbuf.c:235 bpf_map_free kernel/bpf/syscall.c:838 [inline] bpf_map_free_deferred+0x17c/0x310 kernel/bpf/syscall.c:862 process_one_work kernel/workqueue.c:3229 [inline] process_scheduled_works+0xa2b/0x1b60 kernel/workqueue.c:3310 worker_thread+0xedf/0x1550 kernel/workqueue.c:3391 kthread+0x535/0x6b0 kernel/kthread.c:389 ret_from_fork+0x6e/0x90 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 CPU: 1 UID: 0 PID: 17276 Comm: syz.1.16450 Not tainted 6.12.0-05490-g9bb88c659673 #8 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-3.fc41 04/01/2014

What

In the Linux kernel, the following vulnerability has been resolved: bpf, test_run: Fix use-after-free issue in eth_skb_pkt_type() KMSAN reported a use-after-free issue in eth_skb_pkt_type()[1]. The cause of the issue was that eth_skb_pkt_type() accessed skb's data that didn't contain an Ethernet header. This occurs when bpf_prog_test_run_xdp() passes an invalid value as the user_data argument to bpf_test_init(). Fix this by returning an error when user_data is less than ETH_HLEN in bpf_test_init(). Additionally, remove the check for "if (user_size > size)" as it is unnecessary. [1] BUG: KMSAN: use-after-free in eth_skb_pkt_type include/linux/etherdevice.h:627 [inline] BUG: KMSAN: use-after-free in eth_type_trans+0x4ee/0x980 net/ethernet/eth.c:165 eth_skb_pkt_type include/linux/etherdevice.h:627 [inline] eth_type_trans+0x4ee/0x980 net/ethernet/eth.c:165 __xdp_build_skb_from_frame+0x5a8/0xa50 net/core/xdp.c:635 xdp_recv_frames net/bpf/test_run.c:272 [inline] xdp_test_run_batch net/bpf/test_run.c:361 [inline] bpf_test_run_xdp_live+0x2954/0x3330 net/bpf/test_run.c:390 bpf_prog_test_run_xdp+0x148e/0x1b10 net/bpf/test_run.c:1318 bpf_prog_test_run+0x5b7/0xa30 kernel/bpf/syscall.c:4371 __sys_bpf+0x6a6/0xe20 kernel/bpf/syscall.c:5777 __do_sys_bpf kernel/bpf/syscall.c:5866 [inline] __se_sys_bpf kernel/bpf/syscall.c:5864 [inline] __x64_sys_bpf+0xa4/0xf0 kernel/bpf/syscall.c:5864 x64_sys_call+0x2ea0/0x3d90 arch/x86/include/generated/asm/syscalls_64.h:322 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xd9/0x1d0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f Uninit was created at: free_pages_prepare mm/page_alloc.c:1056 [inline] free_unref_page+0x156/0x1320 mm/page_alloc.c:2657 __free_pages+0xa3/0x1b0 mm/page_alloc.c:4838 bpf_ringbuf_free kernel/bpf/ringbuf.c:226 [inline] ringbuf_map_free+0xff/0x1e0 kernel/bpf/ringbuf.c:235 bpf_map_free kernel/bpf/syscall.c:838 [inline] bpf_map_free_deferred+0x17c/0x310 kernel/bpf/syscall.c:862 process_one_work kernel/workqueue.c:3229 [inline] process_scheduled_works+0xa2b/0x1b60 kernel/workqueue.c:3310 worker_thread+0xedf/0x1550 kernel/workqueue.c:3391 kthread+0x535/0x6b0 kernel/kthread.c:389 ret_from_fork+0x6e/0x90 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 CPU: 1 UID: 0 PID: 17276 Comm: syz.1.16450 Not tainted 6.12.0-05490-g9bb88c659673 #8 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-3.fc41 04/01/2014

Why

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

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In the Linux kernel, the following vulnerability has been resolved: bpf, test_run: Fix use-after-free issue in eth_skb_pkt_type() KMSAN reported a use-after-free issue in eth_skb_pkt_type()[1]. The cause of the issue was that eth_skb_pkt_type() accessed skb's data that didn't contain an Ethernet header. This occurs when bpf_prog_test_run_xdp() passes an invalid value as the user_data argument to bpf_test_init(). Fix this by returning an error when user_data is less than ETH_HLEN in bpf_test_init(). Additionally, remove the check for "if (user_size > size)" as it is unnecessary. [1] BUG: KMSAN: use-after-free in eth_skb_pkt_type include/linux/etherdevice.h:627 [inline] BUG: KMSAN: use-after-free in eth_type_trans+0x4ee/0x980 net/ethernet/eth.c:165 eth_skb_pkt_type include/linux/etherdevice.h:627 [inline] eth_type_trans+0x4ee/0x980 net/ethernet/eth.c:165 __xdp_build_skb_from_frame+0x5a8/0xa50 net/core/xdp.c:635 xdp_recv_frames net/bpf/test_run.c:272 [inline] xdp_test_run_batch net/bpf/test_run.c:361 [inline] bpf_test_run_xdp_live+0x2954/0x3330 net/bpf/test_run.c:390 bpf_prog_test_run_xdp+0x148e/0x1b10 net/bpf/test_run.c:1318 bpf_prog_test_run+0x5b7/0xa30 kernel/bpf/syscall.c:4371 __sys_bpf+0x6a6/0xe20 kernel/bpf/syscall.c:5777 __do_sys_bpf kernel/bpf/syscall.c:5866 [inline] __se_sys_bpf kernel/bpf/syscall.c:5864 [inline] __x64_sys_bpf+0xa4/0xf0 kernel/bpf/syscall.c:5864 x64_sys_call+0x2ea0/0x3d90 arch/x86/include/generated/asm/syscalls_64.h:322 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xd9/0x1d0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f Uninit was created at: free_pages_prepare mm/page_alloc.c:1056 [inline] free_unref_page+0x156/0x1320 mm/page_alloc.c:2657 __free_pages+0xa3/0x1b0 mm/page_alloc.c:4838 bpf_ringbuf_free kernel/bpf/ringbuf.c:226 [inline] ringbuf_map_free+0xff/0x1e0 kernel/bpf/ringbuf.c:235 bpf_map_free kernel/bpf/syscall.c:838 [inline] bpf_map_free_deferred+0x17c/0x310 kernel/bpf/syscall.c:862 process_one_work kernel/workqueue.c:3229 [inline] process_scheduled_works+0xa2b/0x1b60 kernel/workqueue.c:3310 worker_thread+0xedf/0x1550 kernel/workqueue.c:3391 kthread+0x535/0x6b0 kernel/kthread.c:389 ret_from_fork+0x6e/0x90 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 CPU: 1 UID: 0 PID: 17276 Comm: syz.1.16450 Not tainted 6.12.0-05490-g9bb88c659673 #8 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-3.fc41 04/01/2014

Why

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

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → Use After Free → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-416 ↗

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

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

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

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

Official authority intelligence

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

ENISA EUVD · EUVD-2025-8435Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: bpf, test_run: Fix use-after-free issue in eth_skb_pkt_type() KMSAN reported a use-after-free issue in eth_skb_pkt_type()[1]. The cause of the issue was that eth_skb_pkt_type() accessed skb's data that didn't contain an Ethernet header. This occurs when bpf_prog_test_run_xdp() passes an invalid value as the user_data argument to bpf_test_init(). Fix this by returning an error when user_data is less than ETH_HLEN in bpf_test_init(). Additionally, remove the check for "if (user_size > size)" as it is unnecessary. [1] BUG: KMSAN: use-after-free in eth_skb_pkt_type include/linux/etherdevice.h:627 [inline] BUG: KMSAN: use-after-free in eth_type_trans+0x4ee/0x980 net/ethernet/eth.c:165 eth_skb_pkt_type include/linux/etherdevice.h:627 [inline] eth_type_trans+0x4ee/0x980 net/ethernet/eth.c:165 __xdp_build_skb_from_frame+0x5a8/0xa50 net/core/xdp.c:635 xdp_recv_frames net/bpf/test_run.c:272 [inline] xdp_test_run_batch net/bpf/test_run.c:361 [inline] bpf_test_run_xdp_live+0x2954/0x3330 net/bpf/test_run.c:390 bpf_prog_test_run_xdp+0x148e/0x1b10 net/bpf/test_run.c:1318 bpf_prog_test_run+0x5b7/0xa30 kernel/bpf/syscall.c:4371 __sys_bpf+0x6a6/0xe20 kernel/bpf/syscall.c:5777 __do_sys_bpf kernel/bpf/syscall.c:5866 [inline] __se_sys_bpf kernel/bpf/syscall.c:5864 [inline] __x64_sys_bpf+0xa4/0xf0 kernel/bpf/syscall.c:5864 x64_sys_call+0x2ea0/0x3d90 arch/x86/include/generated/asm/syscalls_64.h:322 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xd9/0x1d0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f Uninit was created at: free_pages_prepare mm/page_alloc.c:1056 [inline] free_unref_page+0x156/0x1320 mm/page_alloc.c:2657 __free_pages+0xa3/0x1b0 mm/page_alloc.c:4838 bpf_ringbuf_free kernel/bpf/ringbuf.c:226 [inline] ringbuf_map_free+0xff/0x1e0 kernel/bpf/ringbuf.c:235 bpf_map_free kernel/bpf/syscall.c:838 [inline] bpf_map_free_deferred+0x17c/0x310 kernel/bpf/syscall.c:862 process_one_work kernel/workqueue.c:3229 [inline] process_scheduled_works+0xa2b/0x1b60 kernel/workqueue.c:3310 worker_thread+0xedf/0x1550 kernel/workqueue.c:3391 kthread+0x535/0x6b0 kernel/kthread.c:389 ret_from_fork+0x6e/0x90 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 CPU: 1 UID: 0 PID: 17276 Comm: syz.1.16450 Not tainted 6.12.0-05490-g9bb88c659673 #8 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-3.fc41 04/01/2014

Official EUVD record ↗
BSI · German · WID-SEC-2025-0649Linux Kernel: Mehrere Schwachstellen

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht spezifizierte Effekte zu erzielen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20250402Security Bulletin 02 Apr 2025 [1.46 MB]

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 02 Apr 2025 [1.46 MB], published on 2 April 2025. Open the linked bulletin for the product, severity and reference information published in that issue.

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

24-54458, CVE-2024-56631, CVE-2024-56703, CVE-2024-56719, CVE-2024-57917, CVE-2024-57924, CVE-2024-57973, CVE-2024-57977, CVE-2024-57979, CVE-2024-58011, CVE-2024-58016, CVE-2024-58020, CVE-2024-58056, CVE-2024-58058, CVE-2024-58061, CVE-2024-58086, CVE-2025-21645, CVE-2025-21648, CVE-2025-21655, CVE-2025-21676, CVE-2025-21682, CVE-2025-21702, CVE-2025-21705, CVE-2025-21706, CVE-2025-21707, CVE-2025-21718, CVE-2025-21731, CVE-2025-21745, CVE-2025-21758, CVE-2025-21760, CVE-2025-21764, CVE-2025-21765, CVE-2025-21780, CVE-2025-21795, CVE-2025-21796, CVE-2025-21802, CVE-2025-21814, CVE-2025-21846, CVE-2025-21853, CVE-2025-21861, CVE-2025-21864, CVE-2025-21867, CVE-2025-21875, CVE-2025-21887, CVE-2025-21913, CVE-2025-21919, CVE-2025-21925, CVE-2025-21926, CVE-2025-21938, CVE-2025-21959, CVE-2025-21999, CVE-2025-22005, CVE-2025-22015, CVE-2025-22055, CVE-2025-22056, CVE-2025-22060, CVE-2025-22083, CVE-2025-22090, CVE-2025-22095, CVE-2025-22107, CVE-2025-22111, CVE-2025-22121, CVE-2025-23136, CVE-2025-23143, CVE-2025-37785, CVE-2025-37909, CVE-2025-37917, CVE-2025-37945, CVE-2025-37959, CVE-2025-37964, CVE-2025-37972, CVE-2025-37980, CVE-2025-38125, CVE-2025-38162, CVE-2025-38192, CVE-2025-38201, CVE-2025-38232, CVE-2025-38322, CVE-2025-38591, CVE-2025-38614, CVE-2025-38681, CVE-2025-38704, CVE-2025

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

d?id=CVE-2025-21856 Référence CVE CVE-2025-21857 https://www.cve.org/CVERecord?id=CVE-2025-21857 Référence CVE CVE-2025-21858 https://www.cve.org/CVERecord?id=CVE-2025-21858 Référence CVE CVE-2025-21859 https://www.cve.org/CVERecord?id=CVE-2025-21859 Référence CVE CVE-2025-21861 https://www.cve.org/CVERecord?id=CVE-2025-21861 Référence CVE CVE-2025-21862 https://www.cve.org/CVERecord?id=CVE-2025-21862 Référence CVE CVE-2025-21863 https://www.cve.org/CVERecord?id=CVE-2025-21863 Référence CVE CVE-2025-21864 https://www.cve.org/CVERecord?id=CVE-2025-21864 Référence CVE CVE-2025-21866 https://www.cve.org/CVERecord?id=CVE-2025-21866 Référence CVE CVE-2025-21867 https://www.cve.org/CVERecord?id=CVE-2025-21867 Référence CVE CVE-2025-21868 https://www.cve.org/CVERecord?id=CVE-2025-21868 Référence CVE CVE-2025-21869 https://www.cve.org/CVERecord?id=CVE-2025-21869 Référence CVE CVE-2025-21870 https://www.cve.org/CVERecord?id=CVE-2025-21870 Référence CVE CVE-2025-21871 https://www.cve.org/CVERecord?id=CVE-2025-21871 Référence CVE CVE-2025-21872 https://www.cve.org/CVERecord?id=CVE-2025-21872 Référence CVE CVE-2025-21873 https://www.cve.org/CVERecord?id=CVE-2025-21873 Référence CVE CVE-2025-21875 https://www.cve.org/CVERecord?id=CVE-2025-21875 Référence CVE CVE-2025-21877 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-21856 Référence CVE CVE-2025-21857 https://www.cve.org/CVERecord?id=CVE-2025-21857 Référence CVE CVE-2025-21858 https://www.cve.org/CVERecord?id=CVE-2025-21858 Référence CVE CVE-2025-21859 https://www.cve.org/CVERecord?id=CVE-2025-21859 Référence CVE CVE-2025-21861 https://www.cve.org/CVERecord?id=CVE-2025-21861 Référence CVE CVE-2025-21862 https://www.cve.org/CVERecord?id=CVE-2025-21862 Référence CVE CVE-2025-21863 https://www.cve.org/CVERecord?id=CVE-2025-21863 Référence CVE CVE-2025-21864 https://www.cve.org/CVERecord?id=CVE-2025-21864 Référence CVE CVE-2025-21866 https://www.cve.org/CVERecord?id=CVE-2025-21866 Référence CVE CVE-2025-21867 https://www.cve.org/CVERecord?id=CVE-2025-21867 Référence CVE CVE-2025-21868 https://www.cve.org/CVERecord?id=CVE-2025-21868 Référence CVE CVE-2025-21869 https://www.cve.org/CVERecord?id=CVE-2025-21869 Référence CVE CVE-2025-21870 https://www.cve.org/CVERecord?id=CVE-2025-21870 Référence CVE CVE-2025-21871 https://www.cve.org/CVERecord?id=CVE-2025-21871 Référence CVE CVE-2025-21887 https://www.cve.org/CVERecord?id=CVE-2025-21887 Référence CVE CVE-2025-22027 https://www.cve.org/CVERecord?id=CVE-2025-22027 Référence CVE CVE-2025-22062 https://www.cve.org/CVERecord?id=CVE-2025-22062 Référence CVE CVE-2025-23140 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2022-49385 Référence CVE CVE-2022-49788 https://www.cve.org/CVERecord?id=CVE-2022-49788 Référence CVE CVE-2022-49977 https://www.cve.org/CVERecord?id=CVE-2022-49977 Référence CVE CVE-2022-49991 https://www.cve.org/CVERecord?id=CVE-2022-49991 Référence CVE CVE-2022-50020 https://www.cve.org/CVERecord?id=CVE-2022-50020 Référence CVE CVE-2022-50022 https://www.cve.org/CVERecord?id=CVE-2022-50022 Référence CVE CVE-2022-50044 https://www.cve.org/CVERecord?id=CVE-2022-50044 Référence CVE CVE-2023-53047 https://www.cve.org/CVERecord?id=CVE-2023-53047 Référence CVE CVE-2024-57980 https://www.cve.org/CVERecord?id=CVE-2024-57980 Référence CVE CVE-2025-21867 https://www.cve.org/CVERecord?id=CVE-2025-21867 Référence CVE CVE-2025-21919 https://www.cve.org/CVERecord?id=CVE-2025-21919 Référence CVE CVE-2025-21928 https://www.cve.org/CVERecord?id=CVE-2025-21928 Référence CVE CVE-2025-22020 https://www.cve.org/CVERecord?id=CVE-2025-22020 Référence CVE CVE-2025-22026 https://www.cve.org/CVERecord?id=CVE-2025-22026 Référence CVE CVE-2025-22058 https://www.cve.org/CVERecord?id=CVE-2025-22058 Référence CVE CVE-2025-23150 https://www.cve.org/CVERecord?id=CVE-2025-23150 Référence CVE CVE-2025-37890 https://www.cve.org/CVERecord?id=CVE-2025-37890 Référence CVE CVE-2025-37914 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-21856 Référence CVE CVE-2025-21857 https://www.cve.org/CVERecord?id=CVE-2025-21857 Référence CVE CVE-2025-21858 https://www.cve.org/CVERecord?id=CVE-2025-21858 Référence CVE CVE-2025-21859 https://www.cve.org/CVERecord?id=CVE-2025-21859 Référence CVE CVE-2025-21861 https://www.cve.org/CVERecord?id=CVE-2025-21861 Référence CVE CVE-2025-21862 https://www.cve.org/CVERecord?id=CVE-2025-21862 Référence CVE CVE-2025-21863 https://www.cve.org/CVERecord?id=CVE-2025-21863 Référence CVE CVE-2025-21864 https://www.cve.org/CVERecord?id=CVE-2025-21864 Référence CVE CVE-2025-21866 https://www.cve.org/CVERecord?id=CVE-2025-21866 Référence CVE CVE-2025-21867 https://www.cve.org/CVERecord?id=CVE-2025-21867 Référence CVE CVE-2025-21868 https://www.cve.org/CVERecord?id=CVE-2025-21868 Référence CVE CVE-2025-21869 https://www.cve.org/CVERecord?id=CVE-2025-21869 Référence CVE CVE-2025-21870 https://www.cve.org/CVERecord?id=CVE-2025-21870 Référence CVE CVE-2025-21871 https://www.cve.org/CVERecord?id=CVE-2025-21871 Référence CVE CVE-2025-22027 https://www.cve.org/CVERecord?id=CVE-2025-22027 Référence CVE CVE-2025-22062 https://www.cve.org/CVERecord?id=CVE-2025-22062 Référence CVE CVE-2025-23140 https://www.cve.org/CVERecord?id=CVE-2025-23140 Référence CVE CVE-2025-23142 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2021-47670 Référence CVE CVE-2022-49788 https://www.cve.org/CVERecord?id=CVE-2022-49788 Référence CVE CVE-2022-50020 https://www.cve.org/CVERecord?id=CVE-2022-50020 Référence CVE CVE-2022-50022 https://www.cve.org/CVERecord?id=CVE-2022-50022 Référence CVE CVE-2022-50200 https://www.cve.org/CVERecord?id=CVE-2022-50200 Référence CVE CVE-2023-53047 https://www.cve.org/CVERecord?id=CVE-2023-53047 Référence CVE CVE-2024-28956 https://www.cve.org/CVERecord?id=CVE-2024-28956 Référence CVE CVE-2024-57980 https://www.cve.org/CVERecord?id=CVE-2024-57980 Référence CVE CVE-2025-21727 https://www.cve.org/CVERecord?id=CVE-2025-21727 Référence CVE CVE-2025-21867 https://www.cve.org/CVERecord?id=CVE-2025-21867 Référence CVE CVE-2025-21928 https://www.cve.org/CVERecord?id=CVE-2025-21928 Référence CVE CVE-2025-21991 https://www.cve.org/CVERecord?id=CVE-2025-21991 Référence CVE CVE-2025-22020 https://www.cve.org/CVERecord?id=CVE-2025-22020 Référence CVE CVE-2025-22026 https://www.cve.org/CVERecord?id=CVE-2025-22026 Référence CVE CVE-2025-22097 https://www.cve.org/CVERecord?id=CVE-2025-22097 Référence CVE CVE-2025-37797 https://www.cve.org/CVERecord?id=CVE-2025-37797 Référence CVE CVE-2025-37914 https://www.cve.org/CVERecord?id=CVE-2025-37914 Référence CVE CVE-2025-38084 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-21856 Référence CVE CVE-2025-21857 https://www.cve.org/CVERecord?id=CVE-2025-21857 Référence CVE CVE-2025-21858 https://www.cve.org/CVERecord?id=CVE-2025-21858 Référence CVE CVE-2025-21859 https://www.cve.org/CVERecord?id=CVE-2025-21859 Référence CVE CVE-2025-21861 https://www.cve.org/CVERecord?id=CVE-2025-21861 Référence CVE CVE-2025-21862 https://www.cve.org/CVERecord?id=CVE-2025-21862 Référence CVE CVE-2025-21863 https://www.cve.org/CVERecord?id=CVE-2025-21863 Référence CVE CVE-2025-21864 https://www.cve.org/CVERecord?id=CVE-2025-21864 Référence CVE CVE-2025-21866 https://www.cve.org/CVERecord?id=CVE-2025-21866 Référence CVE CVE-2025-21867 https://www.cve.org/CVERecord?id=CVE-2025-21867 Référence CVE CVE-2025-21868 https://www.cve.org/CVERecord?id=CVE-2025-21868 Référence CVE CVE-2025-21869 https://www.cve.org/CVERecord?id=CVE-2025-21869 Référence CVE CVE-2025-21870 https://www.cve.org/CVERecord?id=CVE-2025-21870 Référence CVE CVE-2025-21871 https://www.cve.org/CVERecord?id=CVE-2025-21871 Référence CVE CVE-2025-37797 https://www.cve.org/CVERecord?id=CVE-2025-37797 Référence CVE CVE-2025-37947 https://www.cve.org/CVERecord?id=CVE-2025-37947 Référence CVE CVE-2025-37948 https://www.cve.org/CVERecord?id=CVE-2025-37948 Référence CVE CVE-2025-37949 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-21857 Référence CVE CVE-2025-21858 https://www.cve.org/CVERecord?id=CVE-2025-21858 Référence CVE CVE-2025-21859 https://www.cve.org/CVERecord?id=CVE-2025-21859 Référence CVE CVE-2025-21861 https://www.cve.org/CVERecord?id=CVE-2025-21861 Référence CVE CVE-2025-21862 https://www.cve.org/CVERecord?id=CVE-2025-21862 Référence CVE CVE-2025-21863 https://www.cve.org/CVERecord?id=CVE-2025-21863 Référence CVE CVE-2025-21864 https://www.cve.org/CVERecord?id=CVE-2025-21864 Référence CVE CVE-2025-21865 https://www.cve.org/CVERecord?id=CVE-2025-21865 Référence CVE CVE-2025-21866 https://www.cve.org/CVERecord?id=CVE-2025-21866 Référence CVE CVE-2025-21867 https://www.cve.org/CVERecord?id=CVE-2025-21867 Référence CVE CVE-2025-21868 https://www.cve.org/CVERecord?id=CVE-2025-21868 Référence CVE CVE-2025-21869 https://www.cve.org/CVERecord?id=CVE-2025-21869 Référence CVE CVE-2025-21870 https://www.cve.org/CVERecord?id=CVE-2025-21870 Référence CVE CVE-2025-21871 https://www.cve.org/CVERecord?id=CVE-2025-21871 Référence CVE CVE-2025-21873 https://www.cve.org/CVERecord?id=CVE-2025-21873 Référence CVE CVE-2025-21875 https://www.cve.org/CVERecord?id=CVE-2025-21875 Référence CVE CVE-2025-21876 https://www.cve.org/CVERecord?id=CVE-2025-21876 Référence CVE CVE-2025-21877 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-21857 Référence CVE CVE-2025-21858 https://www.cve.org/CVERecord?id=CVE-2025-21858 Référence CVE CVE-2025-21859 https://www.cve.org/CVERecord?id=CVE-2025-21859 Référence CVE CVE-2025-21861 https://www.cve.org/CVERecord?id=CVE-2025-21861 Référence CVE CVE-2025-21862 https://www.cve.org/CVERecord?id=CVE-2025-21862 Référence CVE CVE-2025-21863 https://www.cve.org/CVERecord?id=CVE-2025-21863 Référence CVE CVE-2025-21864 https://www.cve.org/CVERecord?id=CVE-2025-21864 Référence CVE CVE-2025-21865 https://www.cve.org/CVERecord?id=CVE-2025-21865 Référence CVE CVE-2025-21866 https://www.cve.org/CVERecord?id=CVE-2025-21866 Référence CVE CVE-2025-21867 https://www.cve.org/CVERecord?id=CVE-2025-21867 Référence CVE CVE-2025-21869 https://www.cve.org/CVERecord?id=CVE-2025-21869 Référence CVE CVE-2025-21870 https://www.cve.org/CVERecord?id=CVE-2025-21870 Référence CVE CVE-2025-21871 https://www.cve.org/CVERecord?id=CVE-2025-21871 Référence CVE CVE-2025-21873 https://www.cve.org/CVERecord?id=CVE-2025-21873 Référence CVE CVE-2025-21875 https://www.cve.org/CVERecord?id=CVE-2025-21875 Référence CVE CVE-2025-21876 https://www.cve.org/CVERecord?id=CVE-2025-21876 Référence CVE CVE-2025-21877 https://www.cve.org/CVERecord?id=CVE-2025-21877 Référence CVE CVE-2025-21878 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-21758 Référence CVE CVE-2025-21768 https://www.cve.org/CVERecord?id=CVE-2025-21768 Référence CVE CVE-2025-21792 https://www.cve.org/CVERecord?id=CVE-2025-21792 Référence CVE CVE-2025-21808 https://www.cve.org/CVERecord?id=CVE-2025-21808 Référence CVE CVE-2025-21812 https://www.cve.org/CVERecord?id=CVE-2025-21812 Référence CVE CVE-2025-21833 https://www.cve.org/CVERecord?id=CVE-2025-21833 Référence CVE CVE-2025-21852 https://www.cve.org/CVERecord?id=CVE-2025-21852 Référence CVE CVE-2025-21853 https://www.cve.org/CVERecord?id=CVE-2025-21853 Référence CVE CVE-2025-21854 https://www.cve.org/CVERecord?id=CVE-2025-21854 Référence CVE CVE-2025-21867 https://www.cve.org/CVERecord?id=CVE-2025-21867 Référence CVE CVE-2025-21904 https://www.cve.org/CVERecord?id=CVE-2025-21904 Référence CVE CVE-2025-21925 https://www.cve.org/CVERecord?id=CVE-2025-21925 Référence CVE CVE-2025-21926 https://www.cve.org/CVERecord?id=CVE-2025-21926 Référence CVE CVE-2025-21931 https://www.cve.org/CVERecord?id=CVE-2025-21931 Référence CVE CVE-2025-21962 https://www.cve.org/CVERecord?id=CVE-2025-21962 Référence CVE CVE-2025-21963 https://www.cve.org/CVERecord?id=CVE-2025-21963 Référence CVE CVE-2025-21964 https://www.cve.org/CVERecord?id=CVE-2025-21964 Référence CVE CVE-2025-21980 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-21806 Référence CVE CVE-2025-21808 https://www.cve.org/CVERecord?id=CVE-2025-21808 Référence CVE CVE-2025-21812 https://www.cve.org/CVERecord?id=CVE-2025-21812 Référence CVE CVE-2025-21833 https://www.cve.org/CVERecord?id=CVE-2025-21833 Référence CVE CVE-2025-21836 https://www.cve.org/CVERecord?id=CVE-2025-21836 Référence CVE CVE-2025-21852 https://www.cve.org/CVERecord?id=CVE-2025-21852 Référence CVE CVE-2025-21853 https://www.cve.org/CVERecord?id=CVE-2025-21853 Référence CVE CVE-2025-21854 https://www.cve.org/CVERecord?id=CVE-2025-21854 Référence CVE CVE-2025-21863 https://www.cve.org/CVERecord?id=CVE-2025-21863 Référence CVE CVE-2025-21867 https://www.cve.org/CVERecord?id=CVE-2025-21867 Référence CVE CVE-2025-21873 https://www.cve.org/CVERecord?id=CVE-2025-21873 Référence CVE CVE-2025-21875 https://www.cve.org/CVERecord?id=CVE-2025-21875 Référence CVE CVE-2025-21881 https://www.cve.org/CVERecord?id=CVE-2025-21881 Référence CVE CVE-2025-21884 https://www.cve.org/CVERecord?id=CVE-2025-21884 Référence CVE CVE-2025-21887 https://www.cve.org/CVERecord?id=CVE-2025-21887 Référence CVE CVE-2025-21889 https://www.cve.org/CVERecord?id=CVE-2025-21889 Référence CVE CVE-2025-21894 https://www.cve.org/CVERecord?id=CVE-2025-21894 Référence CVE CVE-2025-21895 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-21848 Référence CVE CVE-2025-21853 https://www.cve.org/CVERecord?id=CVE-2025-21853 Référence CVE CVE-2025-21855 https://www.cve.org/CVERecord?id=CVE-2025-21855 Référence CVE CVE-2025-21858 https://www.cve.org/CVERecord?id=CVE-2025-21858 Référence CVE CVE-2025-21859 https://www.cve.org/CVERecord?id=CVE-2025-21859 Référence CVE CVE-2025-21862 https://www.cve.org/CVERecord?id=CVE-2025-21862 Référence CVE CVE-2025-21864 https://www.cve.org/CVERecord?id=CVE-2025-21864 Référence CVE CVE-2025-21865 https://www.cve.org/CVERecord?id=CVE-2025-21865 Référence CVE CVE-2025-21866 https://www.cve.org/CVERecord?id=CVE-2025-21866 Référence CVE CVE-2025-21867 https://www.cve.org/CVERecord?id=CVE-2025-21867 Référence CVE CVE-2025-21871 https://www.cve.org/CVERecord?id=CVE-2025-21871 Référence CVE CVE-2025-21872 https://www.cve.org/CVERecord?id=CVE-2025-21872 Référence CVE CVE-2025-21875 https://www.cve.org/CVERecord?id=CVE-2025-21875 Référence CVE CVE-2025-21877 https://www.cve.org/CVERecord?id=CVE-2025-21877 Référence CVE CVE-2025-21878 https://www.cve.org/CVERecord?id=CVE-2025-21878 Référence CVE CVE-2025-21881 https://www.cve.org/CVERecord?id=CVE-2025-21881 Référence CVE CVE-2025-21887 https://www.cve.org/CVERecord?id=CVE-2025-21887 Référence CVE CVE-2025-21891 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-21812 Référence CVE CVE-2025-21833 https://www.cve.org/CVERecord?id=CVE-2025-21833 Référence CVE CVE-2025-21836 https://www.cve.org/CVERecord?id=CVE-2025-21836 Référence CVE CVE-2025-21839 https://www.cve.org/CVERecord?id=CVE-2025-21839 Référence CVE CVE-2025-21852 https://www.cve.org/CVERecord?id=CVE-2025-21852 Référence CVE CVE-2025-21853 https://www.cve.org/CVERecord?id=CVE-2025-21853 Référence CVE CVE-2025-21854 https://www.cve.org/CVERecord?id=CVE-2025-21854 Référence CVE CVE-2025-21862 https://www.cve.org/CVERecord?id=CVE-2025-21862 Référence CVE CVE-2025-21863 https://www.cve.org/CVERecord?id=CVE-2025-21863 Référence CVE CVE-2025-21867 https://www.cve.org/CVERecord?id=CVE-2025-21867 Référence CVE CVE-2025-21873 https://www.cve.org/CVERecord?id=CVE-2025-21873 Référence CVE CVE-2025-21875 https://www.cve.org/CVERecord?id=CVE-2025-21875 Référence CVE CVE-2025-21881 https://www.cve.org/CVERecord?id=CVE-2025-21881 Référence CVE CVE-2025-21884 https://www.cve.org/CVERecord?id=CVE-2025-21884 Référence CVE CVE-2025-21886 https://www.cve.org/CVERecord?id=CVE-2025-21886 Référence CVE CVE-2025-21887 https://www.cve.org/CVERecord?id=CVE-2025-21887 Référence CVE CVE-2025-21889 https://www.cve.org/CVERecord?id=CVE-2025-21889 Référence CVE CVE-2025-21894 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-21846 Référence CVE CVE-2025-21848 https://www.cve.org/CVERecord?id=CVE-2025-21848 Référence CVE CVE-2025-21855 https://www.cve.org/CVERecord?id=CVE-2025-21855 Référence CVE CVE-2025-21858 https://www.cve.org/CVERecord?id=CVE-2025-21858 Référence CVE CVE-2025-21859 https://www.cve.org/CVERecord?id=CVE-2025-21859 Référence CVE CVE-2025-21862 https://www.cve.org/CVERecord?id=CVE-2025-21862 Référence CVE CVE-2025-21864 https://www.cve.org/CVERecord?id=CVE-2025-21864 Référence CVE CVE-2025-21865 https://www.cve.org/CVERecord?id=CVE-2025-21865 Référence CVE CVE-2025-21866 https://www.cve.org/CVERecord?id=CVE-2025-21866 Référence CVE CVE-2025-21867 https://www.cve.org/CVERecord?id=CVE-2025-21867 Référence CVE CVE-2025-21871 https://www.cve.org/CVERecord?id=CVE-2025-21871 Référence CVE CVE-2025-21875 https://www.cve.org/CVERecord?id=CVE-2025-21875 Référence CVE CVE-2025-21877 https://www.cve.org/CVERecord?id=CVE-2025-21877 Référence CVE CVE-2025-21878 https://www.cve.org/CVERecord?id=CVE-2025-21878 Référence CVE CVE-2025-21881 https://www.cve.org/CVERecord?id=CVE-2025-21881 Référence CVE CVE-2025-21887 https://www.cve.org/CVERecord?id=CVE-2025-21887 Référence CVE CVE-2025-21891 https://www.cve.org/CVERecord?id=CVE-2025-21891 Référence CVE CVE-2025-21898 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2025-002992Linux の Linux Kernel における解放済みメモリの使用に関する脆弱性

Linux の Linux Kernel には、解放済みメモリの使用に関する脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Linux: < 5.18, 6.1.130 ≤ 6.1.*, 6.6.80 ≤ 6.6.*, 6.12.17 ≤ 6.12.*, 6.13.5 ≤ 6.13.*, 6.14 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
04

Evidence and provenance

Published 27 Mar 2025 · Last source change 8 Sept 2026, 08:40 UTC · CWE-416 · Use After Free

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2025-8435
Product sourceVendor CSAF · Siemens ProductCERT
Remediation sourceVendor CSAF · Siemens ProductCERT
CWE sourceCISA ADP
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 ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    be3d72a2896cb24090f268dce4aa8a304d40bc23 < f615fccfc689cb48977d275ac2e391297b52392b; be3d72a2896cb24090f268dce4aa8a304d40bc23 < d56d8a23d95100b65f40438639dd82db2af81c11; be3d72a2896cb24090f268dce4aa8a304d40bc23 < 972bafed67ca73ad9a56448384281eb5fd5c0ba3; be3d72a2896cb24090f268dce4aa8a304d40bc23 < 1a9e1284e87d59b1303b69d1808d310821d6e5f7; be3d72a2896cb24090f268dce4aa8a304d40bc23 < 6b3d638ca897e099fa99bd6d02189d3176f80a47; 5.18 · Fixed: < 5.18; 6.1.130 ≤ 6.1.*; 6.6.80 ≤ 6.6.*; 6.12.17 ≤ 6.12.*; 6.13.5 ≤ 6.13.*; 6.14 ≤ *
    After
    Linux: be3d72a2896cb24090f268dce4aa8a304d40bc23 < f615fccfc689cb48977d275ac2e391297b52392b, be3d72a2896cb24090f268dce4aa8a304d40bc23 < d56d8a23d95100b65f40438639dd82db2af81c11, be3d72a2896cb24090f268dce4aa8a304d40bc23 < 972bafed67ca73ad9a56448384281eb5fd5c0ba3, be3d72a2896cb24090f268dce4aa8a304d40bc23 < 1a9e1284e87d59b1303b69d1808d310821d6e5f7, be3d72a2896cb24090f268dce4aa8a304d40bc23 < 6b3d638ca897e099fa99bd6d02189d3176f80a47, 5.18 · Fixed: Linux: < 5.18, 6.1.130 ≤ 6.1.*, 6.6.80 ≤ 6.6.*, 6.12.17 ≤ 6.12.*, 6.13.5 ≤ 6.13.*, 6.14 ≤ *
    CNA ↗
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-21867 · cve.blacktree.nl