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

net: allow small head cache usage with large MAX_SKB_FRAGS values

Linux · Linux

7.5HighCVSS 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 138 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:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.38% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • 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: Within 30 daysRemediation target: Within 180 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 138 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 · sourcelinuxNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian 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.

2 current
CVE-2025-21868 · CSAF 2.0 · revision 46 · interimSUSE Product Security TeamCVE-2025-21868
125 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: net: allow small head cache usage with large MAX_SKB_FRAGS values Sabrina reported the following splat: WARNING: CPU: 0 PID: 1 at net/core/dev.c:6935 netif_napi_add_weight_locked+0x8f2/0xba0 Modules linked in: CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.14.0-rc1-net-00092-g011b03359038 #996 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Arch Linux 1.16.3-1-1 04/01/2014 RIP: 0010:netif_napi_add_weight_locked+0x8f2/0xba0 Code: e8 c3 e6 6a fe 48 83 c4 28 5b 5d 41 5c 41 5d 41 5e 41 5f c3 cc cc cc cc c7 44 24 10 ff ff ff ff e9 8f fb ff ff e8 9e e6 6a fe 0b e9 d3 fe ff ff e8 92 e6 6a fe 48 8b 04 24 be ff ff ff ff 48 RSP: 0000:ffffc9000001fc60 EFLAGS: 00010293 RAX: 0000000000000000 RBX: ffff88806ce48128 RCX: 1ffff11001664b9e RDX: ffff888008f00040 RSI: ffffffff8317ca42 RDI: ffff88800b325cb6 RBP: ffff88800b325c40 R08: 0000000000000001 R09: ffffed100167502c R10: ffff88800b3a8163 R11: 0000000000000000 R12: ffff88800ac1c168 R13: ffff88800ac1c168 R14: ffff88800ac1c168 R15: 0000000000000007 FS: 0000000000000000(0000) GS:ffff88806ce00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffff888008201000 CR3: 0000000004c94001 CR4: 0000000000370ef0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: gro_cells_init+0x1ba/0x270 xfrm_input_init+0x4b/0x2a0 xfrm_init+0x38/0x50 ip_rt_init+0x2d7/0x350 ip_init+0xf/0x20 inet_init+0x406/0x590 do_one_initcall+0x9d/0x2e0 do_initcalls+0x23b/0x280 kernel_init_freeable+0x445/0x490 kernel_init+0x20/0x1d0 ret_from_fork+0x46/0x80 ret_from_fork_asm+0x1a/0x30 irq event stamp: 584330 hardirqs last enabled at (584338): [ ] __up_console_sem+0x77/0xb0 hardirqs last disabled at (584345): [ ] __up_console_sem+0x5c/0xb0 softirqs last enabled at (583242): [ ] netlink_insert+0x14d/0x470 softirqs last disabled at (583754): [ ] netif_napi_add_weight_locked+0x77d/0xba0 on kernel built with MAX_SKB_FRAGS=45, where SKB_WITH_OVERHEAD(1024) is smaller than GRO_MAX_HEAD. Such built additionally contains the revert of the single page frag cache so that napi_get_frags() ends up using the page frag allocator, triggering the splat. Note that the underlying issue is independent from the mentioned revert; address it ensuring that the small head cache will fit either TCP and GRO allocation and updating napi_alloc_skb() and __netdev_alloc_skb() to select kmalloc() usage for any allocation fitting such cache.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2025-21868 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: net: allow small head cache usage with large MAX_SKB_FRAGS values
118 known affected

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

  • kernel as a component of Red Hat Enterprise Linux 10
  • kernel-64k as a component of Red Hat Enterprise Linux 10
  • kernel-64k-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-devel as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-devel-matched as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules-extra as a component of Red Hat Enterprise Linux 10
  • kernel-64k-devel as a component of Red Hat Enterprise Linux 10
  • kernel-64k-devel-matched as a component of Red Hat Enterprise Linux 10
Summary
A flaw was found in the Linux kernel's network buffer allocation. When the kernel is built with specific configurations for network packet fragmentation, it can lead to a kernel warning or 'splat' due to incorrect handling of small head cache usage. A local attacker could potentially exploit this to cause a Denial of Service (DoS) by triggering the kernel to enter an unstable state.
Remediation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
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-8434

