BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-52943High confidence

net: skbuff: fix missing zerocopy reference in pskb_carve helpers

Linux · Linux

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

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

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

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

Evidence used

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

Compensating controls

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

Verification

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

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

Cross-source reconciliation

Remediation availability differs by product scope

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

Distribution package intelligence

Release-specific package status

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

24 package states
Package result overrides the generic status

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

Repository candidate not checked

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

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.94-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.176-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.12-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.12-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-fdeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical 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-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-2026-52943 · CSAF 2.0 · revision 29 · interimSUSE Product Security TeamCVE-2026-52943
128 known affected

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

  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
Summary
In the Linux kernel, the following vulnerability has been resolved: net: skbuff: fix missing zerocopy reference in pskb_carve helpers pskb_carve_inside_header() and pskb_carve_inside_nonlinear() both copy the old skb_shared_info header into a new buffer via memcpy(), which includes the destructor_arg pointer (uarg) for MSG_ZEROCOPY skbs. Neither function calls net_zcopy_get() for the new shinfo, creating an unaccounted holder: every skb_shared_info with destructor_arg set will call skb_zcopy_clear() once when freed, but the corresponding net_zcopy_get() was never called for the new copy. Repeated calls drive uarg->refcnt to zero prematurely, freeing ubuf_info_msgzc while TX skbs still hold live destructor_arg pointers. KASAN reports use-after-free on a freed ubuf_info_msgzc: BUG: KASAN: slab-use-after-free in skb_release_data+0x77b/0x810 Read of size 8 at addr ffff88801574d3e8 by task poc/220 Call Trace: skb_release_data+0x77b/0x810 kfree_skb_list_reason+0x13e/0x610 skb_release_data+0x4cd/0x810 sk_skb_reason_drop+0xf3/0x340 skb_queue_purge_reason+0x282/0x440 rds_tcp_inc_free+0x1e/0x30 rds_recvmsg+0x354/0x1780 __sys_recvmsg+0xdf/0x180 Allocated by task 219: msg_zerocopy_realloc+0x157/0x7b0 tcp_sendmsg_locked+0x2892/0x3ba0 Freed by task 219: ip_recv_error+0x74a/0xb10 tcp_recvmsg+0x475/0x530 The skb consuming the late access still referenced the same uarg via shinfo->destructor_arg copied by pskb_carve_inside_nonlinear() without a refcount bump. This has been verified to be reliably exploitable: a working proof-of-concept achieves full root privilege escalation from an unprivileged local user on a default kernel configuration. The fix follows the pattern of pskb_expand_head() which has the same memcpy/cloned structure. For pskb_carve_inside_header(), net_zcopy_get() is placed after skb_orphan_frags() succeeds, so the orphan error path needs no cleanup. For pskb_carve_inside_nonlinear(), net_zcopy_get() is placed after all failure points and just before skb_release_data(), so no error path needs cleanup at all -- matching pskb_expand_head() more closely and avoiding the need for a balancing net_zcopy_put().
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: net: skbuff: fix missing zerocopy reference in pskb_carve helpers pskb_carve_inside_header() and pskb_carve_inside_nonlinear() both copy the old skb_shared_info header into a new buffer via memcpy(), which includes the destructor_arg pointer (uarg) for MSG_ZEROCOPY skbs. Neither function calls net_zcopy_get() for the new shinfo, creating an unaccounted holder: every skb_shared_info with destructor_arg set will call skb_zcopy_clear() once when freed, but the corresponding net_zcopy_get() was never called for the new copy. Repeated calls drive uarg->refcnt to zero prematurely, freeing ubuf_info_msgzc while TX skbs still hold live destructor_arg pointers. KASAN reports use-after-free on a freed ubuf_info_msgzc: BUG: KASAN: slab-use-after-free in skb_release_data+0x77b/0x810 Read of size 8 at addr ffff88801574d3e8 by task poc/220 Call Trace: skb_release_data+0x77b/0x810 kfree_skb_list_reason+0x13e/0x610 skb_release_data+0x4cd/0x810 sk_skb_reason_drop+0xf3/0x340 skb_queue_purge_reason+0x282/0x440 rds_tcp_inc_free+0x1e/0x30 rds_recvmsg+0x354/0x1780 __sys_recvmsg+0xdf/0x180 Allocated by task 219: msg_zerocopy_realloc+0x157/0x7b0 tcp_sendmsg_locked+0x2892/0x3ba0 Freed by task 219: ip_recv_error+0x74a/0xb10 tcp_recvmsg+0x475/0x530 The skb consuming the late access still referenced the same uarg via shinfo->destructor_arg copied by pskb_carve_inside_nonlinear() without a refcount bump. This has been verified to be reliably exploitable: a working proof-of-concept achieves full root privilege escalation from an unprivileged local user on a default kernel configuration. The fix follows the pattern of pskb_expand_head() which has the same memcpy/cloned structure. For pskb_carve_inside_header(), net_zcopy_get() is placed after skb_orphan_frags() succeeds, so the orphan error path needs no cleanup. For pskb_carve_inside_nonlinear(), net_zcopy_get() is placed after all failure points and just before skb_release_data(), so no error path needs cleanup at all -- matching pskb_expand_head() more closely and avoiding the need for a balancing net_zcopy_put().
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-2026-38732

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: net: skbuff: fix missing zerocopy reference in pskb_carve helpers pskb_carve_inside_header() and pskb_carve_inside_nonlinear() both copy the old skb_shared_info header into a new buffer via memcpy(), which includes the destructor_arg pointer (uarg) for MSG_ZEROCOPY skbs. Neither function calls net_zcopy_get() for the new shinfo, creating an unaccounted holder: every skb_shared_info with destructor_arg set will call skb_zcopy_clear() once when freed, but the corresponding net_zcopy_get() was never called for the new copy. Repeated calls drive uarg->refcnt to zero prematurely, freeing ubuf_info_msgzc while TX skbs still hold live destructor_arg pointers. KASAN reports use-after-free on a freed ubuf_info_msgzc: BUG: KASAN: slab-use-after-free in skb_release_data+0x77b/0x810 Read of size 8 at addr ffff88801574d3e8 by task poc/220 Call Trace: skb_release_data+0x77b/0x810 kfree_skb_list_reason+0x13e/0x610 skb_release_data+0x4cd/0x810 sk_skb_reason_drop+0xf3/0x340 skb_queue_purge_reason+0x282/0x440 rds_tcp_inc_free+0x1e/0x30 rds_recvmsg+0x354/0x1780 __sys_recvmsg+0xdf/0x180 Allocated by task 219: msg_zerocopy_realloc+0x157/0x7b0 tcp_sendmsg_locked+0x2892/0x3ba0 Freed by task 219: ip_recv_error+0x74a/0xb10 tcp_recvmsg+0x475/0x530 The skb consuming the late access still referenced the same uarg via shinfo->destructor_arg copied by pskb_carve_inside_nonlinear() without a refcount bump. This has been verified to be reliably exploitable: a working proof-of-concept achieves full root privilege escalation from an unprivileged local user on a default kernel configuration. The fix follows the pattern of pskb_expand_head() which has the same memcpy/cloned structure. For pskb_carve_inside_header(), net_zcopy_get() is placed after skb_orphan_frags() succeeds, so the orphan error path needs no cleanup. For pskb_carve_inside_nonlinear(), net_zcopy_get() is placed after all failure points and just before skb_release_data(), so no error path needs cleanup at all -- matching pskb_expand_head() more closely and avoiding the need for a balancing net_zcopy_put().

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
7.8 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

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

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: net: skbuff: fix missing zerocopy reference in pskb_carve helpers pskb_carve_inside_header() and pskb_carve_inside_nonlinear() both copy the old skb_shared_info header into a new buffer via memcpy(), which includes the destructor_arg pointer (uarg) for MSG_ZEROCOPY skbs. Neither function calls net_zcopy_get() for the new shinfo, creating an unaccounted holder: every skb_shared_info with destructor_arg set will call skb_zcopy_clear() once when freed, but the corresponding net_zcopy_get() was never called for the new copy. Repeated calls drive uarg->refcnt to zero prematurely, freeing ubuf_info_msgzc while TX skbs still hold live destructor_arg pointers. KASAN reports use-after-free on a freed ubuf_info_msgzc: BUG: KASAN: slab-use-after-free in skb_release_data+0x77b/0x810 Read of size 8 at addr ffff88801574d3e8 by task poc/220 Call Trace: skb_release_data+0x77b/0x810 kfree_skb_list_reason+0x13e/0x610 skb_release_data+0x4cd/0x810 sk_skb_reason_drop+0xf3/0x340 skb_queue_purge_reason+0x282/0x440 rds_tcp_inc_free+0x1e/0x30 rds_recvmsg+0x354/0x1780 __sys_recvmsg+0xdf/0x180 Allocated by task 219: msg_zerocopy_realloc+0x157/0x7b0 tcp_sendmsg_locked+0x2892/0x3ba0 Freed by task 219: ip_recv_error+0x74a/0xb10 tcp_recvmsg+0x475/0x530 The skb consuming the late access still referenced the same uarg via shinfo->destructor_arg copied by pskb_carve_inside_nonlinear() without a refcount bump. This has been verified to be reliably exploitable: a working proof-of-concept achieves full root privilege escalation from an unprivileged local user on a default kernel configuration. The fix follows the pattern of pskb_expand_head() which has the same memcpy/cloned structure. For pskb_carve_inside_header(), net_zcopy_get() is placed after skb_orphan_frags() succeeds, so the orphan error path needs no cleanup. For pskb_carve_inside_nonlinear(), net_zcopy_get() is placed after all failure points and just before skb_release_data(), so no error path needs cleanup at all -- matching pskb_expand_head() more closely and avoiding the need for a balancing net_zcopy_put().

