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

llc: do not use skb_get() before dev_queue_xmit()

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. 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 severityMediumOperational priority:Low, 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.22% 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: No default targetRemediation target: Normal maintenance

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.19-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.133-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.19-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.19-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-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.

2 current
CVE-2025-21925 · CSAF 2.0 · revision 45 · interimSUSE Product Security TeamCVE-2025-21925
229 known affected

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

  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP7
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
Summary
In the Linux kernel, the following vulnerability has been resolved: llc: do not use skb_get() before dev_queue_xmit() syzbot is able to crash hosts [1], using llc and devices not supporting IFF_TX_SKB_SHARING. In this case, e1000 driver calls eth_skb_pad(), while the skb is shared. Simply replace skb_get() by skb_clone() in net/llc/llc_s_ac.c Note that e1000 driver might have an issue with pktgen, because it does not clear IFF_TX_SKB_SHARING, this is an orthogonal change. We need to audit other skb_get() uses in net/llc. [1] kernel BUG at net/core/skbuff.c:2178 ! Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN NOPTI CPU: 0 UID: 0 PID: 16371 Comm: syz.2.2764 Not tainted 6.14.0-rc4-syzkaller-00052-gac9c34d1e45a #0 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014 RIP: 0010:pskb_expand_head+0x6ce/0x1240 net/core/skbuff.c:2178 Call Trace: __skb_pad+0x18a/0x610 net/core/skbuff.c:2466 __skb_put_padto include/linux/skbuff.h:3843 [inline] skb_put_padto include/linux/skbuff.h:3862 [inline] eth_skb_pad include/linux/etherdevice.h:656 [inline] e1000_xmit_frame+0x2d99/0x5800 drivers/net/ethernet/intel/e1000/e1000_main.c:3128 __netdev_start_xmit include/linux/netdevice.h:5151 [inline] netdev_start_xmit include/linux/netdevice.h:5160 [inline] xmit_one net/core/dev.c:3806 [inline] dev_hard_start_xmit+0x9a/0x7b0 net/core/dev.c:3822 sch_direct_xmit+0x1ae/0xc30 net/sched/sch_generic.c:343 __dev_xmit_skb net/core/dev.c:4045 [inline] __dev_queue_xmit+0x13d4/0x43e0 net/core/dev.c:4621 dev_queue_xmit include/linux/netdevice.h:3313 [inline] llc_sap_action_send_test_c+0x268/0x320 net/llc/llc_s_ac.c:144 llc_exec_sap_trans_actions net/llc/llc_sap.c:153 [inline] llc_sap_next_state net/llc/llc_sap.c:182 [inline] llc_sap_state_process+0x239/0x510 net/llc/llc_sap.c:209 llc_ui_sendmsg+0xd0d/0x14e0 net/llc/af_llc.c:993 sock_sendmsg_nosec net/socket.c:718 [inline]
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
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: llc: do not use skb_get() before dev_queue_xmit() syzbot is able to crash hosts [1], using llc and devices not supporting IFF_TX_SKB_SHARING. In this case, e1000 driver calls eth_skb_pad(), while the skb is shared. Simply replace skb_get() by skb_clone() in net/llc/llc_s_ac.c Note that e1000 driver might have an issue with pktgen, because it does not clear IFF_TX_SKB_SHARING, this is an orthogonal change. We need to audit other skb_get() uses in net/llc. [1] kernel BUG at net/core/skbuff.c:2178 ! Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN NOPTI CPU: 0 UID: 0 PID: 16371 Comm: syz.2.2764 Not tainted 6.14.0-rc4-syzkaller-00052-gac9c34d1e45a #0 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014 RIP: 0010:pskb_expand_head+0x6ce/0x1240 net/core/skbuff.c:2178 Call Trace: __skb_pad+0x18a/0x610 net/core/skbuff.c:2466 __skb_put_padto include/linux/skbuff.h:3843 [inline] skb_put_padto include/linux/skbuff.h:3862 [inline] eth_skb_pad include/linux/etherdevice.h:656 [inline] e1000_xmit_frame+0x2d99/0x5800 drivers/net/ethernet/intel/e1000/e1000_main.c:3128 __netdev_start_xmit include/linux/netdevice.h:5151 [inline] netdev_start_xmit include/linux/netdevice.h:5160 [inline] xmit_one net/core/dev.c:3806 [inline] dev_hard_start_xmit+0x9a/0x7b0 net/core/dev.c:3822 sch_direct_xmit+0x1ae/0xc30 net/sched/sch_generic.c:343 __dev_xmit_skb net/core/dev.c:4045 [inline] __dev_queue_xmit+0x13d4/0x43e0 net/core/dev.c:4621 dev_queue_xmit include/linux/netdevice.h:3313 [inline] llc_sap_action_send_test_c+0x268/0x320 net/llc/llc_s_ac.c:144 llc_exec_sap_trans_actions net/llc/llc_sap.c:153 [inline] llc_sap_next_state net/llc/llc_sap.c:182 [inline] llc_sap_state_process+0x239/0x510 net/llc/llc_sap.c:209 llc_ui_sendmsg+0xd0d/0x14e0 net/llc/af_llc.c:993 sock_sendmsg_nosec net/socket.c:718 [inline]
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-9396

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: llc: do not use skb_get() before dev_queue_xmit() syzbot is able to crash hosts [1], using llc and devices not supporting IFF_TX_SKB_SHARING. In this case, e1000 driver calls eth_skb_pad(), while the skb is shared. Simply replace skb_get() by skb_clone() in net/llc/llc_s_ac.c Note that e1000 driver might have an issue with pktgen, because it does not clear IFF_TX_SKB_SHARING, this is an orthogonal change. We need to audit other skb_get() uses in net/llc. [1] kernel BUG at net/core/skbuff.c:2178 ! Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN NOPTI CPU: 0 UID: 0 PID: 16371 Comm: syz.2.2764 Not tainted 6.14.0-rc4-syzkaller-00052-gac9c34d1e45a #0 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014 RIP: 0010:pskb_expand_head+0x6ce/0x1240 net/core/skbuff.c:2178 Call Trace: <TASK> __skb_pad+0x18a/0x610 net/core/skbuff.c:2466 __skb_put_padto include/linux/skbuff.h:3843 [inline] skb_put_padto include/linux/skbuff.h:3862 [inline] eth_skb_pad include/linux/etherdevice.h:656 [inline] e1000_xmit_frame+0x2d99/0x5800 drivers/net/ethernet/intel/e1000/e1000_main.c:3128 __netdev_start_xmit include/linux/netdevice.h:5151 [inline] netdev_start_xmit include/linux/netdevice.h:5160 [inline] xmit_one net/core/dev.c:3806 [inline] dev_hard_start_xmit+0x9a/0x7b0 net/core/dev.c:3822 sch_direct_xmit+0x1ae/0xc30 net/sched/sch_generic.c:343 __dev_xmit_skb net/core/dev.c:4045 [inline] __dev_queue_xmit+0x13d4/0x43e0 net/core/dev.c:4621 dev_queue_xmit include/linux/netdevice.h:3313 [inline] llc_sap_action_send_test_c+0x268/0x320 net/llc/llc_s_ac.c:144 llc_exec_sap_trans_actions net/llc/llc_sap.c:153 [inline] llc_sap_next_state net/llc/llc_sap.c:182 [inline] llc_sap_state_process+0x239/0x510 net/llc/llc_sap.c:209 llc_ui_sendmsg+0xd0d/0x14e0 net/llc/af_llc.c:993 sock_sendmsg_nosec net/socket.c:718 [inline]

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

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. 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: llc: do not use skb_get() before dev_queue_xmit() syzbot is able to crash hosts [1], using llc and devices not supporting IFF_TX_SKB_SHARING. In this case, e1000 driver calls eth_skb_pad(), while the skb is shared. Simply replace skb_get() by skb_clone() in net/llc/llc_s_ac.c Note that e1000 driver might have an issue with pktgen, because it does not clear IFF_TX_SKB_SHARING, this is an orthogonal change. We need to audit other skb_get() uses in net/llc. [1] kernel BUG at net/core/skbuff.c:2178 ! Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN NOPTI CPU: 0 UID: 0 PID: 16371 Comm: syz.2.2764 Not tainted 6.14.0-rc4-syzkaller-00052-gac9c34d1e45a #0 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014 RIP: 0010:pskb_expand_head+0x6ce/0x1240 net/core/skbuff.c:2178 Call Trace: <TASK> __skb_pad+0x18a/0x610 net/core/skbuff.c:2466 __skb_put_padto include/linux/skbuff.h:3843 [inline] skb_put_padto include/linux/skbuff.h:3862 [inline] eth_skb_pad include/linux/etherdevice.h:656 [inline] e1000_xmit_frame+0x2d99/0x5800 drivers/net/ethernet/intel/e1000/e1000_main.c:3128 __netdev_start_xmit include/linux/netdevice.h:5151 [inline] netdev_start_xmit include/linux/netdevice.h:5160 [inline] xmit_one net/core/dev.c:3806 [inline] dev_hard_start_xmit+0x9a/0x7b0 net/core/dev.c:3822 sch_direct_xmit+0x1ae/0xc30 net/sched/sch_generic.c:343 __dev_xmit_skb net/core/dev.c:4045 [inline] __dev_queue_xmit+0x13d4/0x43e0 net/core/dev.c:4621 dev_queue_xmit include/linux/netdevice.h:3313 [inline] llc_sap_action_send_test_c+0x268/0x320 net/llc/llc_s_ac.c:144 llc_exec_sap_trans_actions net/llc/llc_sap.c:153 [inline] llc_sap_next_state net/llc/llc_sap.c:182 [inline] llc_sap_state_process+0x239/0x510 net/llc/llc_sap.c:209 llc_ui_sendmsg+0xd0d/0x14e0 net/llc/af_llc.c:993 sock_sendmsg_nosec net/socket.c:718 [inline]