No EUVD known-exploited evidence

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

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended 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 138 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: net: allow small head cache usage with large MAX_SKB_FRAGS values Sabrina reported the following splat: WARNING: CPU: 0 PID: 1 at net/core/dev.c:6935 netif_napi_add_weight_locked+0x8f2/0xba0 Modules linked in: CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.14.0-rc1-net-00092-g011b03359038 #996 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Arch Linux 1.16.3-1-1 04/01/2014 RIP: 0010:netif_napi_add_weight_locked+0x8f2/0xba0 Code: e8 c3 e6 6a fe 48 83 c4 28 5b 5d 41 5c 41 5d 41 5e 41 5f c3 cc cc cc cc c7 44 24 10 ff ff ff ff e9 8f fb ff ff e8 9e e6 6a fe <0f> 0b e9 d3 fe ff ff e8 92 e6 6a fe 48 8b 04 24 be ff ff ff ff 48 RSP: 0000:ffffc9000001fc60 EFLAGS: 00010293 RAX: 0000000000000000 RBX: ffff88806ce48128 RCX: 1ffff11001664b9e RDX: ffff888008f00040 RSI: ffffffff8317ca42 RDI: ffff88800b325cb6 RBP: ffff88800b325c40 R08: 0000000000000001 R09: ffffed100167502c R10: ffff88800b3a8163 R11: 0000000000000000 R12: ffff88800ac1c168 R13: ffff88800ac1c168 R14: ffff88800ac1c168 R15: 0000000000000007 FS: 0000000000000000(0000) GS:ffff88806ce00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffff888008201000 CR3: 0000000004c94001 CR4: 0000000000370ef0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> gro_cells_init+0x1ba/0x270 xfrm_input_init+0x4b/0x2a0 xfrm_init+0x38/0x50 ip_rt_init+0x2d7/0x350 ip_init+0xf/0x20 inet_init+0x406/0x590 do_one_initcall+0x9d/0x2e0 do_initcalls+0x23b/0x280 kernel_init_freeable+0x445/0x490 kernel_init+0x20/0x1d0 ret_from_fork+0x46/0x80 ret_from_fork_asm+0x1a/0x30 </TASK> irq event stamp: 584330 hardirqs last enabled at (584338): [<ffffffff8168bf87>] __up_console_sem+0x77/0xb0 hardirqs last disabled at (584345): [<ffffffff8168bf6c>] __up_console_sem+0x5c/0xb0 softirqs last enabled at (583242): [<ffffffff833ee96d>] netlink_insert+0x14d/0x470 softirqs last disabled at (583754): [<ffffffff8317c8cd>] netif_napi_add_weight_locked+0x77d/0xba0 on kernel built with MAX_SKB_FRAGS=45, where SKB_WITH_OVERHEAD(1024) is smaller than GRO_MAX_HEAD. Such built additionally contains the revert of the single page frag cache so that napi_get_frags() ends up using the page frag allocator, triggering the splat. Note that the underlying issue is independent from the mentioned revert; address it ensuring that the small head cache will fit either TCP and GRO allocation and updating napi_alloc_skb() and __netdev_alloc_skb() to select kmalloc() usage for any allocation fitting such cache.

What