What

In the Linux kernel, the following vulnerability has been resolved: net: skbuff: fix missing zerocopy reference in pskb_carve helpers pskb_carve_inside_header() and pskb_carve_inside_nonlinear() both copy the old skb_shared_info header into a new buffer via memcpy(), which includes the destructor_arg pointer (uarg) for MSG_ZEROCOPY skbs. Neither function calls net_zcopy_get() for the new shinfo, creating an unaccounted holder: every skb_shared_info with destructor_arg set will call skb_zcopy_clear() once when freed, but the corresponding net_zcopy_get() was never called for the new copy. Repeated calls drive uarg->refcnt to zero prematurely, freeing ubuf_info_msgzc while TX skbs still hold live destructor_arg pointers. KASAN reports use-after-free on a freed ubuf_info_msgzc: BUG: KASAN: slab-use-after-free in skb_release_data+0x77b/0x810 Read of size 8 at addr ffff88801574d3e8 by task poc/220 Call Trace: skb_release_data+0x77b/0x810 kfree_skb_list_reason+0x13e/0x610 skb_release_data+0x4cd/0x810 sk_skb_reason_drop+0xf3/0x340 skb_queue_purge_reason+0x282/0x440 rds_tcp_inc_free+0x1e/0x30 rds_recvmsg+0x354/0x1780 __sys_recvmsg+0xdf/0x180 Allocated by task 219: msg_zerocopy_realloc+0x157/0x7b0 tcp_sendmsg_locked+0x2892/0x3ba0 Freed by task 219: ip_recv_error+0x74a/0xb10 tcp_recvmsg+0x475/0x530 The skb consuming the late access still referenced the same uarg via shinfo->destructor_arg copied by pskb_carve_inside_nonlinear() without a refcount bump. This has been verified to be reliably exploitable: a working proof-of-concept achieves full root privilege escalation from an unprivileged local user on a default kernel configuration. The fix follows the pattern of pskb_expand_head() which has the same memcpy/cloned structure. For pskb_carve_inside_header(), net_zcopy_get() is placed after skb_orphan_frags() succeeds, so the orphan error path needs no cleanup. For pskb_carve_inside_nonlinear(), net_zcopy_get() is placed after all failure points and just before skb_release_data(), so no error path needs cleanup at all -- matching pskb_expand_head() more closely and avoiding the need for a balancing net_zcopy_put().

