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

net: skbuff: propagate shared-frag marker through frag-transfer helpers

Linux · Linux

8.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 20 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 24 Aug 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 1.99% 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 20 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.90-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.174-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.9-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.9-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-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.

1 current
CVE-2026-43503 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: net: skbuff: propagate shared-frag marker through frag-transfer helpers
2,576 fixed

The vendor explicitly identifies these products or versions as containing the fix.

  • kernel-0:6.12.0-211.8.el10nv.aarch64 as a component of NVIDIA for RHEL 10
  • kernel-0:6.12.0-211.8.el10nv.src as a component of NVIDIA for RHEL 10
  • kernel-0:6.12.0-231.12.el10nv.aarch64 as a component of NVIDIA for RHEL 10
  • kernel-0:6.12.0-231.12.el10nv.src as a component of NVIDIA for RHEL 10
  • kernel-64k-0:6.12.0-211.8.el10nv.aarch64 as a component of NVIDIA for RHEL 10
  • kernel-64k-0:6.12.0-231.12.el10nv.aarch64 as a component of NVIDIA for RHEL 10
  • kernel-64k-core-0:6.12.0-211.8.el10nv.aarch64 as a component of NVIDIA for RHEL 10
  • kernel-64k-core-0:6.12.0-231.12.el10nv.aarch64 as a component of NVIDIA for RHEL 10
  • kernel-64k-debug-0:6.12.0-211.8.el10nv.aarch64 as a component of NVIDIA for RHEL 10
  • kernel-64k-debug-0:6.12.0-231.12.el10nv.aarch64 as a component of NVIDIA for RHEL 10
  • kernel-64k-debug-core-0:6.12.0-211.8.el10nv.aarch64 as a component of NVIDIA for RHEL 10
  • kernel-64k-debug-core-0:6.12.0-231.12.el10nv.aarch64 as a component of NVIDIA for RHEL 10
Summary
A flaw was found in the Linux kernel's networking (skbuff) component. When skb_try_coalesce() attaches paged fragments, it can lose the SKBFL_SHARED_FRAG marker. This can lead to the Encapsulating Security Payload (ESP) input decrypting data in place over page-cache backed fragments, potentially resulting in data corruption.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.
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-31536

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: net: skbuff: propagate shared-frag marker through frag-transfer helpers Two frag-transfer helpers (__pskb_copy_fclone() and skb_shift()) fail to propagate the SKBFL_SHARED_FRAG bit in skb_shinfo()->flags when moving frags from source to destination. __pskb_copy_fclone() defers the rest of the shinfo metadata to skb_copy_header() after copying frag descriptors, but that helper only carries over gso_{size,segs, type} and never touches skb_shinfo()->flags; skb_shift() moves frag descriptors directly and leaves flags untouched. As a result, the destination skb keeps a reference to the same externally-owned or page-cache-backed pages while reporting skb_has_shared_frag() as false. The mismatch is harmful in any in-place writer that uses skb_has_shared_frag() to decide whether shared pages must be detoured through skb_cow_data(). ESP input is one such writer (esp4.c, esp6.c), and a single nft 'dup to <local>' rule -- or any other nf_dup_ipv4() / xt_TEE caller -- is enough to land a pskb_copy()'d skb in esp_input() with the marker stripped, letting an unprivileged user write into the page cache of a root-owned read-only file via authencesn-ESN stray writes. Set SKBFL_SHARED_FRAG on the destination whenever frag descriptors were actually moved from the source. skb_copy() and skb_copy_expand() share skb_copy_header() too but linearize all paged data into freshly allocated head storage and emerge with nr_frags == 0, so skb_has_shared_frag() returns false on its own; they need no change. The same omission exists in skb_gro_receive() and skb_gro_receive_list(). The former moves the incoming skb's frag descriptors into the accumulator's last sub-skb via two paths (a direct frag-move loop and the head_frag + memcpy path); the latter chains the incoming skb whole onto p's frag_list. Downstream skb_segment() reads only skb_shinfo(p)->flags, and skb_segment_list() reuses each sub-skb's shinfo as the nskb -- both p and lp must carry the marker. The same omission also exists in tcp_clone_payload(), which builds an MTU probe skb by moving frag descriptors from skbs on sk_write_queue into a freshly allocated nskb. The helper falls into the same family and warrants the same fix for consistency; no TCP TX-side in-place writer is currently known to reach a user page through this gap, but a future consumer depending on the marker would regress silently. The same omission exists in skb_segment(): the per-iteration flag merge takes only head_skb's flag, and the inner switch that rebinds frag_skb to list_skb on head_skb-frags exhaustion does not fold the new frag_skb's flag into nskb. Fold frag_skb's flag at both sites so segments drawing frags from frag_list members carry the marker.

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
8.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 20 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: propagate shared-frag marker through frag-transfer helpers Two frag-transfer helpers (__pskb_copy_fclone() and skb_shift()) fail to propagate the SKBFL_SHARED_FRAG bit in skb_shinfo()->flags when moving frags from source to destination. __pskb_copy_fclone() defers the rest of the shinfo metadata to skb_copy_header() after copying frag descriptors, but that helper only carries over gso_{size,segs, type} and never touches skb_shinfo()->flags; skb_shift() moves frag descriptors directly and leaves flags untouched. As a result, the destination skb keeps a reference to the same externally-owned or page-cache-backed pages while reporting skb_has_shared_frag() as false. The mismatch is harmful in any in-place writer that uses skb_has_shared_frag() to decide whether shared pages must be detoured through skb_cow_data(). ESP input is one such writer (esp4.c, esp6.c), and a single nft 'dup to <local>' rule -- or any other nf_dup_ipv4() / xt_TEE caller -- is enough to land a pskb_copy()'d skb in esp_input() with the marker stripped, letting an unprivileged user write into the page cache of a root-owned read-only file via authencesn-ESN stray writes. Set SKBFL_SHARED_FRAG on the destination whenever frag descriptors were actually moved from the source. skb_copy() and skb_copy_expand() share skb_copy_header() too but linearize all paged data into freshly allocated head storage and emerge with nr_frags == 0, so skb_has_shared_frag() returns false on its own; they need no change. The same omission exists in skb_gro_receive() and skb_gro_receive_list(). The former moves the incoming skb's frag descriptors into the accumulator's last sub-skb via two paths (a direct frag-move loop and the head_frag + memcpy path); the latter chains the incoming skb whole onto p's frag_list. Downstream skb_segment() reads only skb_shinfo(p)->flags, and skb_segment_list() reuses each sub-skb's shinfo as the nskb -- both p and lp must carry the marker. The same omission also exists in tcp_clone_payload(), which builds an MTU probe skb by moving frag descriptors from skbs on sk_write_queue into a freshly allocated nskb. The helper falls into the same family and warrants the same fix for consistency; no TCP TX-side in-place writer is currently known to reach a user page through this gap, but a future consumer depending on the marker would regress silently. The same omission exists in skb_segment(): the per-iteration flag merge takes only head_skb's flag, and the inner switch that rebinds frag_skb to list_skb on head_skb-frags exhaustion does not fold the new frag_skb's flag into nskb. Fold frag_skb's flag at both sites so segments drawing frags from frag_list members carry the marker.