What

In the Linux kernel, the following vulnerability has been resolved: llc: do not use skb_get() before dev_queue_xmit() syzbot is able to crash hosts [1], using llc and devices not supporting IFF_TX_SKB_SHARING. In this case, e1000 driver calls eth_skb_pad(), while the skb is shared. Simply replace skb_get() by skb_clone() in net/llc/llc_s_ac.c Note that e1000 driver might have an issue with pktgen, because it does not clear IFF_TX_SKB_SHARING, this is an orthogonal change. We need to audit other skb_get() uses in net/llc. [1] kernel BUG at net/core/skbuff.c:2178 ! Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN NOPTI CPU: 0 UID: 0 PID: 16371 Comm: syz.2.2764 Not tainted 6.14.0-rc4-syzkaller-00052-gac9c34d1e45a #0 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014 RIP: 0010:pskb_expand_head+0x6ce/0x1240 net/core/skbuff.c:2178 Call Trace: <TASK> __skb_pad+0x18a/0x610 net/core/skbuff.c:2466 __skb_put_padto include/linux/skbuff.h:3843 [inline] skb_put_padto include/linux/skbuff.h:3862 [inline] eth_skb_pad include/linux/etherdevice.h:656 [inline] e1000_xmit_frame+0x2d99/0x5800 drivers/net/ethernet/intel/e1000/e1000_main.c:3128 __netdev_start_xmit include/linux/netdevice.h:5151 [inline] netdev_start_xmit include/linux/netdevice.h:5160 [inline] xmit_one net/core/dev.c:3806 [inline] dev_hard_start_xmit+0x9a/0x7b0 net/core/dev.c:3822 sch_direct_xmit+0x1ae/0xc30 net/sched/sch_generic.c:343 __dev_xmit_skb net/core/dev.c:4045 [inline] __dev_queue_xmit+0x13d4/0x43e0 net/core/dev.c:4621 dev_queue_xmit include/linux/netdevice.h:3313 [inline] llc_sap_action_send_test_c+0x268/0x320 net/llc/llc_s_ac.c:144 llc_exec_sap_trans_actions net/llc/llc_sap.c:153 [inline] llc_sap_next_state net/llc/llc_sap.c:182 [inline] llc_sap_state_process+0x239/0x510 net/llc/llc_sap.c:209 llc_ui_sendmsg+0xd0d/0x14e0 net/llc/af_llc.c:993 sock_sendmsg_nosec net/socket.c:718 [inline]

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may disrupt the affected service.