Why

The product uses a reference count to manage a resource, but it does not update or incorrectly updates the reference count.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may gain additional privileges.

What

In the Linux kernel, the following vulnerability has been resolved: net: skbuff: fix missing zerocopy reference in pskb_carve helpers pskb_carve_inside_header() and pskb_carve_inside_nonlinear() both copy the old skb_shared_info header into a new buffer via memcpy(), which includes the destructor_arg pointer (uarg) for MSG_ZEROCOPY skbs. Neither function calls net_zcopy_get() for the new shinfo, creating an unaccounted holder: every skb_shared_info with destructor_arg set will call skb_zcopy_clear() once when freed, but the corresponding net_zcopy_get() was never called for the new copy. Repeated calls drive uarg->refcnt to zero prematurely, freeing ubuf_info_msgzc while TX skbs still hold live destructor_arg pointers. KASAN reports use-after-free on a freed ubuf_info_msgzc: BUG: KASAN: slab-use-after-free in skb_release_data+0x77b/0x810 Read of size 8 at addr ffff88801574d3e8 by task poc/220 Call Trace: skb_release_data+0x77b/0x810 kfree_skb_list_reason+0x13e/0x610 skb_release_data+0x4cd/0x810 sk_skb_reason_drop+0xf3/0x340 skb_queue_purge_reason+0x282/0x440 rds_tcp_inc_free+0x1e/0x30 rds_recvmsg+0x354/0x1780 __sys_recvmsg+0xdf/0x180 Allocated by task 219: msg_zerocopy_realloc+0x157/0x7b0 tcp_sendmsg_locked+0x2892/0x3ba0 Freed by task 219: ip_recv_error+0x74a/0xb10 tcp_recvmsg+0x475/0x530 The skb consuming the late access still referenced the same uarg via shinfo->destructor_arg copied by pskb_carve_inside_nonlinear() without a refcount bump. This has been verified to be reliably exploitable: a working proof-of-concept achieves full root privilege escalation from an unprivileged local user on a default kernel configuration. The fix follows the pattern of pskb_expand_head() which has the same memcpy/cloned structure. For pskb_carve_inside_header(), net_zcopy_get() is placed after skb_orphan_frags() succeeds, so the orphan error path needs no cleanup. For pskb_carve_inside_nonlinear(), net_zcopy_get() is placed after all failure points and just before skb_release_data(), so no error path needs cleanup at all -- matching pskb_expand_head() more closely and avoiding the need for a balancing net_zcopy_put().

Why

The product uses a reference count to manage a resource, but it does not update or incorrectly updates the reference count.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may gain additional privileges.

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 → Improper Update of Reference Count → gain additional privileges
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-911 ↗

CWE-911: Improper Update of Reference Count. The product uses a reference count to manage a resource, but it does not update or incorrectly updates the reference count.

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

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

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

Official authority intelligence

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

ENISA EUVD · EUVD-2026-38732Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: net: skbuff: fix missing zerocopy reference in pskb_carve helpers pskb_carve_inside_header() and pskb_carve_inside_nonlinear() both copy the old skb_shared_info header into a new buffer via memcpy(), which includes the destructor_arg pointer (uarg) for MSG_ZEROCOPY skbs. Neither function calls net_zcopy_get() for the new shinfo, creating an unaccounted holder: every skb_shared_info with destructor_arg set will call skb_zcopy_clear() once when freed, but the corresponding net_zcopy_get() was never called for the new copy. Repeated calls drive uarg->refcnt to zero prematurely, freeing ubuf_info_msgzc while TX skbs still hold live destructor_arg pointers. KASAN reports use-after-free on a freed ubuf_info_msgzc: BUG: KASAN: slab-use-after-free in skb_release_data+0x77b/0x810 Read of size 8 at addr ffff88801574d3e8 by task poc/220 Call Trace: skb_release_data+0x77b/0x810 kfree_skb_list_reason+0x13e/0x610 skb_release_data+0x4cd/0x810 sk_skb_reason_drop+0xf3/0x340 skb_queue_purge_reason+0x282/0x440 rds_tcp_inc_free+0x1e/0x30 rds_recvmsg+0x354/0x1780 __sys_recvmsg+0xdf/0x180 Allocated by task 219: msg_zerocopy_realloc+0x157/0x7b0 tcp_sendmsg_locked+0x2892/0x3ba0 Freed by task 219: ip_recv_error+0x74a/0xb10 tcp_recvmsg+0x475/0x530 The skb consuming the late access still referenced the same uarg via shinfo->destructor_arg copied by pskb_carve_inside_nonlinear() without a refcount bump. This has been verified to be reliably exploitable: a working proof-of-concept achieves full root privilege escalation from an unprivileged local user on a default kernel configuration. The fix follows the pattern of pskb_expand_head() which has the same memcpy/cloned structure. For pskb_carve_inside_header(), net_zcopy_get() is placed after skb_orphan_frags() succeeds, so the orphan error path needs no cleanup. For pskb_carve_inside_nonlinear(), net_zcopy_get() is placed after all failure points and just before skb_release_data(), so no error path needs cleanup at all -- matching pskb_expand_head() more closely and avoiding the need for a balancing net_zcopy_put().