What

In the Linux kernel, the following vulnerability has been resolved: net: skbuff: propagate shared-frag marker through frag-transfer helpers Two frag-transfer helpers (__pskb_copy_fclone() and skb_shift()) fail to propagate the SKBFL_SHARED_FRAG bit in skb_shinfo()->flags when moving frags from source to destination. __pskb_copy_fclone() defers the rest of the shinfo metadata to skb_copy_header() after copying frag descriptors, but that helper only carries over gso_{size,segs, type} and never touches skb_shinfo()->flags; skb_shift() moves frag descriptors directly and leaves flags untouched. As a result, the destination skb keeps a reference to the same externally-owned or page-cache-backed pages while reporting skb_has_shared_frag() as false. The mismatch is harmful in any in-place writer that uses skb_has_shared_frag() to decide whether shared pages must be detoured through skb_cow_data(). ESP input is one such writer (esp4.c, esp6.c), and a single nft 'dup to <local>' rule -- or any other nf_dup_ipv4() / xt_TEE caller -- is enough to land a pskb_copy()'d skb in esp_input() with the marker stripped, letting an unprivileged user write into the page cache of a root-owned read-only file via authencesn-ESN stray writes. Set SKBFL_SHARED_FRAG on the destination whenever frag descriptors were actually moved from the source. skb_copy() and skb_copy_expand() share skb_copy_header() too but linearize all paged data into freshly allocated head storage and emerge with nr_frags == 0, so skb_has_shared_frag() returns false on its own; they need no change. The same omission exists in skb_gro_receive() and skb_gro_receive_list(). The former moves the incoming skb's frag descriptors into the accumulator's last sub-skb via two paths (a direct frag-move loop and the head_frag + memcpy path); the latter chains the incoming skb whole onto p's frag_list. Downstream skb_segment() reads only skb_shinfo(p)->flags, and skb_segment_list() reuses each sub-skb's shinfo as the nskb -- both p and lp must carry the marker. The same omission also exists in tcp_clone_payload(), which builds an MTU probe skb by moving frag descriptors from skbs on sk_write_queue into a freshly allocated nskb. The helper falls into the same family and warrants the same fix for consistency; no TCP TX-side in-place writer is currently known to reach a user page through this gap, but a future consumer depending on the marker would regress silently. The same omission exists in skb_segment(): the per-iteration flag merge takes only head_skb's flag, and the inner switch that rebinds frag_skb to list_skb on head_skb-frags exhaustion does not fold the new frag_skb's flag into nskb. Fold frag_skb's flag at both sites so segments drawing frags from frag_list members carry the marker.

Why

The product does not maintain or incorrectly maintains control over a resource throughout its lifetime of creation, use, and release.

How

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

What

In the Linux kernel, the following vulnerability has been resolved: net: skbuff: propagate shared-frag marker through frag-transfer helpers Two frag-transfer helpers (__pskb_copy_fclone() and skb_shift()) fail to propagate the SKBFL_SHARED_FRAG bit in skb_shinfo()->flags when moving frags from source to destination. __pskb_copy_fclone() defers the rest of the shinfo metadata to skb_copy_header() after copying frag descriptors, but that helper only carries over gso_{size,segs, type} and never touches skb_shinfo()->flags; skb_shift() moves frag descriptors directly and leaves flags untouched. As a result, the destination skb keeps a reference to the same externally-owned or page-cache-backed pages while reporting skb_has_shared_frag() as false. The mismatch is harmful in any in-place writer that uses skb_has_shared_frag() to decide whether shared pages must be detoured through skb_cow_data(). ESP input is one such writer (esp4.c, esp6.c), and a single nft 'dup to <local>' rule -- or any other nf_dup_ipv4() / xt_TEE caller -- is enough to land a pskb_copy()'d skb in esp_input() with the marker stripped, letting an unprivileged user write into the page cache of a root-owned read-only file via authencesn-ESN stray writes. Set SKBFL_SHARED_FRAG on the destination whenever frag descriptors were actually moved from the source. skb_copy() and skb_copy_expand() share skb_copy_header() too but linearize all paged data into freshly allocated head storage and emerge with nr_frags == 0, so skb_has_shared_frag() returns false on its own; they need no change. The same omission exists in skb_gro_receive() and skb_gro_receive_list(). The former moves the incoming skb's frag descriptors into the accumulator's last sub-skb via two paths (a direct frag-move loop and the head_frag + memcpy path); the latter chains the incoming skb whole onto p's frag_list. Downstream skb_segment() reads only skb_shinfo(p)->flags, and skb_segment_list() reuses each sub-skb's shinfo as the nskb -- both p and lp must carry the marker. The same omission also exists in tcp_clone_payload(), which builds an MTU probe skb by moving frag descriptors from skbs on sk_write_queue into a freshly allocated nskb. The helper falls into the same family and warrants the same fix for consistency; no TCP TX-side in-place writer is currently known to reach a user page through this gap, but a future consumer depending on the marker would regress silently. The same omission exists in skb_segment(): the per-iteration flag merge takes only head_skb's flag, and the inner switch that rebinds frag_skb to list_skb on head_skb-frags exhaustion does not fold the new frag_skb's flag into nskb. Fold frag_skb's flag at both sites so segments drawing frags from frag_list members carry the marker.

Why

The product does not maintain or incorrectly maintains control over a resource throughout its lifetime of creation, use, and release.

How

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

02

Exploit reality and attack path

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

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

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

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

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

Likely attack path
local access → Improper Control of a Resource Through its Lifetime → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Changed: exploitation can affect a different security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-664 ↗

CWE-664: Improper Control of a Resource Through its Lifetime. The product does not maintain or incorrectly maintains control over a resource throughout its lifetime of creation, use, and release.

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:C/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.SChangedScope: The attack can affect a component governed by a different security authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
CWE-664
A