What

In the Linux kernel, the following vulnerability has been resolved: llc: do not use skb_get() before dev_queue_xmit() syzbot is able to crash hosts [1], using llc and devices not supporting IFF_TX_SKB_SHARING. In this case, e1000 driver calls eth_skb_pad(), while the skb is shared. Simply replace skb_get() by skb_clone() in net/llc/llc_s_ac.c Note that e1000 driver might have an issue with pktgen, because it does not clear IFF_TX_SKB_SHARING, this is an orthogonal change. We need to audit other skb_get() uses in net/llc. [1] kernel BUG at net/core/skbuff.c:2178 ! Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN NOPTI CPU: 0 UID: 0 PID: 16371 Comm: syz.2.2764 Not tainted 6.14.0-rc4-syzkaller-00052-gac9c34d1e45a #0 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014 RIP: 0010:pskb_expand_head+0x6ce/0x1240 net/core/skbuff.c:2178 Call Trace: <TASK> __skb_pad+0x18a/0x610 net/core/skbuff.c:2466 __skb_put_padto include/linux/skbuff.h:3843 [inline] skb_put_padto include/linux/skbuff.h:3862 [inline] eth_skb_pad include/linux/etherdevice.h:656 [inline] e1000_xmit_frame+0x2d99/0x5800 drivers/net/ethernet/intel/e1000/e1000_main.c:3128 __netdev_start_xmit include/linux/netdevice.h:5151 [inline] netdev_start_xmit include/linux/netdevice.h:5160 [inline] xmit_one net/core/dev.c:3806 [inline] dev_hard_start_xmit+0x9a/0x7b0 net/core/dev.c:3822 sch_direct_xmit+0x1ae/0xc30 net/sched/sch_generic.c:343 __dev_xmit_skb net/core/dev.c:4045 [inline] __dev_queue_xmit+0x13d4/0x43e0 net/core/dev.c:4621 dev_queue_xmit include/linux/netdevice.h:3313 [inline] llc_sap_action_send_test_c+0x268/0x320 net/llc/llc_s_ac.c:144 llc_exec_sap_trans_actions net/llc/llc_sap.c:153 [inline] llc_sap_next_state net/llc/llc_sap.c:182 [inline] llc_sap_state_process+0x239/0x510 net/llc/llc_sap.c:209 llc_ui_sendmsg+0xd0d/0x14e0 net/llc/af_llc.c:993 sock_sendmsg_nosec net/socket.c:718 [inline]

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may disrupt the affected service.

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 → vulnerable operation → disrupt the affected service
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.
CWE not yet assigned
CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

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

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

Official authority intelligence

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