Official EUVD record ↗
BSI · German · WID-SEC-2026-2158Linux Kernel: Schwachstelle ermöglicht Erlangen von Administratorrechten

Ein lokaler Angreifer kann eine Schwachstelle in Linux Kernel ausnutzen, um Administratorrechte zu erlangen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260701Security Bulletin 1 July 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 1 July 2026, published on 1 July 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

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

d?id=CVE-2026-52934 Référence CVE CVE-2026-52935 https://www.cve.org/CVERecord?id=CVE-2026-52935 Référence CVE CVE-2026-52936 https://www.cve.org/CVERecord?id=CVE-2026-52936 Référence CVE CVE-2026-52937 https://www.cve.org/CVERecord?id=CVE-2026-52937 Référence CVE CVE-2026-52938 https://www.cve.org/CVERecord?id=CVE-2026-52938 Référence CVE CVE-2026-52939 https://www.cve.org/CVERecord?id=CVE-2026-52939 Référence CVE CVE-2026-52940 https://www.cve.org/CVERecord?id=CVE-2026-52940 Référence CVE CVE-2026-52941 https://www.cve.org/CVERecord?id=CVE-2026-52941 Référence CVE CVE-2026-52942 https://www.cve.org/CVERecord?id=CVE-2026-52942 Référence CVE CVE-2026-52943 https://www.cve.org/CVERecord?id=CVE-2026-52943 Référence CVE CVE-2026-52944 https://www.cve.org/CVERecord?id=CVE-2026-52944 Référence CVE CVE-2026-52947 https://www.cve.org/CVERecord?id=CVE-2026-52947 Référence CVE CVE-2026-52948 https://www.cve.org/CVERecord?id=CVE-2026-52948 Référence CVE CVE-2026-52949 https://www.cve.org/CVERecord?id=CVE-2026-52949 Référence CVE CVE-2026-52950 https://www.cve.org/CVERecord?id=CVE-2026-52950 Référence CVE CVE-2026-52951 https://www.cve.org/CVERecord?id=CVE-2026-52951 Référence CVE CVE-2026-52952 https://www.cve.org/CVERecord?id=CVE-2026-52952 Référence CVE CVE-2026-52953 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-52934 Référence CVE CVE-2026-52935 https://www.cve.org/CVERecord?id=CVE-2026-52935 Référence CVE CVE-2026-52936 https://www.cve.org/CVERecord?id=CVE-2026-52936 Référence CVE CVE-2026-52937 https://www.cve.org/CVERecord?id=CVE-2026-52937 Référence CVE CVE-2026-52938 https://www.cve.org/CVERecord?id=CVE-2026-52938 Référence CVE CVE-2026-52939 https://www.cve.org/CVERecord?id=CVE-2026-52939 Référence CVE CVE-2026-52940 https://www.cve.org/CVERecord?id=CVE-2026-52940 Référence CVE CVE-2026-52941 https://www.cve.org/CVERecord?id=CVE-2026-52941 Référence CVE CVE-2026-52942 https://www.cve.org/CVERecord?id=CVE-2026-52942 Référence CVE CVE-2026-52943 https://www.cve.org/CVERecord?id=CVE-2026-52943 Référence CVE CVE-2026-52944 https://www.cve.org/CVERecord?id=CVE-2026-52944 Référence CVE CVE-2026-52947 https://www.cve.org/CVERecord?id=CVE-2026-52947 Référence CVE CVE-2026-52948 https://www.cve.org/CVERecord?id=CVE-2026-52948 Référence CVE CVE-2026-52949 https://www.cve.org/CVERecord?id=CVE-2026-52949 Référence CVE CVE-2026-52950 https://www.cve.org/CVERecord?id=CVE-2026-52950 Référence CVE CVE-2026-52951 https://www.cve.org/CVERecord?id=CVE-2026-52951 Référence CVE CVE-2026-52952 https://www.cve.org/CVERecord?id=CVE-2026-52952 Référence CVE CVE-2026-52953 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-52934 Référence CVE CVE-2026-52935 https://www.cve.org/CVERecord?id=CVE-2026-52935 Référence CVE CVE-2026-52936 https://www.cve.org/CVERecord?id=CVE-2026-52936 Référence CVE CVE-2026-52937 https://www.cve.org/CVERecord?id=CVE-2026-52937 Référence CVE CVE-2026-52938 https://www.cve.org/CVERecord?id=CVE-2026-52938 Référence CVE CVE-2026-52939 https://www.cve.org/CVERecord?id=CVE-2026-52939 Référence CVE CVE-2026-52940 https://www.cve.org/CVERecord?id=CVE-2026-52940 Référence CVE CVE-2026-52941 https://www.cve.org/CVERecord?id=CVE-2026-52941 Référence CVE CVE-2026-52942 https://www.cve.org/CVERecord?id=CVE-2026-52942 Référence CVE CVE-2026-52943 https://www.cve.org/CVERecord?id=CVE-2026-52943 Référence CVE CVE-2026-52944 https://www.cve.org/CVERecord?id=CVE-2026-52944 Référence CVE CVE-2026-52947 https://www.cve.org/CVERecord?id=CVE-2026-52947 Référence CVE CVE-2026-52948 https://www.cve.org/CVERecord?id=CVE-2026-52948 Référence CVE CVE-2026-52949 https://www.cve.org/CVERecord?id=CVE-2026-52949 Référence CVE CVE-2026-52950 https://www.cve.org/CVERecord?id=CVE-2026-52950 Référence CVE CVE-2026-52951 https://www.cve.org/CVERecord?id=CVE-2026-52951 Référence CVE CVE-2026-52952 https://www.cve.org/CVERecord?id=CVE-2026-52952 Référence CVE CVE-2026-52953 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-52927 Référence CVE CVE-2026-52928 https://www.cve.org/CVERecord?id=CVE-2026-52928 Référence CVE CVE-2026-52931 https://www.cve.org/CVERecord?id=CVE-2026-52931 Référence CVE CVE-2026-52932 https://www.cve.org/CVERecord?id=CVE-2026-52932 Référence CVE CVE-2026-52933 https://www.cve.org/CVERecord?id=CVE-2026-52933 Référence CVE CVE-2026-52934 https://www.cve.org/CVERecord?id=CVE-2026-52934 Référence CVE CVE-2026-52936 https://www.cve.org/CVERecord?id=CVE-2026-52936 Référence CVE CVE-2026-52937 https://www.cve.org/CVERecord?id=CVE-2026-52937 Référence CVE CVE-2026-52941 https://www.cve.org/CVERecord?id=CVE-2026-52941 Référence CVE CVE-2026-52943 https://www.cve.org/CVERecord?id=CVE-2026-52943 Référence CVE CVE-2026-52944 https://www.cve.org/CVERecord?id=CVE-2026-52944 Référence CVE CVE-2026-52949 https://www.cve.org/CVERecord?id=CVE-2026-52949 Référence CVE CVE-2026-52950 https://www.cve.org/CVERecord?id=CVE-2026-52950 Référence CVE CVE-2026-52951 https://www.cve.org/CVERecord?id=CVE-2026-52951 Référence CVE CVE-2026-52952 https://www.cve.org/CVERecord?id=CVE-2026-52952 Référence CVE CVE-2026-52953 https://www.cve.org/CVERecord?id=CVE-2026-52953 Référence CVE CVE-2026-52954 https://www.cve.org/CVERecord?id=CVE-2026-52954 Référence CVE CVE-2026-52955 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-46322 Référence CVE CVE-2026-46328 https://www.cve.org/CVERecord?id=CVE-2026-46328 Référence CVE CVE-2026-46331 https://www.cve.org/CVERecord?id=CVE-2026-46331 Référence CVE CVE-2026-52908 https://www.cve.org/CVERecord?id=CVE-2026-52908 Référence CVE CVE-2026-52909 https://www.cve.org/CVERecord?id=CVE-2026-52909 Référence CVE CVE-2026-52919 https://www.cve.org/CVERecord?id=CVE-2026-52919 Référence CVE CVE-2026-52923 https://www.cve.org/CVERecord?id=CVE-2026-52923 Référence CVE CVE-2026-52924 https://www.cve.org/CVERecord?id=CVE-2026-52924 Référence CVE CVE-2026-52933 https://www.cve.org/CVERecord?id=CVE-2026-52933 Référence CVE CVE-2026-52943 https://www.cve.org/CVERecord?id=CVE-2026-52943 Référence CVE CVE-2026-52954 https://www.cve.org/CVERecord?id=CVE-2026-52954 Référence CVE CVE-2026-52955 https://www.cve.org/CVERecord?id=CVE-2026-52955 Référence CVE CVE-2026-52956 https://www.cve.org/CVERecord?id=CVE-2026-52956 Référence CVE CVE-2026-52957 https://www.cve.org/CVERecord?id=CVE-2026-52957 Référence CVE CVE-2026-52958 https://www.cve.org/CVERecord?id=CVE-2026-52958 Référence CVE CVE-2026-52961 https://www.cve.org/CVERecord?id=CVE-2026-52961 Référence CVE CVE-2026-52962 https://www.cve.org/CVERecord?id=CVE-2026-52962 Référence CVE CVE-2026-52975 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-52927 Référence CVE CVE-2026-52928 https://www.cve.org/CVERecord?id=CVE-2026-52928 Référence CVE CVE-2026-52931 https://www.cve.org/CVERecord?id=CVE-2026-52931 Référence CVE CVE-2026-52932 https://www.cve.org/CVERecord?id=CVE-2026-52932 Référence CVE CVE-2026-52933 https://www.cve.org/CVERecord?id=CVE-2026-52933 Référence CVE CVE-2026-52934 https://www.cve.org/CVERecord?id=CVE-2026-52934 Référence CVE CVE-2026-52936 https://www.cve.org/CVERecord?id=CVE-2026-52936 Référence CVE CVE-2026-52937 https://www.cve.org/CVERecord?id=CVE-2026-52937 Référence CVE CVE-2026-52941 https://www.cve.org/CVERecord?id=CVE-2026-52941 Référence CVE CVE-2026-52943 https://www.cve.org/CVERecord?id=CVE-2026-52943 Référence CVE CVE-2026-52944 https://www.cve.org/CVERecord?id=CVE-2026-52944 Référence CVE CVE-2026-52949 https://www.cve.org/CVERecord?id=CVE-2026-52949 Référence CVE CVE-2026-52950 https://www.cve.org/CVERecord?id=CVE-2026-52950 Référence CVE CVE-2026-52951 https://www.cve.org/CVERecord?id=CVE-2026-52951 Référence CVE CVE-2026-52952 https://www.cve.org/CVERecord?id=CVE-2026-52952 Référence CVE CVE-2026-52953 https://www.cve.org/CVERecord?id=CVE-2026-52953 Référence CVE CVE-2026-52954 https://www.cve.org/CVERecord?id=CVE-2026-52954 Référence CVE CVE-2026-52955 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-52918 Référence CVE CVE-2026-52919 https://www.cve.org/CVERecord?id=CVE-2026-52919 Référence CVE CVE-2026-52922 https://www.cve.org/CVERecord?id=CVE-2026-52922 Référence CVE CVE-2026-52923 https://www.cve.org/CVERecord?id=CVE-2026-52923 Référence CVE CVE-2026-52924 https://www.cve.org/CVERecord?id=CVE-2026-52924 Référence CVE CVE-2026-52926 https://www.cve.org/CVERecord?id=CVE-2026-52926 Référence CVE CVE-2026-52931 https://www.cve.org/CVERecord?id=CVE-2026-52931 Référence CVE CVE-2026-52933 https://www.cve.org/CVERecord?id=CVE-2026-52933 Référence CVE CVE-2026-52936 https://www.cve.org/CVERecord?id=CVE-2026-52936 Référence CVE CVE-2026-52943 https://www.cve.org/CVERecord?id=CVE-2026-52943 Référence CVE CVE-2026-52948 https://www.cve.org/CVERecord?id=CVE-2026-52948 Référence CVE CVE-2026-52951 https://www.cve.org/CVERecord?id=CVE-2026-52951 Référence CVE CVE-2026-52953 https://www.cve.org/CVERecord?id=CVE-2026-52953 Référence CVE CVE-2026-52954 https://www.cve.org/CVERecord?id=CVE-2026-52954 Référence CVE CVE-2026-52955 https://www.cve.org/CVERecord?id=CVE-2026-52955 Référence CVE CVE-2026-52956 https://www.cve.org/CVERecord?id=CVE-2026-52956 Référence CVE CVE-2026-52957 https://www.cve.org/CVERecord?id=CVE-2026-52957 Référence CVE CVE-2026-52958 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-52927 Référence CVE CVE-2026-52928 https://www.cve.org/CVERecord?id=CVE-2026-52928 Référence CVE CVE-2026-52931 https://www.cve.org/CVERecord?id=CVE-2026-52931 Référence CVE CVE-2026-52932 https://www.cve.org/CVERecord?id=CVE-2026-52932 Référence CVE CVE-2026-52933 https://www.cve.org/CVERecord?id=CVE-2026-52933 Référence CVE CVE-2026-52934 https://www.cve.org/CVERecord?id=CVE-2026-52934 Référence CVE CVE-2026-52936 https://www.cve.org/CVERecord?id=CVE-2026-52936 Référence CVE CVE-2026-52937 https://www.cve.org/CVERecord?id=CVE-2026-52937 Référence CVE CVE-2026-52941 https://www.cve.org/CVERecord?id=CVE-2026-52941 Référence CVE CVE-2026-52943 https://www.cve.org/CVERecord?id=CVE-2026-52943 Référence CVE CVE-2026-52944 https://www.cve.org/CVERecord?id=CVE-2026-52944 Référence CVE CVE-2026-52949 https://www.cve.org/CVERecord?id=CVE-2026-52949 Référence CVE CVE-2026-52950 https://www.cve.org/CVERecord?id=CVE-2026-52950 Référence CVE CVE-2026-52951 https://www.cve.org/CVERecord?id=CVE-2026-52951 Référence CVE CVE-2026-52952 https://www.cve.org/CVERecord?id=CVE-2026-52952 Référence CVE CVE-2026-52953 https://www.cve.org/CVERecord?id=CVE-2026-52953 Référence CVE CVE-2026-52954 https://www.cve.org/CVERecord?id=CVE-2026-52954 Référence CVE CVE-2026-52955 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-46319 Référence CVE CVE-2026-46320 https://www.cve.org/CVERecord?id=CVE-2026-46320 Référence CVE CVE-2026-46328 https://www.cve.org/CVERecord?id=CVE-2026-46328 Référence CVE CVE-2026-46330 https://www.cve.org/CVERecord?id=CVE-2026-46330 Référence CVE CVE-2026-46331 https://www.cve.org/CVERecord?id=CVE-2026-46331 Référence CVE CVE-2026-52909 https://www.cve.org/CVERecord?id=CVE-2026-52909 Référence CVE CVE-2026-52918 https://www.cve.org/CVERecord?id=CVE-2026-52918 Référence CVE CVE-2026-52923 https://www.cve.org/CVERecord?id=CVE-2026-52923 Référence CVE CVE-2026-52924 https://www.cve.org/CVERecord?id=CVE-2026-52924 Référence CVE CVE-2026-52943 https://www.cve.org/CVERecord?id=CVE-2026-52943 Référence CVE CVE-2026-52954 https://www.cve.org/CVERecord?id=CVE-2026-52954 Référence CVE CVE-2026-52955 https://www.cve.org/CVERecord?id=CVE-2026-52955 Référence CVE CVE-2026-52957 https://www.cve.org/CVERecord?id=CVE-2026-52957 Référence CVE CVE-2026-52962 https://www.cve.org/CVERecord?id=CVE-2026-52962 Référence CVE CVE-2026-52969 https://www.cve.org/CVERecord?id=CVE-2026-52969 Référence CVE CVE-2026-52972 https://www.cve.org/CVERecord?id=CVE-2026-52972 Référence CVE CVE-2026-52993 https://www.cve.org/CVERecord?id=CVE-2026-52993 Référence CVE CVE-2026-53016 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-46323 Référence CVE CVE-2026-46328 https://www.cve.org/CVERecord?id=CVE-2026-46328 Référence CVE CVE-2026-46330 https://www.cve.org/CVERecord?id=CVE-2026-46330 Référence CVE CVE-2026-46331 https://www.cve.org/CVERecord?id=CVE-2026-46331 Référence CVE CVE-2026-46333 https://www.cve.org/CVERecord?id=CVE-2026-46333 Référence CVE CVE-2026-52908 https://www.cve.org/CVERecord?id=CVE-2026-52908 Référence CVE CVE-2026-52909 https://www.cve.org/CVERecord?id=CVE-2026-52909 Référence CVE CVE-2026-52918 https://www.cve.org/CVERecord?id=CVE-2026-52918 Référence CVE CVE-2026-52923 https://www.cve.org/CVERecord?id=CVE-2026-52923 Référence CVE CVE-2026-52943 https://www.cve.org/CVERecord?id=CVE-2026-52943 Référence CVE CVE-2026-52954 https://www.cve.org/CVERecord?id=CVE-2026-52954 Référence CVE CVE-2026-52957 https://www.cve.org/CVERecord?id=CVE-2026-52957 Référence CVE CVE-2026-52962 https://www.cve.org/CVERecord?id=CVE-2026-52962 Référence CVE CVE-2026-52969 https://www.cve.org/CVERecord?id=CVE-2026-52969 Référence CVE CVE-2026-52972 https://www.cve.org/CVERecord?id=CVE-2026-52972 Référence CVE CVE-2026-53016 https://www.cve.org/CVERecord?id=CVE-2026-53016 Référence CVE CVE-2026-53040 https://www.cve.org/CVERecord?id=CVE-2026-53040 Référence CVE CVE-2026-53041 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-52929 Référence CVE CVE-2026-52930 https://www.cve.org/CVERecord?id=CVE-2026-52930 Référence CVE CVE-2026-52931 https://www.cve.org/CVERecord?id=CVE-2026-52931 Référence CVE CVE-2026-52933 https://www.cve.org/CVERecord?id=CVE-2026-52933 Référence CVE CVE-2026-52934 https://www.cve.org/CVERecord?id=CVE-2026-52934 Référence CVE CVE-2026-52935 https://www.cve.org/CVERecord?id=CVE-2026-52935 Référence CVE CVE-2026-52939 https://www.cve.org/CVERecord?id=CVE-2026-52939 Référence CVE CVE-2026-52941 https://www.cve.org/CVERecord?id=CVE-2026-52941 Référence CVE CVE-2026-52942 https://www.cve.org/CVERecord?id=CVE-2026-52942 Référence CVE CVE-2026-52943 https://www.cve.org/CVERecord?id=CVE-2026-52943 Référence CVE CVE-2026-52946 https://www.cve.org/CVERecord?id=CVE-2026-52946 Référence CVE CVE-2026-52947 https://www.cve.org/CVERecord?id=CVE-2026-52947 Référence CVE CVE-2026-52948 https://www.cve.org/CVERecord?id=CVE-2026-52948 Référence CVE CVE-2026-52954 https://www.cve.org/CVERecord?id=CVE-2026-52954 Référence CVE CVE-2026-52955 https://www.cve.org/CVERecord?id=CVE-2026-52955 Référence CVE CVE-2026-52957 https://www.cve.org/CVERecord?id=CVE-2026-52957 Référence CVE CVE-2026-52958 https://www.cve.org/CVERecord?id=CVE-2026-52958 Référence CVE CVE-2026-52962 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0812Multiples vulnérabilités dans Microsoft Azure Linux