Official authority intelligence

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

ENISA EUVD · EUVD-2026-31536Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: net: skbuff: propagate shared-frag marker through frag-transfer helpers Two frag-transfer helpers (__pskb_copy_fclone() and skb_shift()) fail to propagate the SKBFL_SHARED_FRAG bit in skb_shinfo()->flags when moving frags from source to destination. __pskb_copy_fclone() defers the rest of the shinfo metadata to skb_copy_header() after copying frag descriptors, but that helper only carries over gso_{size,segs, type} and never touches skb_shinfo()->flags; skb_shift() moves frag descriptors directly and leaves flags untouched. As a result, the destination skb keeps a reference to the same externally-owned or page-cache-backed pages while reporting skb_has_shared_frag() as false. The mismatch is harmful in any in-place writer that uses skb_has_shared_frag() to decide whether shared pages must be detoured through skb_cow_data(). ESP input is one such writer (esp4.c, esp6.c), and a single nft 'dup to <local>' rule -- or any other nf_dup_ipv4() / xt_TEE caller -- is enough to land a pskb_copy()'d skb in esp_input() with the marker stripped, letting an unprivileged user write into the page cache of a root-owned read-only file via authencesn-ESN stray writes. Set SKBFL_SHARED_FRAG on the destination whenever frag descriptors were actually moved from the source. skb_copy() and skb_copy_expand() share skb_copy_header() too but linearize all paged data into freshly allocated head storage and emerge with nr_frags == 0, so skb_has_shared_frag() returns false on its own; they need no change. The same omission exists in skb_gro_receive() and skb_gro_receive_list(). The former moves the incoming skb's frag descriptors into the accumulator's last sub-skb via two paths (a direct frag-move loop and the head_frag + memcpy path); the latter chains the incoming skb whole onto p's frag_list. Downstream skb_segment() reads only skb_shinfo(p)->flags, and skb_segment_list() reuses each sub-skb's shinfo as the nskb -- both p and lp must carry the marker. The same omission also exists in tcp_clone_payload(), which builds an MTU probe skb by moving frag descriptors from skbs on sk_write_queue into a freshly allocated nskb. The helper falls into the same family and warrants the same fix for consistency; no TCP TX-side in-place writer is currently known to reach a user page through this gap, but a future consumer depending on the marker would regress silently. The same omission exists in skb_segment(): the per-iteration flag merge takes only head_skb's flag, and the inner switch that rebinds frag_skb to list_skb on head_skb-frags exhaustion does not fold the new frag_skb's flag into nskb. Fold frag_skb's flag at both sites so segments drawing frags from frag_list members carry the marker.

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

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

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