In the Linux kernel, the following vulnerability has been resolved: net: allow small head cache usage with large MAX_SKB_FRAGS values Sabrina reported the following splat: WARNING: CPU: 0 PID: 1 at net/core/dev.c:6935 netif_napi_add_weight_locked+0x8f2/0xba0 Modules linked in: CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.14.0-rc1-net-00092-g011b03359038 #996 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Arch Linux 1.16.3-1-1 04/01/2014 RIP: 0010:netif_napi_add_weight_locked+0x8f2/0xba0 Code: e8 c3 e6 6a fe 48 83 c4 28 5b 5d 41 5c 41 5d 41 5e 41 5f c3 cc cc cc cc c7 44 24 10 ff ff ff ff e9 8f fb ff ff e8 9e e6 6a fe <0f> 0b e9 d3 fe ff ff e8 92 e6 6a fe 48 8b 04 24 be ff ff ff ff 48 RSP: 0000:ffffc9000001fc60 EFLAGS: 00010293 RAX: 0000000000000000 RBX: ffff88806ce48128 RCX: 1ffff11001664b9e RDX: ffff888008f00040 RSI: ffffffff8317ca42 RDI: ffff88800b325cb6 RBP: ffff88800b325c40 R08: 0000000000000001 R09: ffffed100167502c R10: ffff88800b3a8163 R11: 0000000000000000 R12: ffff88800ac1c168 R13: ffff88800ac1c168 R14: ffff88800ac1c168 R15: 0000000000000007 FS: 0000000000000000(0000) GS:ffff88806ce00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffff888008201000 CR3: 0000000004c94001 CR4: 0000000000370ef0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> gro_cells_init+0x1ba/0x270 xfrm_input_init+0x4b/0x2a0 xfrm_init+0x38/0x50 ip_rt_init+0x2d7/0x350 ip_init+0xf/0x20 inet_init+0x406/0x590 do_one_initcall+0x9d/0x2e0 do_initcalls+0x23b/0x280 kernel_init_freeable+0x445/0x490 kernel_init+0x20/0x1d0 ret_from_fork+0x46/0x80 ret_from_fork_asm+0x1a/0x30 </TASK> irq event stamp: 584330 hardirqs last enabled at (584338): [<ffffffff8168bf87>] __up_console_sem+0x77/0xb0 hardirqs last disabled at (584345): [<ffffffff8168bf6c>] __up_console_sem+0x5c/0xb0 softirqs last enabled at (583242): [<ffffffff833ee96d>] netlink_insert+0x14d/0x470 softirqs last disabled at (583754): [<ffffffff8317c8cd>] netif_napi_add_weight_locked+0x77d/0xba0 on kernel built with MAX_SKB_FRAGS=45, where SKB_WITH_OVERHEAD(1024) is smaller than GRO_MAX_HEAD. Such built additionally contains the revert of the single page frag cache so that napi_get_frags() ends up using the page frag allocator, triggering the splat. Note that the underlying issue is independent from the mentioned revert; address it ensuring that the small head cache will fit either TCP and GRO allocation and updating napi_alloc_skb() and __netdev_alloc_skb() to select kmalloc() usage for any allocation fitting such cache.

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 a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In the Linux kernel, the following vulnerability has been resolved: net: allow small head cache usage with large MAX_SKB_FRAGS values Sabrina reported the following splat: WARNING: CPU: 0 PID: 1 at net/core/dev.c:6935 netif_napi_add_weight_locked+0x8f2/0xba0 Modules linked in: CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.14.0-rc1-net-00092-g011b03359038 #996 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Arch Linux 1.16.3-1-1 04/01/2014 RIP: 0010:netif_napi_add_weight_locked+0x8f2/0xba0 Code: e8 c3 e6 6a fe 48 83 c4 28 5b 5d 41 5c 41 5d 41 5e 41 5f c3 cc cc cc cc c7 44 24 10 ff ff ff ff e9 8f fb ff ff e8 9e e6 6a fe <0f> 0b e9 d3 fe ff ff e8 92 e6 6a fe 48 8b 04 24 be ff ff ff ff 48 RSP: 0000:ffffc9000001fc60 EFLAGS: 00010293 RAX: 0000000000000000 RBX: ffff88806ce48128 RCX: 1ffff11001664b9e RDX: ffff888008f00040 RSI: ffffffff8317ca42 RDI: ffff88800b325cb6 RBP: ffff88800b325c40 R08: 0000000000000001 R09: ffffed100167502c R10: ffff88800b3a8163 R11: 0000000000000000 R12: ffff88800ac1c168 R13: ffff88800ac1c168 R14: ffff88800ac1c168 R15: 0000000000000007 FS: 0000000000000000(0000) GS:ffff88806ce00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffff888008201000 CR3: 0000000004c94001 CR4: 0000000000370ef0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> gro_cells_init+0x1ba/0x270 xfrm_input_init+0x4b/0x2a0 xfrm_init+0x38/0x50 ip_rt_init+0x2d7/0x350 ip_init+0xf/0x20 inet_init+0x406/0x590 do_one_initcall+0x9d/0x2e0 do_initcalls+0x23b/0x280 kernel_init_freeable+0x445/0x490 kernel_init+0x20/0x1d0 ret_from_fork+0x46/0x80 ret_from_fork_asm+0x1a/0x30 </TASK> irq event stamp: 584330 hardirqs last enabled at (584338): [<ffffffff8168bf87>] __up_console_sem+0x77/0xb0 hardirqs last disabled at (584345): [<ffffffff8168bf6c>] __up_console_sem+0x5c/0xb0 softirqs last enabled at (583242): [<ffffffff833ee96d>] netlink_insert+0x14d/0x470 softirqs last disabled at (583754): [<ffffffff8317c8cd>] netif_napi_add_weight_locked+0x77d/0xba0 on kernel built with MAX_SKB_FRAGS=45, where SKB_WITH_OVERHEAD(1024) is smaller than GRO_MAX_HEAD. Such built additionally contains the revert of the single page frag cache so that napi_get_frags() ends up using the page frag allocator, triggering the splat. Note that the underlying issue is independent from the mentioned revert; address it ensuring that the small head cache will fit either TCP and GRO allocation and updating napi_alloc_skb() and __netdev_alloc_skb() to select kmalloc() usage for any allocation fitting such cache.

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 a network path may attempt exploitation without authentication or user interaction. 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
a network path → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
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:N/AC:L/PR:N/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.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing 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
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticated
A