ulletin de sécurité Microsoft CVE-2026-52922 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-52923 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-52924 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-52926 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-52927 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-52930 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-52931 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-52934 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-52941 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-52942 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-52943 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-52947 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53080 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53133 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53135 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53143 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53146 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53147 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53148 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53149 du 27 juin 2026 Bulletin de sécurité Microsoft CVE-2026-53150 du 27 juin 2026 Bulletin de s

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-023065LinuxのLinux Kernelにおける複数の脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました。net: skbuff: pskb_carveヘルパー内のゼロコピー参照の欠落を修正しました。pskb_carve_inside_header()とpskb_carve_inside_nonlinear()は共に、古いskb_shared_infoヘッダーをmemcpy()経由で新しいバッファにコピーしており、これにはMSG_ZEROCOPYスキューで使われるdestructor_argポインタ（uarg）が含まれています。どちらの関数も新しいshinfoに対してnet_zcopy_get()を呼び出していなかったため、適切に管理されないホルダーが作成されていました。destructor_argが設定されたskb_shared_infoは解放時にskb_zcopy_clear()を1回呼び出しますが、新しいコピーに対して対応するnet_zcopy_get()が呼ばれていません。複数回の呼び出しによりuarg-＞refcntが早期にゼロとなり、TXスキューが実際にdestructor_argポインタを保持しているにもかかわらず、ubuf_info_msgzcが解放されてしまいます。KASANは解放済みのubuf_info_msgzcに対するuse-after-freeを報告しました。具体的には以下の通りです。BUG: KASAN: slab-use-after-free in skb_release_data+0x77b/0x810 タスクpoc/220によるaddr ffff88801574d3e8の8バイト読み取り コールトレース: skb_release_data+0x77b/0x810 kfree_skb_list_reason+0x13e/0x610 skb_release_data+0x4cd/0x810 sk_skb_reason_drop+0xf3/0x340 skb_queue_purge_reason+0x282/0x440 rds_tcp_inc_free+0x1e/0x30 rds_recvmsg+0x354/0x1780 __sys_recvmsg+0xdf/0x180 タスク219による割り当て: msg_zerocopy_realloc+0x157/0x7b0 tcp_sendmsg_locked+0x2892/0x3ba0 タスク219によって解放: ip_recv_error+0x74a/0xb10 tcp_recvmsg+0x475/0x530 遅延アクセス時に使用されたskbは、refcount増加なしにpskb_carve_inside_nonlinear()がコピーしたshinfo-＞destructor_arg経由で同じuargを参照していました。これが信頼性高く悪用可能であることが検証されており、動作する概念実証によってデフォルトカーネル設定の非特権ローカルユーザーから完全なroot権限昇格が達成されています。修正は、同様のmemcpyやクローン構造を持つpskb_expand_head()のパターンに従っています。pskb_carve_inside_header()では、skb_orphan_frags()成功後にnet_zcopy_get()を配置し、孤立エラー経路のクリーンアップを不要にしました。pskb_carve_inside_nonlinear()では、全失敗ポイントの後かつskb_release_data()直前にnet_zcopy_get()を配置し、エラー経路のクリーンアップを不要にしています。これによりpskb_expand_head()に近づき、対応するnet_zcopy_put()を必要としません。

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: < 4.7, 5.10.259 ≤ 5.10.*, 5.15.210 ≤ 5.15.*, 6.1.176 ≤ 6.1.*, 6.6.143 ≤ 6.6.*, 6.12.93 ≤ 6.12.*, 6.18.35 ≤ 6.18.*, 7.0.12 ≤ 7.0.*, 7.1 ≤ *
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 24 Jun 2026 · Last source change 8 Sept 2026, 08:49 UTC · CWE-911 · Improper Update of Reference Count

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-2026-38732
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceOther authority
NVD statusNVD modified after enrichment

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

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    6fa01ccd883021105e9f8af7d04b9f156fa3494a < 8dbed691e43a50903658130bde0fcb5abc425b37; 6fa01ccd883021105e9f8af7d04b9f156fa3494a < 9b40bdc2a3298225dffab8158208a0d8c6300578; 6fa01ccd883021105e9f8af7d04b9f156fa3494a < fd470f0a97b8e9a125f520265d2f3b088ffb5b8a; 6fa01ccd883021105e9f8af7d04b9f156fa3494a < ceafb893b12f23331dcc5ff9587e643c3a40ee9f; 6fa01ccd883021105e9f8af7d04b9f156fa3494a < 2e0e74c59b2761a414d9f48d7bee1e45220b2427; 6fa01ccd883021105e9f8af7d04b9f156fa3494a < 96a4713ae041cc85e712bac682cd2e644004d6c6; 6fa01ccd883021105e9f8af7d04b9f156fa3494a < 474d6c771d798bca84f0a140b611e36743511e18; 6fa01ccd883021105e9f8af7d04b9f156fa3494a < 98d0912e9f841e5529a5b89a972805f34cb1c69d · Fixed: < 4.7; 5.10.259 ≤ 5.10.*; 5.15.210 ≤ 5.15.*; 6.1.176 ≤ 6.1.*; 6.6.143 ≤ 6.6.*; 6.12.93 ≤ 6.12.*; 6.18.35 ≤ 6.18.*; 7.0.12 ≤ 7.0.*
    After
    Linux: 6fa01ccd883021105e9f8af7d04b9f156fa3494a < 8dbed691e43a50903658130bde0fcb5abc425b37, 6fa01ccd883021105e9f8af7d04b9f156fa3494a < 9b40bdc2a3298225dffab8158208a0d8c6300578, 6fa01ccd883021105e9f8af7d04b9f156fa3494a < fd470f0a97b8e9a125f520265d2f3b088ffb5b8a, 6fa01ccd883021105e9f8af7d04b9f156fa3494a < ceafb893b12f23331dcc5ff9587e643c3a40ee9f, 6fa01ccd883021105e9f8af7d04b9f156fa3494a < 2e0e74c59b2761a414d9f48d7bee1e45220b2427, 6fa01ccd883021105e9f8af7d04b9f156fa3494a < 96a4713ae041cc85e712bac682cd2e644004d6c6, 6fa01ccd883021105e9f8af7d04b9f156fa3494a < 474d6c771d798bca84f0a140b611e36743511e18, 6fa01ccd883021105e9f8af7d04b9f156fa3494a < 98d0912e9f841e5529a5b89a972805f34cb1c69d, 4.7 · Fixed: Linux: < 4.7, 5.10.259 ≤ 5.10.*, 5.15.210 ≤ 5.15.*, 6.1.176 ≤ 6.1.*, 6.6.143 ≤ 6.6.*, 6.12.93 ≤ 6.12.*, 6.18.35 ≤ 6.18.*, 7.0.12 ≤ 7.0.*, 7.1 ≤ *
    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-2026-38732↗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-2026-52943 · cve.blacktree.nl