d?id=CVE-2026-43284 Référence CVE CVE-2026-43378 https://www.cve.org/CVERecord?id=CVE-2026-43378 Référence CVE CVE-2026-43379 https://www.cve.org/CVERecord?id=CVE-2026-43379 Référence CVE CVE-2026-43383 https://www.cve.org/CVERecord?id=CVE-2026-43383 Référence CVE CVE-2026-43407 https://www.cve.org/CVERecord?id=CVE-2026-43407 Référence CVE CVE-2026-43414 https://www.cve.org/CVERecord?id=CVE-2026-43414 Référence CVE CVE-2026-43465 https://www.cve.org/CVERecord?id=CVE-2026-43465 Référence CVE CVE-2026-43493 https://www.cve.org/CVERecord?id=CVE-2026-43493 Référence CVE CVE-2026-43499 https://www.cve.org/CVERecord?id=CVE-2026-43499 Référence CVE CVE-2026-43503 https://www.cve.org/CVERecord?id=CVE-2026-43503 Référence CVE CVE-2026-45988 https://www.cve.org/CVERecord?id=CVE-2026-45988 Référence CVE CVE-2026-46043 https://www.cve.org/CVERecord?id=CVE-2026-46043 Référence CVE CVE-2026-46113 https://www.cve.org/CVERecord?id=CVE-2026-46113 Référence CVE CVE-2026-46119 https://www.cve.org/CVERecord?id=CVE-2026-46119 Référence CVE CVE-2026-46137 https://www.cve.org/CVERecord?id=CVE-2026-46137 Référence CVE CVE-2026-46242 https://www.cve.org/CVERecord?id=CVE-2026-46242 Référence CVE CVE-2026-46243 https://www.cve.org/CVERecord?id=CVE-2026-46243 Référence CVE CVE-2026-46266 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-43494 Référence CVE CVE-2026-43495 https://www.cve.org/CVERecord?id=CVE-2026-43495 Référence CVE CVE-2026-43496 https://www.cve.org/CVERecord?id=CVE-2026-43496 Référence CVE CVE-2026-43497 https://www.cve.org/CVERecord?id=CVE-2026-43497 Référence CVE CVE-2026-43498 https://www.cve.org/CVERecord?id=CVE-2026-43498 Référence CVE CVE-2026-43499 https://www.cve.org/CVERecord?id=CVE-2026-43499 Référence CVE CVE-2026-43500 https://www.cve.org/CVERecord?id=CVE-2026-43500 Référence CVE CVE-2026-43501 https://www.cve.org/CVERecord?id=CVE-2026-43501 Référence CVE CVE-2026-43502 https://www.cve.org/CVERecord?id=CVE-2026-43502 Référence CVE CVE-2026-43503 https://www.cve.org/CVERecord?id=CVE-2026-43503 Référence CVE CVE-2026-45834 https://www.cve.org/CVERecord?id=CVE-2026-45834 Référence CVE CVE-2026-45835 https://www.cve.org/CVERecord?id=CVE-2026-45835 Référence CVE CVE-2026-45836 https://www.cve.org/CVERecord?id=CVE-2026-45836 Référence CVE CVE-2026-45837 https://www.cve.org/CVERecord?id=CVE-2026-45837 Référence CVE CVE-2026-45838 https://www.cve.org/CVERecord?id=CVE-2026-45838 Référence CVE CVE-2026-45839 https://www.cve.org/CVERecord?id=CVE-2026-45839 Référence CVE CVE-2026-45840 https://www.cve.org/CVERecord?id=CVE-2026-45840 Référence CVE CVE-2026-45841 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-43494 Référence CVE CVE-2026-43495 https://www.cve.org/CVERecord?id=CVE-2026-43495 Référence CVE CVE-2026-43496 https://www.cve.org/CVERecord?id=CVE-2026-43496 Référence CVE CVE-2026-43497 https://www.cve.org/CVERecord?id=CVE-2026-43497 Référence CVE CVE-2026-43498 https://www.cve.org/CVERecord?id=CVE-2026-43498 Référence CVE CVE-2026-43499 https://www.cve.org/CVERecord?id=CVE-2026-43499 Référence CVE CVE-2026-43500 https://www.cve.org/CVERecord?id=CVE-2026-43500 Référence CVE CVE-2026-43501 https://www.cve.org/CVERecord?id=CVE-2026-43501 Référence CVE CVE-2026-43502 https://www.cve.org/CVERecord?id=CVE-2026-43502 Référence CVE CVE-2026-43503 https://www.cve.org/CVERecord?id=CVE-2026-43503 Référence CVE CVE-2026-45834 https://www.cve.org/CVERecord?id=CVE-2026-45834 Référence CVE CVE-2026-45835 https://www.cve.org/CVERecord?id=CVE-2026-45835 Référence CVE CVE-2026-45836 https://www.cve.org/CVERecord?id=CVE-2026-45836 Référence CVE CVE-2026-45837 https://www.cve.org/CVERecord?id=CVE-2026-45837 Référence CVE CVE-2026-45838 https://www.cve.org/CVERecord?id=CVE-2026-45838 Référence CVE CVE-2026-45839 https://www.cve.org/CVERecord?id=CVE-2026-45839 Référence CVE CVE-2026-45840 https://www.cve.org/CVERecord?id=CVE-2026-45840 Référence CVE CVE-2026-45841 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-43378 Référence CVE CVE-2026-43383 https://www.cve.org/CVERecord?id=CVE-2026-43383 Référence CVE CVE-2026-43384 https://www.cve.org/CVERecord?id=CVE-2026-43384 Référence CVE CVE-2026-43402 https://www.cve.org/CVERecord?id=CVE-2026-43402 Référence CVE CVE-2026-43406 https://www.cve.org/CVERecord?id=CVE-2026-43406 Référence CVE CVE-2026-43407 https://www.cve.org/CVERecord?id=CVE-2026-43407 Référence CVE CVE-2026-43414 https://www.cve.org/CVERecord?id=CVE-2026-43414 Référence CVE CVE-2026-43493 https://www.cve.org/CVERecord?id=CVE-2026-43493 Référence CVE CVE-2026-43501 https://www.cve.org/CVERecord?id=CVE-2026-43501 Référence CVE CVE-2026-43503 https://www.cve.org/CVERecord?id=CVE-2026-43503 Référence CVE CVE-2026-45898 https://www.cve.org/CVERecord?id=CVE-2026-45898 Référence CVE CVE-2026-45988 https://www.cve.org/CVERecord?id=CVE-2026-45988 Référence CVE CVE-2026-46039 https://www.cve.org/CVERecord?id=CVE-2026-46039 Référence CVE CVE-2026-46043 https://www.cve.org/CVERecord?id=CVE-2026-46043 Référence CVE CVE-2026-46115 https://www.cve.org/CVERecord?id=CVE-2026-46115 Référence CVE CVE-2026-46119 https://www.cve.org/CVERecord?id=CVE-2026-46119 Référence CVE CVE-2026-46135 https://www.cve.org/CVERecord?id=CVE-2026-46135 Référence CVE CVE-2026-46185 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-43469 Référence CVE CVE-2026-43470 https://www.cve.org/CVERecord?id=CVE-2026-43470 Référence CVE CVE-2026-43472 https://www.cve.org/CVERecord?id=CVE-2026-43472 Référence CVE CVE-2026-43483 https://www.cve.org/CVERecord?id=CVE-2026-43483 Référence CVE CVE-2026-43491 https://www.cve.org/CVERecord?id=CVE-2026-43491 Référence CVE CVE-2026-43492 https://www.cve.org/CVERecord?id=CVE-2026-43492 Référence CVE CVE-2026-43499 https://www.cve.org/CVERecord?id=CVE-2026-43499 Référence CVE CVE-2026-43501 https://www.cve.org/CVERecord?id=CVE-2026-43501 Référence CVE CVE-2026-43502 https://www.cve.org/CVERecord?id=CVE-2026-43502 Référence CVE CVE-2026-43503 https://www.cve.org/CVERecord?id=CVE-2026-43503 Référence CVE CVE-2026-45838 https://www.cve.org/CVERecord?id=CVE-2026-45838 Référence CVE CVE-2026-45840 https://www.cve.org/CVERecord?id=CVE-2026-45840 Référence CVE CVE-2026-45841 https://www.cve.org/CVERecord?id=CVE-2026-45841 Référence CVE CVE-2026-45842 https://www.cve.org/CVERecord?id=CVE-2026-45842 Référence CVE CVE-2026-45843 https://www.cve.org/CVERecord?id=CVE-2026-45843 Référence CVE CVE-2026-45846 https://www.cve.org/CVERecord?id=CVE-2026-45846 Référence CVE CVE-2026-45848 https://www.cve.org/CVERecord?id=CVE-2026-45848 Référence CVE CVE-2026-45852 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-43406 Référence CVE CVE-2026-43407 https://www.cve.org/CVERecord?id=CVE-2026-43407 Référence CVE CVE-2026-43414 https://www.cve.org/CVERecord?id=CVE-2026-43414 Référence CVE CVE-2026-43491 https://www.cve.org/CVERecord?id=CVE-2026-43491 Référence CVE CVE-2026-43493 https://www.cve.org/CVERecord?id=CVE-2026-43493 Référence CVE CVE-2026-43494 https://www.cve.org/CVERecord?id=CVE-2026-43494 Référence CVE CVE-2026-43499 https://www.cve.org/CVERecord?id=CVE-2026-43499 Référence CVE CVE-2026-43500 https://www.cve.org/CVERecord?id=CVE-2026-43500 Référence CVE CVE-2026-43501 https://www.cve.org/CVERecord?id=CVE-2026-43501 Référence CVE CVE-2026-43503 https://www.cve.org/CVERecord?id=CVE-2026-43503 Référence CVE CVE-2026-45847 https://www.cve.org/CVERecord?id=CVE-2026-45847 Référence CVE CVE-2026-45848 https://www.cve.org/CVERecord?id=CVE-2026-45848 Référence CVE CVE-2026-45849 https://www.cve.org/CVERecord?id=CVE-2026-45849 Référence CVE CVE-2026-45851 https://www.cve.org/CVERecord?id=CVE-2026-45851 Référence CVE CVE-2026-45852 https://www.cve.org/CVERecord?id=CVE-2026-45852 Référence CVE CVE-2026-45856 https://www.cve.org/CVERecord?id=CVE-2026-45856 Référence CVE CVE-2026-45857 https://www.cve.org/CVERecord?id=CVE-2026-45857 Référence CVE CVE-2026-45859 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-43413 Référence CVE CVE-2026-43414 https://www.cve.org/CVERecord?id=CVE-2026-43414 Référence CVE CVE-2026-43455 https://www.cve.org/CVERecord?id=CVE-2026-43455 Référence CVE CVE-2026-43469 https://www.cve.org/CVERecord?id=CVE-2026-43469 Référence CVE CVE-2026-43470 https://www.cve.org/CVERecord?id=CVE-2026-43470 Référence CVE CVE-2026-43483 https://www.cve.org/CVERecord?id=CVE-2026-43483 Référence CVE CVE-2026-43491 https://www.cve.org/CVERecord?id=CVE-2026-43491 Référence CVE CVE-2026-43499 https://www.cve.org/CVERecord?id=CVE-2026-43499 Référence CVE CVE-2026-43501 https://www.cve.org/CVERecord?id=CVE-2026-43501 Référence CVE CVE-2026-43503 https://www.cve.org/CVERecord?id=CVE-2026-43503 Référence CVE CVE-2026-45840 https://www.cve.org/CVERecord?id=CVE-2026-45840 Référence CVE CVE-2026-45841 https://www.cve.org/CVERecord?id=CVE-2026-45841 Référence CVE CVE-2026-45842 https://www.cve.org/CVERecord?id=CVE-2026-45842 Référence CVE CVE-2026-45843 https://www.cve.org/CVERecord?id=CVE-2026-45843 Référence CVE CVE-2026-45846 https://www.cve.org/CVERecord?id=CVE-2026-45846 Référence CVE CVE-2026-45852 https://www.cve.org/CVERecord?id=CVE-2026-45852 Référence CVE CVE-2026-45856 https://www.cve.org/CVERecord?id=CVE-2026-45856 Référence CVE CVE-2026-45862 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-43406 Référence CVE CVE-2026-43407 https://www.cve.org/CVERecord?id=CVE-2026-43407 Référence CVE CVE-2026-43414 https://www.cve.org/CVERecord?id=CVE-2026-43414 Référence CVE CVE-2026-43491 https://www.cve.org/CVERecord?id=CVE-2026-43491 Référence CVE CVE-2026-43493 https://www.cve.org/CVERecord?id=CVE-2026-43493 Référence CVE CVE-2026-43494 https://www.cve.org/CVERecord?id=CVE-2026-43494 Référence CVE CVE-2026-43499 https://www.cve.org/CVERecord?id=CVE-2026-43499 Référence CVE CVE-2026-43500 https://www.cve.org/CVERecord?id=CVE-2026-43500 Référence CVE CVE-2026-43501 https://www.cve.org/CVERecord?id=CVE-2026-43501 Référence CVE CVE-2026-43503 https://www.cve.org/CVERecord?id=CVE-2026-43503 Référence CVE CVE-2026-45847 https://www.cve.org/CVERecord?id=CVE-2026-45847 Référence CVE CVE-2026-45848 https://www.cve.org/CVERecord?id=CVE-2026-45848 Référence CVE CVE-2026-45849 https://www.cve.org/CVERecord?id=CVE-2026-45849 Référence CVE CVE-2026-45851 https://www.cve.org/CVERecord?id=CVE-2026-45851 Référence CVE CVE-2026-45852 https://www.cve.org/CVERecord?id=CVE-2026-45852 Référence CVE CVE-2026-45856 https://www.cve.org/CVERecord?id=CVE-2026-45856 Référence CVE CVE-2026-45857 https://www.cve.org/CVERecord?id=CVE-2026-45857 Référence CVE CVE-2026-45859 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-31431 Référence CVE CVE-2026-31504 https://www.cve.org/CVERecord?id=CVE-2026-31504 Référence CVE CVE-2026-31533 https://www.cve.org/CVERecord?id=CVE-2026-31533 Référence CVE CVE-2026-43033 https://www.cve.org/CVERecord?id=CVE-2026-43033 Référence CVE CVE-2026-43077 https://www.cve.org/CVERecord?id=CVE-2026-43077 Référence CVE CVE-2026-43078 https://www.cve.org/CVERecord?id=CVE-2026-43078 Référence CVE CVE-2026-43284 https://www.cve.org/CVERecord?id=CVE-2026-43284 Référence CVE CVE-2026-43494 https://www.cve.org/CVERecord?id=CVE-2026-43494 Référence CVE CVE-2026-43500 https://www.cve.org/CVERecord?id=CVE-2026-43500 Référence CVE CVE-2026-43503 https://www.cve.org/CVERecord?id=CVE-2026-43503 Référence CVE CVE-2026-45998 https://www.cve.org/CVERecord?id=CVE-2026-45998 Référence CVE CVE-2026-46000 https://www.cve.org/CVERecord?id=CVE-2026-46000 Référence CVE CVE-2026-46028 https://www.cve.org/CVERecord?id=CVE-2026-46028 Référence CVE CVE-2026-46300 https://www.cve.org/CVERecord?id=CVE-2026-46300 Référence CVE CVE-2026-46323 https://www.cve.org/CVERecord?id=CVE-2026-46323 Référence CVE CVE-2026-46333 https://www.cve.org/CVERecord?id=CVE-2026-46333 Référence CVE CVE-2026-47326 https://www.cve.org/CVERecord?id=CVE-2026-47326 Référence CVE CVE-2026-47327 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-43407 Référence CVE CVE-2026-43411 https://www.cve.org/CVERecord?id=CVE-2026-43411 Référence CVE CVE-2026-43413 https://www.cve.org/CVERecord?id=CVE-2026-43413 Référence CVE CVE-2026-43414 https://www.cve.org/CVERecord?id=CVE-2026-43414 Référence CVE CVE-2026-43455 https://www.cve.org/CVERecord?id=CVE-2026-43455 Référence CVE CVE-2026-43470 https://www.cve.org/CVERecord?id=CVE-2026-43470 Référence CVE CVE-2026-43483 https://www.cve.org/CVERecord?id=CVE-2026-43483 Référence CVE CVE-2026-43499 https://www.cve.org/CVERecord?id=CVE-2026-43499 Référence CVE CVE-2026-43501 https://www.cve.org/CVERecord?id=CVE-2026-43501 Référence CVE CVE-2026-43503 https://www.cve.org/CVERecord?id=CVE-2026-43503 Référence CVE CVE-2026-45842 https://www.cve.org/CVERecord?id=CVE-2026-45842 Référence CVE CVE-2026-45843 https://www.cve.org/CVERecord?id=CVE-2026-45843 Référence CVE CVE-2026-45846 https://www.cve.org/CVERecord?id=CVE-2026-45846 Référence CVE CVE-2026-45852 https://www.cve.org/CVERecord?id=CVE-2026-45852 Référence CVE CVE-2026-45856 https://www.cve.org/CVERecord?id=CVE-2026-45856 Référence CVE CVE-2026-45878 https://www.cve.org/CVERecord?id=CVE-2026-45878 Référence CVE CVE-2026-45886 https://www.cve.org/CVERecord?id=CVE-2026-45886 Référence CVE CVE-2026-45898 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-31533 Référence CVE CVE-2026-31676 https://www.cve.org/CVERecord?id=CVE-2026-31676 Référence CVE CVE-2026-43033 https://www.cve.org/CVERecord?id=CVE-2026-43033 Référence CVE CVE-2026-43077 https://www.cve.org/CVERecord?id=CVE-2026-43077 Référence CVE CVE-2026-43078 https://www.cve.org/CVERecord?id=CVE-2026-43078 Référence CVE CVE-2026-43284 https://www.cve.org/CVERecord?id=CVE-2026-43284 Référence CVE CVE-2026-43362 https://www.cve.org/CVERecord?id=CVE-2026-43362 Référence CVE CVE-2026-43494 https://www.cve.org/CVERecord?id=CVE-2026-43494 Référence CVE CVE-2026-43500 https://www.cve.org/CVERecord?id=CVE-2026-43500 Référence CVE CVE-2026-43503 https://www.cve.org/CVERecord?id=CVE-2026-43503 Référence CVE CVE-2026-45998 https://www.cve.org/CVERecord?id=CVE-2026-45998 Référence CVE CVE-2026-46000 https://www.cve.org/CVERecord?id=CVE-2026-46000 Référence CVE CVE-2026-46028 https://www.cve.org/CVERecord?id=CVE-2026-46028 Référence CVE CVE-2026-46300 https://www.cve.org/CVERecord?id=CVE-2026-46300 Référence CVE CVE-2026-46323 https://www.cve.org/CVERecord?id=CVE-2026-46323 Référence CVE CVE-2026-46333 https://www.cve.org/CVERecord?id=CVE-2026-46333 Référence CVE CVE-2026-47326 https://www.cve.org/CVERecord?id=CVE-2026-47326 Référence CVE CVE-2026-47327 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-43407 Référence CVE CVE-2026-43411 https://www.cve.org/CVERecord?id=CVE-2026-43411 Référence CVE CVE-2026-43413 https://www.cve.org/CVERecord?id=CVE-2026-43413 Référence CVE CVE-2026-43414 https://www.cve.org/CVERecord?id=CVE-2026-43414 Référence CVE CVE-2026-43455 https://www.cve.org/CVERecord?id=CVE-2026-43455 Référence CVE CVE-2026-43470 https://www.cve.org/CVERecord?id=CVE-2026-43470 Référence CVE CVE-2026-43483 https://www.cve.org/CVERecord?id=CVE-2026-43483 Référence CVE CVE-2026-43499 https://www.cve.org/CVERecord?id=CVE-2026-43499 Référence CVE CVE-2026-43501 https://www.cve.org/CVERecord?id=CVE-2026-43501 Référence CVE CVE-2026-43503 https://www.cve.org/CVERecord?id=CVE-2026-43503 Référence CVE CVE-2026-45445 https://www.cve.org/CVERecord?id=CVE-2026-45445 Référence CVE CVE-2026-45446 https://www.cve.org/CVERecord?id=CVE-2026-45446 Référence CVE CVE-2026-45447 https://www.cve.org/CVERecord?id=CVE-2026-45447 Référence CVE CVE-2026-45835 https://www.cve.org/CVERecord?id=CVE-2026-45835 Référence CVE CVE-2026-45841 https://www.cve.org/CVERecord?id=CVE-2026-45841 Référence CVE CVE-2026-45842 https://www.cve.org/CVERecord?id=CVE-2026-45842 Référence CVE CVE-2026-45843 https://www.cve.org/CVERecord?id=CVE-2026-45843 Référence CVE CVE-2026-45846 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-31504 Référence CVE CVE-2026-31533 https://www.cve.org/CVERecord?id=CVE-2026-31533 Référence CVE CVE-2026-31676 https://www.cve.org/CVERecord?id=CVE-2026-31676 Référence CVE CVE-2026-43033 https://www.cve.org/CVERecord?id=CVE-2026-43033 Référence CVE CVE-2026-43077 https://www.cve.org/CVERecord?id=CVE-2026-43077 Référence CVE CVE-2026-43078 https://www.cve.org/CVERecord?id=CVE-2026-43078 Référence CVE CVE-2026-43284 https://www.cve.org/CVERecord?id=CVE-2026-43284 Référence CVE CVE-2026-43494 https://www.cve.org/CVERecord?id=CVE-2026-43494 Référence CVE CVE-2026-43500 https://www.cve.org/CVERecord?id=CVE-2026-43500 Référence CVE CVE-2026-43503 https://www.cve.org/CVERecord?id=CVE-2026-43503 Référence CVE CVE-2026-44917 https://www.cve.org/CVERecord?id=CVE-2026-44917 Référence CVE CVE-2026-45998 https://www.cve.org/CVERecord?id=CVE-2026-45998 Référence CVE CVE-2026-46000 https://www.cve.org/CVERecord?id=CVE-2026-46000 Référence CVE CVE-2026-46028 https://www.cve.org/CVERecord?id=CVE-2026-46028 Référence CVE CVE-2026-46300 https://www.cve.org/CVERecord?id=CVE-2026-46300 Référence CVE CVE-2026-46333 https://www.cve.org/CVERecord?id=CVE-2026-46333 Référence CVE CVE-2026-46447 https://www.cve.org/CVERecord?id=CVE-2026-46447 Référence CVE CVE-2026-47326 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-43341 Référence CVE CVE-2026-43359 https://www.cve.org/CVERecord?id=CVE-2026-43359 Référence CVE CVE-2026-43360 https://www.cve.org/CVERecord?id=CVE-2026-43360 Référence CVE CVE-2026-43361 https://www.cve.org/CVERecord?id=CVE-2026-43361 Référence CVE CVE-2026-43362 https://www.cve.org/CVERecord?id=CVE-2026-43362 Référence CVE CVE-2026-43414 https://www.cve.org/CVERecord?id=CVE-2026-43414 Référence CVE CVE-2026-43437 https://www.cve.org/CVERecord?id=CVE-2026-43437 Référence CVE CVE-2026-43499 https://www.cve.org/CVERecord?id=CVE-2026-43499 Référence CVE CVE-2026-43501 https://www.cve.org/CVERecord?id=CVE-2026-43501 Référence CVE CVE-2026-43503 https://www.cve.org/CVERecord?id=CVE-2026-43503 Référence CVE CVE-2026-45843 https://www.cve.org/CVERecord?id=CVE-2026-45843 Référence CVE CVE-2026-45852 https://www.cve.org/CVERecord?id=CVE-2026-45852 Référence CVE CVE-2026-45910 https://www.cve.org/CVERecord?id=CVE-2026-45910 Référence CVE CVE-2026-45970 https://www.cve.org/CVERecord?id=CVE-2026-45970 Référence CVE CVE-2026-46004 https://www.cve.org/CVERecord?id=CVE-2026-46004 Référence CVE CVE-2026-46021 https://www.cve.org/CVERecord?id=CVE-2026-46021 Référence CVE CVE-2026-46043 https://www.cve.org/CVERecord?id=CVE-2026-46043 Référence CVE CVE-2026-46110 https://www.cve.org/CVERecord?id=

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