ENISA EUVD · EUVD-2025-9396Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: llc: do not use skb_get() before dev_queue_xmit() syzbot is able to crash hosts [1], using llc and devices not supporting IFF_TX_SKB_SHARING. In this case, e1000 driver calls eth_skb_pad(), while the skb is shared. Simply replace skb_get() by skb_clone() in net/llc/llc_s_ac.c Note that e1000 driver might have an issue with pktgen, because it does not clear IFF_TX_SKB_SHARING, this is an orthogonal change. We need to audit other skb_get() uses in net/llc. [1] kernel BUG at net/core/skbuff.c:2178 ! Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN NOPTI CPU: 0 UID: 0 PID: 16371 Comm: syz.2.2764 Not tainted 6.14.0-rc4-syzkaller-00052-gac9c34d1e45a #0 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014 RIP: 0010:pskb_expand_head+0x6ce/0x1240 net/core/skbuff.c:2178 Call Trace: <TASK> __skb_pad+0x18a/0x610 net/core/skbuff.c:2466 __skb_put_padto include/linux/skbuff.h:3843 [inline] skb_put_padto include/linux/skbuff.h:3862 [inline] eth_skb_pad include/linux/etherdevice.h:656 [inline] e1000_xmit_frame+0x2d99/0x5800 drivers/net/ethernet/intel/e1000/e1000_main.c:3128 __netdev_start_xmit include/linux/netdevice.h:5151 [inline] netdev_start_xmit include/linux/netdevice.h:5160 [inline] xmit_one net/core/dev.c:3806 [inline] dev_hard_start_xmit+0x9a/0x7b0 net/core/dev.c:3822 sch_direct_xmit+0x1ae/0xc30 net/sched/sch_generic.c:343 __dev_xmit_skb net/core/dev.c:4045 [inline] __dev_queue_xmit+0x13d4/0x43e0 net/core/dev.c:4621 dev_queue_xmit include/linux/netdevice.h:3313 [inline] llc_sap_action_send_test_c+0x268/0x320 net/llc/llc_s_ac.c:144 llc_exec_sap_trans_actions net/llc/llc_sap.c:153 [inline] llc_sap_next_state net/llc/llc_sap.c:182 [inline] llc_sap_state_process+0x239/0x510 net/llc/llc_sap.c:209 llc_ui_sendmsg+0xd0d/0x14e0 net/llc/af_llc.c:993 sock_sendmsg_nosec net/socket.c:718 [inline]

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

Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial-of-Service auszulösen und um nicht näher spezifizierte Auswirkungen 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-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-38721, CVE-2025-38725, CVE-2025-38727, CVE-2025-38732, CVE-2025-38736, CVE-2025

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