Official authority intelligence

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

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-2025-AVI-0969Multiples vulnérabilités dans les produits VMware

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-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=CVE-2025-21877 Référence CVE CVE-2025-21878 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-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=CVE-2025-23140 Référence CVE CVE-2025-23142 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-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=CVE-2025-23142 Référence CVE CVE-2025-23144 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-58237 Référence CVE CVE-2025-21629 https://www.cve.org/CVERecord?id=CVE-2025-21629 Référence CVE CVE-2025-21658 https://www.cve.org/CVERecord?id=CVE-2025-21658 Référence CVE CVE-2025-21701 https://www.cve.org/CVERecord?id=CVE-2025-21701 Référence CVE CVE-2025-21702 https://www.cve.org/CVERecord?id=CVE-2025-21702 Référence CVE CVE-2025-21720 https://www.cve.org/CVERecord?id=CVE-2025-21720 Référence CVE CVE-2025-21731 https://www.cve.org/CVERecord?id=CVE-2025-21731 Référence CVE CVE-2025-21839 https://www.cve.org/CVERecord?id=CVE-2025-21839 Référence CVE CVE-2025-21854 https://www.cve.org/CVERecord?id=CVE-2025-21854 Référence CVE CVE-2025-21868 https://www.cve.org/CVERecord?id=CVE-2025-21868 Référence CVE CVE-2025-21872 https://www.cve.org/CVERecord?id=CVE-2025-21872 Référence CVE CVE-2025-21881 https://www.cve.org/CVERecord?id=CVE-2025-21881 Référence CVE CVE-2025-21898 https://www.cve.org/CVERecord?id=CVE-2025-21898 Référence CVE CVE-2025-21899 https://www.cve.org/CVERecord?id=CVE-2025-21899 Référence CVE CVE-2025-21920 https://www.cve.org/CVERecord?id=CVE-2025-21920 Référence CVE CVE-2025-21928 https://www.cve.org/CVERecord?id=CVE-2025-21928 Référence CVE CVE-2025-21938 https://www.cve.org/CVERecord?id=CVE-2025-21938 Référence CVE CVE-2025-21959 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-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=CVE-2025-37949 Référence CVE CVE-2025-37950 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-57982 Référence CVE CVE-2024-57999 https://www.cve.org/CVERecord?id=CVE-2024-57999 Référence CVE CVE-2024-58053 https://www.cve.org/CVERecord?id=CVE-2024-58053 Référence CVE CVE-2025-21658 https://www.cve.org/CVERecord?id=CVE-2025-21658 Référence CVE CVE-2025-21700 https://www.cve.org/CVERecord?id=CVE-2025-21700 Référence CVE CVE-2025-21702 https://www.cve.org/CVERecord?id=CVE-2025-21702 Référence CVE CVE-2025-21703 https://www.cve.org/CVERecord?id=CVE-2025-21703 Référence CVE CVE-2025-21720 https://www.cve.org/CVERecord?id=CVE-2025-21720 Référence CVE CVE-2025-21756 https://www.cve.org/CVERecord?id=CVE-2025-21756 Référence CVE CVE-2025-21868 https://www.cve.org/CVERecord?id=CVE-2025-21868 Référence CVE CVE-2025-21898 https://www.cve.org/CVERecord?id=CVE-2025-21898 Référence CVE CVE-2025-21899 https://www.cve.org/CVERecord?id=CVE-2025-21899 Référence CVE CVE-2025-21920 https://www.cve.org/CVERecord?id=CVE-2025-21920 Référence CVE CVE-2025-21938 https://www.cve.org/CVERecord?id=CVE-2025-21938 Référence CVE CVE-2025-21959 https://www.cve.org/CVERecord?id=CVE-2025-21959 Référence CVE CVE-2025-21997 https://www.cve.org/CVERecord?id=CVE-2025-21997 Référence CVE CVE-2025-22035 https://www.cve.org/CVERecord?id=CVE-2025-22035 Référence CVE CVE-2025-22083 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-21703 Référence CVE CVE-2025-21713 https://www.cve.org/CVERecord?id=CVE-2025-21713 Référence CVE CVE-2025-21720 https://www.cve.org/CVERecord?id=CVE-2025-21720 Référence CVE CVE-2025-21756 https://www.cve.org/CVERecord?id=CVE-2025-21756 Référence CVE CVE-2025-21770 https://www.cve.org/CVERecord?id=CVE-2025-21770 Référence CVE CVE-2025-21805 https://www.cve.org/CVERecord?id=CVE-2025-21805 Référence CVE CVE-2025-21824 https://www.cve.org/CVERecord?id=CVE-2025-21824 Référence CVE CVE-2025-21842 https://www.cve.org/CVERecord?id=CVE-2025-21842 Référence CVE CVE-2025-21849 https://www.cve.org/CVERecord?id=CVE-2025-21849 Référence CVE CVE-2025-21868 https://www.cve.org/CVERecord?id=CVE-2025-21868 Référence CVE CVE-2025-21880 https://www.cve.org/CVERecord?id=CVE-2025-21880 Référence CVE CVE-2025-21898 https://www.cve.org/CVERecord?id=CVE-2025-21898 Référence CVE CVE-2025-21899 https://www.cve.org/CVERecord?id=CVE-2025-21899 Référence CVE CVE-2025-21901 https://www.cve.org/CVERecord?id=CVE-2025-21901 Référence CVE CVE-2025-21911 https://www.cve.org/CVERecord?id=CVE-2025-21911 Référence CVE CVE-2025-21920 https://www.cve.org/CVERecord?id=CVE-2025-21920 Référence CVE CVE-2025-21938 https://www.cve.org/CVERecord?id=CVE-2025-21938 Référence CVE CVE-2025-21939 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-21703 Référence CVE CVE-2025-21713 https://www.cve.org/CVERecord?id=CVE-2025-21713 Référence CVE CVE-2025-21720 https://www.cve.org/CVERecord?id=CVE-2025-21720 Référence CVE CVE-2025-21756 https://www.cve.org/CVERecord?id=CVE-2025-21756 Référence CVE CVE-2025-21770 https://www.cve.org/CVERecord?id=CVE-2025-21770 Référence CVE CVE-2025-21805 https://www.cve.org/CVERecord?id=CVE-2025-21805 Référence CVE CVE-2025-21824 https://www.cve.org/CVERecord?id=CVE-2025-21824 Référence CVE CVE-2025-21842 https://www.cve.org/CVERecord?id=CVE-2025-21842 Référence CVE CVE-2025-21849 https://www.cve.org/CVERecord?id=CVE-2025-21849 Référence CVE CVE-2025-21868 https://www.cve.org/CVERecord?id=CVE-2025-21868 Référence CVE CVE-2025-21880 https://www.cve.org/CVERecord?id=CVE-2025-21880 Référence CVE CVE-2025-21888 https://www.cve.org/CVERecord?id=CVE-2025-21888 Référence CVE CVE-2025-21898 https://www.cve.org/CVERecord?id=CVE-2025-21898 Référence CVE CVE-2025-21899 https://www.cve.org/CVERecord?id=CVE-2025-21899 Référence CVE CVE-2025-21901 https://www.cve.org/CVERecord?id=CVE-2025-21901 Référence CVE CVE-2025-21911 https://www.cve.org/CVERecord?id=CVE-2025-21911 Référence CVE CVE-2025-21920 https://www.cve.org/CVERecord?id=CVE-2025-21920 Référence CVE CVE-2025-21938 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-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=CVE-2025-21877 Référence CVE CVE-2025-21878 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2025-018355Linux の 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: < 6.4, 6.6.117 ≤ 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
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 27 Mar 2025 · Last source change 5 Aug 2026, 11:55 UTC · CWE not yet assigned

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-8434
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 ↗

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

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2025-8434↗Vendor CSAF · SUSE Product Security Team↗Patch or update reference↗Patch or update reference↗Patch or update reference↗CVE authority or vendor 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-21868 · cve.blacktree.nl