x RSS des indicateurs de compromission Flux RSS des durcissement et recommandations Flux RSS des bulletins d'actualité Premier Ministre S.G.D.S.N Agence nationale de la sécurité des systèmes d'information Paris, le 10 juin 2026 N° CERTFR-2026-AVI-0731 Affaire suivie par: CERT-FR Avis du CERT-FR Objet: Multiples vulnérabilités dans les produits Microsoft Gestion du document Référence CERTFR-2026-AVI-0731 Titre Multiples vulnérabilités dans les produits Microsoft Date de la première version 10 juin 2026 Date de la dernière version 10 juin 2026 Source(s) Bulletin de sécurité Microsoft CVE-2026-39833 du 27 mai 2026 Bulletin de sécurité Microsoft CVE-2026-43503 du 27 mai 2026 Bulletin de sécurité Microsoft CVE-2026-46300 du 27 mai 2026 Bulletin de sécurité Microsoft CVE-2026-45834 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-45835 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-45836 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-45838 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-45839 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-45840 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-45841 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-45842 du 28 mai 2026 Bulletin de sécurité Microsoft CVE-2026-45843 du 28 mai 2026 Bulletin de sécurité Mic

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

d?id=CVE-2026-43330 Référence CVE CVE-2026-43334 https://www.cve.org/CVERecord?id=CVE-2026-43334 Référence CVE CVE-2026-43365 https://www.cve.org/CVERecord?id=CVE-2026-43365 Référence CVE CVE-2026-43366 https://www.cve.org/CVERecord?id=CVE-2026-43366 Référence CVE CVE-2026-43419 https://www.cve.org/CVERecord?id=CVE-2026-43419 Référence CVE CVE-2026-43437 https://www.cve.org/CVERecord?id=CVE-2026-43437 Référence CVE CVE-2026-43441 https://www.cve.org/CVERecord?id=CVE-2026-43441 Référence CVE CVE-2026-43494 https://www.cve.org/CVERecord?id=CVE-2026-43494 Référence CVE CVE-2026-43500 https://www.cve.org/CVERecord?id=CVE-2026-43500 Référence CVE CVE-2026-43503 https://www.cve.org/CVERecord?id=CVE-2026-43503 Référence CVE CVE-2026-46300 https://www.cve.org/CVERecord?id=CVE-2026-46300 Référence CVE CVE-2026-46333 https://www.cve.org/CVERecord?id=CVE-2026-46333 Gestion détaillée du document le 05 juin 2026 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la Défense et de la Sécurité Nationale / Agence nationale de la sécurité des systèmes d'information

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