d?id=CVE-2025-21914 Référence CVE CVE-2025-21915 https://www.cve.org/CVERecord?id=CVE-2025-21915 Référence CVE CVE-2025-21916 https://www.cve.org/CVERecord?id=CVE-2025-21916 Référence CVE CVE-2025-21917 https://www.cve.org/CVERecord?id=CVE-2025-21917 Référence CVE CVE-2025-21918 https://www.cve.org/CVERecord?id=CVE-2025-21918 Référence CVE CVE-2025-21919 https://www.cve.org/CVERecord?id=CVE-2025-21919 Référence CVE CVE-2025-21920 https://www.cve.org/CVERecord?id=CVE-2025-21920 Référence CVE CVE-2025-21922 https://www.cve.org/CVERecord?id=CVE-2025-21922 Référence CVE CVE-2025-21924 https://www.cve.org/CVERecord?id=CVE-2025-21924 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-21927 https://www.cve.org/CVERecord?id=CVE-2025-21927 Référence CVE CVE-2025-21928 https://www.cve.org/CVERecord?id=CVE-2025-21928 Référence CVE CVE-2025-21929 https://www.cve.org/CVERecord?id=CVE-2025-21929 Référence CVE CVE-2025-21930 https://www.cve.org/CVERecord?id=CVE-2025-21930 Référence CVE CVE-2025-21934 https://www.cve.org/CVERecord?id=CVE-2025-21934 Référence CVE CVE-2025-21935 https://www.cve.org/CVERecord?id=CVE-2025-21935 Référence CVE CVE-2025-21936 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-21914 Référence CVE CVE-2025-21915 https://www.cve.org/CVERecord?id=CVE-2025-21915 Référence CVE CVE-2025-21916 https://www.cve.org/CVERecord?id=CVE-2025-21916 Référence CVE CVE-2025-21917 https://www.cve.org/CVERecord?id=CVE-2025-21917 Référence CVE CVE-2025-21918 https://www.cve.org/CVERecord?id=CVE-2025-21918 Référence CVE CVE-2025-21919 https://www.cve.org/CVERecord?id=CVE-2025-21919 Référence CVE CVE-2025-21920 https://www.cve.org/CVERecord?id=CVE-2025-21920 Référence CVE CVE-2025-21922 https://www.cve.org/CVERecord?id=CVE-2025-21922 Référence CVE CVE-2025-21924 https://www.cve.org/CVERecord?id=CVE-2025-21924 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-21927 https://www.cve.org/CVERecord?id=CVE-2025-21927 Référence CVE CVE-2025-21928 https://www.cve.org/CVERecord?id=CVE-2025-21928 Référence CVE CVE-2025-21929 https://www.cve.org/CVERecord?id=CVE-2025-21929 Référence CVE CVE-2025-21930 https://www.cve.org/CVERecord?id=CVE-2025-21930 Référence CVE CVE-2025-21934 https://www.cve.org/CVERecord?id=CVE-2025-21934 Référence CVE CVE-2025-21935 https://www.cve.org/CVERecord?id=CVE-2025-21935 Référence CVE CVE-2025-21936 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-21914 Référence CVE CVE-2025-21915 https://www.cve.org/CVERecord?id=CVE-2025-21915 Référence CVE CVE-2025-21916 https://www.cve.org/CVERecord?id=CVE-2025-21916 Référence CVE CVE-2025-21917 https://www.cve.org/CVERecord?id=CVE-2025-21917 Référence CVE CVE-2025-21918 https://www.cve.org/CVERecord?id=CVE-2025-21918 Référence CVE CVE-2025-21919 https://www.cve.org/CVERecord?id=CVE-2025-21919 Référence CVE CVE-2025-21920 https://www.cve.org/CVERecord?id=CVE-2025-21920 Référence CVE CVE-2025-21922 https://www.cve.org/CVERecord?id=CVE-2025-21922 Référence CVE CVE-2025-21924 https://www.cve.org/CVERecord?id=CVE-2025-21924 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-21927 https://www.cve.org/CVERecord?id=CVE-2025-21927 Référence CVE CVE-2025-21928 https://www.cve.org/CVERecord?id=CVE-2025-21928 Référence CVE CVE-2025-21929 https://www.cve.org/CVERecord?id=CVE-2025-21929 Référence CVE CVE-2025-21930 https://www.cve.org/CVERecord?id=CVE-2025-21930 Référence CVE CVE-2025-21934 https://www.cve.org/CVERecord?id=CVE-2025-21934 Référence CVE CVE-2025-21935 https://www.cve.org/CVERecord?id=CVE-2025-21935 Référence CVE CVE-2025-21936 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-21914 Référence CVE CVE-2025-21915 https://www.cve.org/CVERecord?id=CVE-2025-21915 Référence CVE CVE-2025-21916 https://www.cve.org/CVERecord?id=CVE-2025-21916 Référence CVE CVE-2025-21917 https://www.cve.org/CVERecord?id=CVE-2025-21917 Référence CVE CVE-2025-21918 https://www.cve.org/CVERecord?id=CVE-2025-21918 Référence CVE CVE-2025-21919 https://www.cve.org/CVERecord?id=CVE-2025-21919 Référence CVE CVE-2025-21920 https://www.cve.org/CVERecord?id=CVE-2025-21920 Référence CVE CVE-2025-21922 https://www.cve.org/CVERecord?id=CVE-2025-21922 Référence CVE CVE-2025-21924 https://www.cve.org/CVERecord?id=CVE-2025-21924 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-21927 https://www.cve.org/CVERecord?id=CVE-2025-21927 Référence CVE CVE-2025-21928 https://www.cve.org/CVERecord?id=CVE-2025-21928 Référence CVE CVE-2025-21929 https://www.cve.org/CVERecord?id=CVE-2025-21929 Référence CVE CVE-2025-21930 https://www.cve.org/CVERecord?id=CVE-2025-21930 Référence CVE CVE-2025-21934 https://www.cve.org/CVERecord?id=CVE-2025-21934 Référence CVE CVE-2025-21935 https://www.cve.org/CVERecord?id=CVE-2025-21935 Référence CVE CVE-2025-21936 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-21914 Référence CVE CVE-2025-21915 https://www.cve.org/CVERecord?id=CVE-2025-21915 Référence CVE CVE-2025-21916 https://www.cve.org/CVERecord?id=CVE-2025-21916 Référence CVE CVE-2025-21917 https://www.cve.org/CVERecord?id=CVE-2025-21917 Référence CVE CVE-2025-21918 https://www.cve.org/CVERecord?id=CVE-2025-21918 Référence CVE CVE-2025-21919 https://www.cve.org/CVERecord?id=CVE-2025-21919 Référence CVE CVE-2025-21920 https://www.cve.org/CVERecord?id=CVE-2025-21920 Référence CVE CVE-2025-21922 https://www.cve.org/CVERecord?id=CVE-2025-21922 Référence CVE CVE-2025-21924 https://www.cve.org/CVERecord?id=CVE-2025-21924 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-21927 https://www.cve.org/CVERecord?id=CVE-2025-21927 Référence CVE CVE-2025-21928 https://www.cve.org/CVERecord?id=CVE-2025-21928 Référence CVE CVE-2025-21929 https://www.cve.org/CVERecord?id=CVE-2025-21929 Référence CVE CVE-2025-21930 https://www.cve.org/CVERecord?id=CVE-2025-21930 Référence CVE CVE-2025-21934 https://www.cve.org/CVERecord?id=CVE-2025-21934 Référence CVE CVE-2025-21935 https://www.cve.org/CVERecord?id=CVE-2025-21935 Référence CVE CVE-2025-21936 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-21904 Référence CVE CVE-2025-21905 https://www.cve.org/CVERecord?id=CVE-2025-21905 Référence CVE CVE-2025-21909 https://www.cve.org/CVERecord?id=CVE-2025-21909 Référence CVE CVE-2025-21910 https://www.cve.org/CVERecord?id=CVE-2025-21910 Référence CVE CVE-2025-21914 https://www.cve.org/CVERecord?id=CVE-2025-21914 Référence CVE CVE-2025-21916 https://www.cve.org/CVERecord?id=CVE-2025-21916 Référence CVE CVE-2025-21917 https://www.cve.org/CVERecord?id=CVE-2025-21917 Référence CVE CVE-2025-21920 https://www.cve.org/CVERecord?id=CVE-2025-21920 Référence CVE CVE-2025-21922 https://www.cve.org/CVERecord?id=CVE-2025-21922 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-21928 https://www.cve.org/CVERecord?id=CVE-2025-21928 Référence CVE CVE-2025-21934 https://www.cve.org/CVERecord?id=CVE-2025-21934 Référence CVE CVE-2025-21935 https://www.cve.org/CVERecord?id=CVE-2025-21935 Référence CVE CVE-2025-21948 https://www.cve.org/CVERecord?id=CVE-2025-21948 Référence CVE CVE-2025-21956 https://www.cve.org/CVERecord?id=CVE-2025-21956 Référence CVE CVE-2025-21957 https://www.cve.org/CVERecord?id=CVE-2025-21957 Référence CVE CVE-2025-21959 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-21915 Référence CVE CVE-2025-21916 https://www.cve.org/CVERecord?id=CVE-2025-21916 Référence CVE CVE-2025-21917 https://www.cve.org/CVERecord?id=CVE-2025-21917 Référence CVE CVE-2025-21918 https://www.cve.org/CVERecord?id=CVE-2025-21918 Référence CVE CVE-2025-21919 https://www.cve.org/CVERecord?id=CVE-2025-21919 Référence CVE CVE-2025-21920 https://www.cve.org/CVERecord?id=CVE-2025-21920 Référence CVE CVE-2025-21922 https://www.cve.org/CVERecord?id=CVE-2025-21922 Référence CVE CVE-2025-21923 https://www.cve.org/CVERecord?id=CVE-2025-21923 Référence CVE CVE-2025-21924 https://www.cve.org/CVERecord?id=CVE-2025-21924 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-21927 https://www.cve.org/CVERecord?id=CVE-2025-21927 Référence CVE CVE-2025-21928 https://www.cve.org/CVERecord?id=CVE-2025-21928 Référence CVE CVE-2025-21929 https://www.cve.org/CVERecord?id=CVE-2025-21929 Référence CVE CVE-2025-21930 https://www.cve.org/CVERecord?id=CVE-2025-21930 Référence CVE CVE-2025-21934 https://www.cve.org/CVERecord?id=CVE-2025-21934 Référence CVE CVE-2025-21935 https://www.cve.org/CVERecord?id=CVE-2025-21935 Référence CVE CVE-2025-21936 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-21915 Référence CVE CVE-2025-21916 https://www.cve.org/CVERecord?id=CVE-2025-21916 Référence CVE CVE-2025-21917 https://www.cve.org/CVERecord?id=CVE-2025-21917 Référence CVE CVE-2025-21918 https://www.cve.org/CVERecord?id=CVE-2025-21918 Référence CVE CVE-2025-21919 https://www.cve.org/CVERecord?id=CVE-2025-21919 Référence CVE CVE-2025-21920 https://www.cve.org/CVERecord?id=CVE-2025-21920 Référence CVE CVE-2025-21922 https://www.cve.org/CVERecord?id=CVE-2025-21922 Référence CVE CVE-2025-21923 https://www.cve.org/CVERecord?id=CVE-2025-21923 Référence CVE CVE-2025-21924 https://www.cve.org/CVERecord?id=CVE-2025-21924 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-21927 https://www.cve.org/CVERecord?id=CVE-2025-21927 Référence CVE CVE-2025-21928 https://www.cve.org/CVERecord?id=CVE-2025-21928 Référence CVE CVE-2025-21929 https://www.cve.org/CVERecord?id=CVE-2025-21929 Référence CVE CVE-2025-21930 https://www.cve.org/CVERecord?id=CVE-2025-21930 Référence CVE CVE-2025-21934 https://www.cve.org/CVERecord?id=CVE-2025-21934 Référence CVE CVE-2025-21935 https://www.cve.org/CVERecord?id=CVE-2025-21935 Référence CVE CVE-2025-21936 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-21914 Référence CVE CVE-2025-21915 https://www.cve.org/CVERecord?id=CVE-2025-21915 Référence CVE CVE-2025-21916 https://www.cve.org/CVERecord?id=CVE-2025-21916 Référence CVE CVE-2025-21917 https://www.cve.org/CVERecord?id=CVE-2025-21917 Référence CVE CVE-2025-21918 https://www.cve.org/CVERecord?id=CVE-2025-21918 Référence CVE CVE-2025-21919 https://www.cve.org/CVERecord?id=CVE-2025-21919 Référence CVE CVE-2025-21922 https://www.cve.org/CVERecord?id=CVE-2025-21922 Référence CVE CVE-2025-21923 https://www.cve.org/CVERecord?id=CVE-2025-21923 Référence CVE CVE-2025-21924 https://www.cve.org/CVERecord?id=CVE-2025-21924 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-21927 https://www.cve.org/CVERecord?id=CVE-2025-21927 Référence CVE CVE-2025-21928 https://www.cve.org/CVERecord?id=CVE-2025-21928 Référence CVE CVE-2025-21929 https://www.cve.org/CVERecord?id=CVE-2025-21929 Référence CVE CVE-2025-21930 https://www.cve.org/CVERecord?id=CVE-2025-21930 Référence CVE CVE-2025-21931 https://www.cve.org/CVERecord?id=CVE-2025-21931 Référence CVE CVE-2025-21934 https://www.cve.org/CVERecord?id=CVE-2025-21934 Référence CVE CVE-2025-21935 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-21914 Référence CVE CVE-2025-21915 https://www.cve.org/CVERecord?id=CVE-2025-21915 Référence CVE CVE-2025-21916 https://www.cve.org/CVERecord?id=CVE-2025-21916 Référence CVE CVE-2025-21917 https://www.cve.org/CVERecord?id=CVE-2025-21917 Référence CVE CVE-2025-21918 https://www.cve.org/CVERecord?id=CVE-2025-21918 Référence CVE CVE-2025-21919 https://www.cve.org/CVERecord?id=CVE-2025-21919 Référence CVE CVE-2025-21922 https://www.cve.org/CVERecord?id=CVE-2025-21922 Référence CVE CVE-2025-21923 https://www.cve.org/CVERecord?id=CVE-2025-21923 Référence CVE CVE-2025-21924 https://www.cve.org/CVERecord?id=CVE-2025-21924 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-21927 https://www.cve.org/CVERecord?id=CVE-2025-21927 Référence CVE CVE-2025-21928 https://www.cve.org/CVERecord?id=CVE-2025-21928 Référence CVE CVE-2025-21930 https://www.cve.org/CVERecord?id=CVE-2025-21930 Référence CVE CVE-2025-21931 https://www.cve.org/CVERecord?id=CVE-2025-21931 Référence CVE CVE-2025-21934 https://www.cve.org/CVERecord?id=CVE-2025-21934 Référence CVE CVE-2025-21935 https://www.cve.org/CVERecord?id=CVE-2025-21935 Référence CVE CVE-2025-21936 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-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=CVE-2025-21980 Référence CVE CVE-2025-21985 https://www.cve.org/CVERecord?id=CVE-2025-21985 Référence CVE CVE-2025-21999 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-21913 Référence CVE CVE-2025-21914 https://www.cve.org/CVERecord?id=CVE-2025-21914 Référence CVE CVE-2025-21915 https://www.cve.org/CVERecord?id=CVE-2025-21915 Référence CVE CVE-2025-21916 https://www.cve.org/CVERecord?id=CVE-2025-21916 Référence CVE CVE-2025-21917 https://www.cve.org/CVERecord?id=CVE-2025-21917 Référence CVE CVE-2025-21918 https://www.cve.org/CVERecord?id=CVE-2025-21918 Référence CVE CVE-2025-21922 https://www.cve.org/CVERecord?id=CVE-2025-21922 Référence CVE CVE-2025-21923 https://www.cve.org/CVERecord?id=CVE-2025-21923 Référence CVE CVE-2025-21924 https://www.cve.org/CVERecord?id=CVE-2025-21924 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-21927 https://www.cve.org/CVERecord?id=CVE-2025-21927 Référence CVE CVE-2025-21928 https://www.cve.org/CVERecord?id=CVE-2025-21928 Référence CVE CVE-2025-21930 https://www.cve.org/CVERecord?id=CVE-2025-21930 Référence CVE CVE-2025-21931 https://www.cve.org/CVERecord?id=CVE-2025-21931 Référence CVE CVE-2025-21934 https://www.cve.org/CVERecord?id=CVE-2025-21934 Référence CVE CVE-2025-21935 https://www.cve.org/CVERecord?id=CVE-2025-21935 Référence CVE CVE-2025-21936 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-21913 Référence CVE CVE-2025-21914 https://www.cve.org/CVERecord?id=CVE-2025-21914 Référence CVE CVE-2025-21916 https://www.cve.org/CVERecord?id=CVE-2025-21916 Référence CVE CVE-2025-21917 https://www.cve.org/CVERecord?id=CVE-2025-21917 Référence CVE CVE-2025-21918 https://www.cve.org/CVERecord?id=CVE-2025-21918 Référence CVE CVE-2025-21919 https://www.cve.org/CVERecord?id=CVE-2025-21919 Référence CVE CVE-2025-21920 https://www.cve.org/CVERecord?id=CVE-2025-21920 Référence CVE CVE-2025-21922 https://www.cve.org/CVERecord?id=CVE-2025-21922 Référence CVE CVE-2025-21924 https://www.cve.org/CVERecord?id=CVE-2025-21924 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-21928 https://www.cve.org/CVERecord?id=CVE-2025-21928 Référence CVE CVE-2025-21934 https://www.cve.org/CVERecord?id=CVE-2025-21934 Référence CVE CVE-2025-21935 https://www.cve.org/CVERecord?id=CVE-2025-21935 Référence CVE CVE-2025-21936 https://www.cve.org/CVERecord?id=CVE-2025-21936 Référence CVE CVE-2025-21937 https://www.cve.org/CVERecord?id=CVE-2025-21937 Référence CVE CVE-2025-21938 https://www.cve.org/CVERecord?id=CVE-2025-21938 Référence CVE CVE-2025-21941 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-21913 Référence CVE CVE-2025-21914 https://www.cve.org/CVERecord?id=CVE-2025-21914 Référence CVE CVE-2025-21915 https://www.cve.org/CVERecord?id=CVE-2025-21915 Référence CVE CVE-2025-21916 https://www.cve.org/CVERecord?id=CVE-2025-21916 Référence CVE CVE-2025-21917 https://www.cve.org/CVERecord?id=CVE-2025-21917 Référence CVE CVE-2025-21918 https://www.cve.org/CVERecord?id=CVE-2025-21918 Référence CVE CVE-2025-21922 https://www.cve.org/CVERecord?id=CVE-2025-21922 Référence CVE CVE-2025-21923 https://www.cve.org/CVERecord?id=CVE-2025-21923 Référence CVE CVE-2025-21924 https://www.cve.org/CVERecord?id=CVE-2025-21924 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-21927 https://www.cve.org/CVERecord?id=CVE-2025-21927 Référence CVE CVE-2025-21928 https://www.cve.org/CVERecord?id=CVE-2025-21928 Référence CVE CVE-2025-21930 https://www.cve.org/CVERecord?id=CVE-2025-21930 Référence CVE CVE-2025-21931 https://www.cve.org/CVERecord?id=CVE-2025-21931 Référence CVE CVE-2025-21934 https://www.cve.org/CVERecord?id=CVE-2025-21934 Référence CVE CVE-2025-21935 https://www.cve.org/CVERecord?id=CVE-2025-21935 Référence CVE CVE-2025-21936 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-21913 Référence CVE CVE-2025-21914 https://www.cve.org/CVERecord?id=CVE-2025-21914 Référence CVE CVE-2025-21916 https://www.cve.org/CVERecord?id=CVE-2025-21916 Référence CVE CVE-2025-21917 https://www.cve.org/CVERecord?id=CVE-2025-21917 Référence CVE CVE-2025-21918 https://www.cve.org/CVERecord?id=CVE-2025-21918 Référence CVE CVE-2025-21919 https://www.cve.org/CVERecord?id=CVE-2025-21919 Référence CVE CVE-2025-21920 https://www.cve.org/CVERecord?id=CVE-2025-21920 Référence CVE CVE-2025-21922 https://www.cve.org/CVERecord?id=CVE-2025-21922 Référence CVE CVE-2025-21924 https://www.cve.org/CVERecord?id=CVE-2025-21924 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-21928 https://www.cve.org/CVERecord?id=CVE-2025-21928 Référence CVE CVE-2025-21934 https://www.cve.org/CVERecord?id=CVE-2025-21934 Référence CVE CVE-2025-21935 https://www.cve.org/CVERecord?id=CVE-2025-21935 Référence CVE CVE-2025-21936 https://www.cve.org/CVERecord?id=CVE-2025-21936 Référence CVE CVE-2025-21937 https://www.cve.org/CVERecord?id=CVE-2025-21937 Référence CVE CVE-2025-21938 https://www.cve.org/CVERecord?id=CVE-2025-21938 Référence CVE CVE-2025-21941 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2025-018415Linux の 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: < 2.6.12, 5.4.291 ≤ 5.4.*, 5.10.235 ≤ 5.10.*, 5.15.179 ≤ 5.15.*, 6.1.131 ≤ 6.1.*, 6.6.83 ≤ 6.6.*, 6.12.19 ≤ 6.12.*, 6.13.7 ≤ 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
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 1 Apr 2025 · Last source change 8 Sept 2026, 08:40 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2025-9396
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceUnavailable
NVD statusNVD modified after enrichment

Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < cd1c44327bbbd50fc24f2b38892f5f328b784d0f; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 13f3f872627f0f27c31245524fc11367756240ad; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 9b6f083db141ece0024be01526aa05aa978811cb; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 17f86e25431ebc15aa9245ff156414fdad47822d; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 416e8b4c20c6398044e93008deefd563289f477d; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 0f764208dc24ea043c3e20194d32aebf94f8459c; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 056e8a46d79e22983bae4267e0d9c52927076f46; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 64e6a754d33d31aa844b3ee66fb93ac84ca1565e · Fixed: < 2.6.12; 5.4.291 ≤ 5.4.*; 5.10.235 ≤ 5.10.*; 5.15.179 ≤ 5.15.*; 6.1.131 ≤ 6.1.*; 6.6.83 ≤ 6.6.*; 6.12.19 ≤ 6.12.*; 6.13.7 ≤ 6.13.*
    After
    Linux: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < cd1c44327bbbd50fc24f2b38892f5f328b784d0f, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 13f3f872627f0f27c31245524fc11367756240ad, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 9b6f083db141ece0024be01526aa05aa978811cb, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 17f86e25431ebc15aa9245ff156414fdad47822d, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 416e8b4c20c6398044e93008deefd563289f477d, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 0f764208dc24ea043c3e20194d32aebf94f8459c, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 056e8a46d79e22983bae4267e0d9c52927076f46, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 64e6a754d33d31aa844b3ee66fb93ac84ca1565e, 2.6.12 · Fixed: Linux: < 2.6.12, 5.4.291 ≤ 5.4.*, 5.10.235 ≤ 5.10.*, 5.15.179 ≤ 5.15.*, 6.1.131 ≤ 6.1.*, 6.6.83 ≤ 6.6.*, 6.12.19 ≤ 6.12.*, 6.13.7 ≤ 6.13.*, 6.14 ≤ *
    CNA ↗
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-9396↗Vendor CSAF · SUSE Product Security Team↗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-21925 · cve.blacktree.nl