Skip to content
PiLabs security advisory Updated 17 November 2026
High 7.8 CVE-2026-46300 Known exploited

Lost shared-fragment marker in Linux kernel network buffer coalescing

Affected
Linux Kernel
Affected versions
≥ 3.1.5, ≤ 3.1.6; ≥ 3.9, ≤ 5.10.257; ≥ 4.12, < 4.12.91; ≥ 4.13, < 4.13.67; ≥ 4.14, < 4.14.68; ≥ 4.15, < 4.15.65; ≥ 4.16, < 4.16.63; ≥ 4.17, < 4.17.55
Disclosed
Last updated
CVSS 3.1 vector
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Written automatically on 17 November 2026 from the NVD and the CISA catalogue of known exploited vulnerabilities. The facts above come from those sources; check them before you act. Sources of this advisory

CISA lists CVE-2026-46300 in the Linux kernel as exploited. The flaw can let ESP decrypt in place over page-cache backed data. CVSS 3.1 rates it 7.8, high.

What is affected

The sources describe CVE-2026-46300 as a flaw in the Linux kernel, in the network buffer (skb) code. The source title is "Linux Kernel Missing Initialization of a Variable Vulnerability", and the weakness is recorded as CWE-456. The sources list these affected version ranges, exactly as given:

  • ≥ 3.1.5, ≤ 3.1.6
  • ≥ 3.9, ≤ 5.10.257
  • ≥ 4.12, < 4.12.91
  • ≥ 4.13, < 4.13.67
  • ≥ 4.14, < 4.14.68
  • ≥ 4.15, < 4.15.65
  • ≥ 4.16, < 4.16.63
  • ≥ 4.17, < 4.17.55

The vulnerability was disclosed on 2026-05-23. Distribution kernels often carry their own version numbers and backported fixes, so the ranges above are a starting point and not a final answer about your systems.

What the flaw allows

According to the description in the sources, the function skb_try_coalesce() can attach paged fragments from one buffer to another. If the source buffer carries the shared-fragment marker SKBFL_SHARED_FRAG, the resulting buffer can hold the same externally owned or page-cache backed fragments, but the marker is lost. Later code that writes in place relies on that marker.

The sources give one example. The ESP input path checks for shared fragments before deciding whether it can skip copying the data. If TCP receive coalescing has moved shared fragments into a buffer without the marker, ESP can conclude there are none and decrypt in place over page-cache backed fragments.

The CVSS 3.1 base score is 7.8, which is high severity. The vector is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. It describes a local attack with low complexity and low privileges, no user interaction, and high impact on confidentiality, integrity and availability.

Exploitation

CISA lists this vulnerability as exploited in its Known Exploited Vulnerabilities catalogue and added it on 2026-10-28. CISA states a due date of 2026-10-31, which is its deadline for US federal agencies. CISA records ransomware use as unknown. The sources do not describe who is exploiting the flaw or how, and this advisory does not either.

What to do

Check whether the Linux kernels you run fall within the ranges above, taking into account your distribution's own advisories and backports. The sources describe a code fix that preserves the marker when fragments are transferred. Fixed releases are listed in the vendor and distribution advisories and in the kernel.org stable commits. See the mitigation section for the references.

What to do

CISA's required action is to apply mitigations in accordance with vendor instructions, or to discontinue use of the product if mitigations are unavailable. The facts name no separate workaround, so the remedy is the kernel fix. Check the kernel.org stable commit at the kernel.org stable commit and your distribution's advisory for the fixed releases. More detail is in the NVD entry and the CISA Known Exploited Vulnerabilities catalogue.

Sources

All vulnerabilities

Need to know whether these vulnerabilities affect you?

A consultant can check which of the affected products you run and what to fix first. For a wider review, ask for a security assessment.