d?id=CVE-2026-43451 Référence CVE CVE-2026-43452 https://www.cve.org/CVERecord?id=CVE-2026-43452 Référence CVE CVE-2026-43453 https://www.cve.org/CVERecord?id=CVE-2026-43453 Référence CVE CVE-2026-43458 https://www.cve.org/CVERecord?id=CVE-2026-43458 Référence CVE CVE-2026-43459 https://www.cve.org/CVERecord?id=CVE-2026-43459 Référence CVE CVE-2026-43466 https://www.cve.org/CVERecord?id=CVE-2026-43466 Référence CVE CVE-2026-43472 https://www.cve.org/CVERecord?id=CVE-2026-43472 Référence CVE CVE-2026-43475 https://www.cve.org/CVERecord?id=CVE-2026-43475 Référence CVE CVE-2026-43480 https://www.cve.org/CVERecord?id=CVE-2026-43480 Référence CVE CVE-2026-43503 https://www.cve.org/CVERecord?id=CVE-2026-43503 Référence CVE CVE-2026-45848 https://www.cve.org/CVERecord?id=CVE-2026-45848 Référence CVE CVE-2026-45852 https://www.cve.org/CVERecord?id=CVE-2026-45852 Référence CVE CVE-2026-45856 https://www.cve.org/CVERecord?id=CVE-2026-45856 Référence CVE CVE-2026-45857 https://www.cve.org/CVERecord?id=CVE-2026-45857 Référence CVE CVE-2026-45860 https://www.cve.org/CVERecord?id=CVE-2026-45860 Référence CVE CVE-2026-45862 https://www.cve.org/CVERecord?id=CVE-2026-45862 Référence CVE CVE-2026-45866 https://www.cve.org/CVERecord?id=CVE-2026-45866 Référence CVE CVE-2026-45867 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-31504 Référence CVE CVE-2026-31533 https://www.cve.org/CVERecord?id=CVE-2026-31533 Référence CVE CVE-2026-31676 https://www.cve.org/CVERecord?id=CVE-2026-31676 Référence CVE CVE-2026-43033 https://www.cve.org/CVERecord?id=CVE-2026-43033 Référence CVE CVE-2026-43077 https://www.cve.org/CVERecord?id=CVE-2026-43077 Référence CVE CVE-2026-43078 https://www.cve.org/CVERecord?id=CVE-2026-43078 Référence CVE CVE-2026-43284 https://www.cve.org/CVERecord?id=CVE-2026-43284 Référence CVE CVE-2026-43494 https://www.cve.org/CVERecord?id=CVE-2026-43494 Référence CVE CVE-2026-43500 https://www.cve.org/CVERecord?id=CVE-2026-43500 Référence CVE CVE-2026-43503 https://www.cve.org/CVERecord?id=CVE-2026-43503 Référence CVE CVE-2026-45966 https://www.cve.org/CVERecord?id=CVE-2026-45966 Référence CVE CVE-2026-45998 https://www.cve.org/CVERecord?id=CVE-2026-45998 Référence CVE CVE-2026-46000 https://www.cve.org/CVERecord?id=CVE-2026-46000 Référence CVE CVE-2026-46028 https://www.cve.org/CVERecord?id=CVE-2026-46028 Référence CVE CVE-2026-46300 https://www.cve.org/CVERecord?id=CVE-2026-46300 Référence CVE CVE-2026-46333 https://www.cve.org/CVERecord?id=CVE-2026-46333 Référence CVE CVE-2026-47326 https://www.cve.org/CVERecord?id=CVE-2026-47326 Référence CVE CVE-2026-47327 https://www.cve.org/CVERecord?id=

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

De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Certaines d'entre elles permettent à un attaquant de provoquer une élévation de privilèges, une atteinte à la confidentialité des données et un déni de service.

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-021359LinuxのLinux Kernelにおける不特定の脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました。この脆弱性は、net: skbuffのフラグメント転送ヘルパーを通じて共有フラグメントマーカーが正しく伝播されない問題に起因します。2つのフラグメント転送ヘルパー（__pskb_copy_fclone() と skb_shift()）は、フラグメントをソースから宛先に移動するときに skb_shinfo()-flags の SKBFL_SHARED_FRAG ビットを伝播しません。__pskb_copy_fclone() はフラグメント記述子のコピー後に残りの shinfo メタデータを skb_copy_header() に委ねますが、このヘルパーは gso_{size,segs,type} のみを引き継ぎ、skb_shinfo()-flags に触れません。skb_shift() はフラグメント記述子を直接移動し、flags はそのままにします。その結果、宛先の skb は同じ外部所有またはページキャッシュ対応ページへの参照を維持しつつ、skb_has_shared_frag() が false を返します。この不整合は、skb_has_shared_frag() を使って共有ページを skb_cow_data() 経由で迂回する必要があるかを判断するインプレースライターにとって有害です。ESP入力（esp4.c, esp6.c）はそのようなライターの一例であり、単一の nft 'dup to local' ルールやその他の nf_dup_ipv4() / xt_TEE 呼び出しで pskb_copy() された skb が esp_input() にてマーカーを剥奪された状態で渡ると、権限のないユーザーが authencesn-ESN の逸脱書き込みを介してルート所有の読み取り専用ファイルのページキャッシュに書き込むことが可能になります。フラグメント記述子が実際にソースから移動された場合は、宛先の skb に SKBFL_SHARED_FRAG を設定します。skb_copy() と skb_copy_expand() も skb_copy_header() を共有しますが、すべてのページデータを新たに割り当てられたヘッドストレージに線形化し、nr_frags == 0 となるため、skb_has_shared_frag() は自動的に false を返しており、変更は不要です。同様の欠落は skb_gro_receive() と skb_gro_receive_list() にも存在します。前者は直接のフラグメント移動ループおよび head_frag + memcpy 経路の2つで受信skbのフラグメント記述子をアキュムレーターの最後のサブskbに移動し、後者は受信skbを p の frag_list に連結します。下流の skb_segment() は skb_shinfo(p)-flags のみを読み取り、skb_segment_list() は各サブskbの shinfo を nskb として再利用するため、p と lp は両方マーカーを持つ必要があります。同様の欠落は tcp_clone_payload() にも存在します。これは sk_write_queue 上の skb からフラグメント記述子を移動して新たに割り当てられた nskb で MTU プローブ skb を構築します。このヘルパーは同じタイプに属しており、一貫性のため同じ修正が必要です。現在のところ、このギャップを介してユーザーページに到達する TCP TX 側のインプレースライターは知られていませんが、将来マーカーに依存する利用者が silently 後退する可能性があります。同様の欠落は skb_segment() にもあります。反復ごとのフラグマージは head_skb のフラグのみを取得し、head_skb のフラグメント枯渇時に frag_skb を list_skb に再バインドする内部のスイッチは新しい frag_skb のフラグを nskb に反映しません。両方の箇所で frag_skb のフラグを反映させ、frag_list メンバーからフラグメントを取り出すセグメントがマーカーを保持するように修正しました。

Official advisory ↗
KISA KrCERT/CC · Korean · KNVD-6863Linux 제품 보안 업데이트 권고

Linux Kernel에서 발생하는 Improper Initialization 취약점(CVE-2026-43503) [1]~[9]

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
Linux: cef401de7be8c4e155c6746bfccf721a4fa5fab9 < fbeab9555564a1b98e8582cd106dfe46c4606991, cef401de7be8c4e155c6746bfccf721a4fa5fab9 < 179f1852bdedc300e373e807cc102cd81feff196, cef401de7be8c4e155c6746bfccf721a4fa5fab9 < 12401fcfb01f53ccc63ab0a3246570fe8f3105ee, cef401de7be8c4e155c6746bfccf721a4fa5fab9 < 989214c66884d70716d83dc1d0bf5e16287bf349, cef401de7be8c4e155c6746bfccf721a4fa5fab9 < fc6eb39c55e97df2f94ad974b8a5bbcd019da2c8, cef401de7be8c4e155c6746bfccf721a4fa5fab9 < ff375cc75f9167168db38e0464a482d5fbc8d81d, cef401de7be8c4e155c6746bfccf721a4fa5fab9 < 9bc9d6d6967a2239aa57af2aa53554eddd640d20, cef401de7be8c4e155c6746bfccf721a4fa5fab9 < 48f6a5356a33dd78e7144ae1faef95ffc990aae0, 3.9
Fixed
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 23 May 2026 · Last source change 24 Aug 2026, 12:06 UTC · CWE-664 · Improper Control of a Resource Through its Lifetime

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-31536
Product sourceCNA
Remediation sourceVendor CSAF · Red Hat Product Security
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 ↗

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-2026-31536↗Vendor CSAF · Red Hat Product Security↗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-43503 · cve.blacktree.nl