Actively exploited KEV catalog
CVE-2026-53362

Linux Kernel Unspecified Vulnerability

In the Linux kernel, the following vulnerability has been resolved: ipv6: account for fraggap on the paged allocation path In __ip6_append_data(), when the paged-allocation branch is taken (MSG_MORE / NETIF_F_SG / large fraglen),…

CheckOps priority index
4.3/10 Patch within 7 days
Severity7.8
Probability0.1
Exploitation2/5

Severity = CVSS. Probability = EPSS (FIRST). Exploitation = public signals: KEV, EUVD, ransomware, EPSS above 10 %, no account required.

EPSS · today 0.71% higher than 53.5% of CVEs
CVSS 3.1 7.8 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:
Exploited for 68 days 27 Aug 2026
CISA due date 30 Aug 2026 for US federal agencies

Exploitation probability EPSS · FIRST

05010025 Sep05 Oct15 Oct24 Oct02 Nov
EPSS probability (%)Percentile among all CVEs

Exploitation signals 2 / 5

  • KEV catalog (CISA)27 Aug 2026
  • Exploited in EUVD (ENISA)27 Aug 2026
  • Used by ransomwareno
  • EPSS above 10 %0.71%
  • No account, over the networkno

What to do

Fix

Apply the vendor’s fix as soon as it is available.

CISA guidance: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

Meanwhile

Take the service off the internet or restrict access to it, watch the logs and look for signs of compromise.

Manufacturers (CRA)

Exploited vulnerability in your product: early warning to ENISA within 24 h, then notification within 72 h (Article 14 of the Cyber Resilience Act). The CRA explained

Description ENISA EUVD

In the Linux kernel, the following vulnerability has been resolved: ipv6: account for fraggap on the paged allocation path In __ip6_append_data(), when the paged-allocation branch is taken (MSG_MORE / NETIF_F_SG / large fraglen), alloclen and pagedlen are computed as alloclen = fragheaderlen + transhdrlen; pagedlen = datalen - transhdrlen; datalen already includes fraggap (datalen = length + fraggap). When fraggap is non-zero, this is not the first skb and transhdrlen is zero. The fraggap bytes carried over from the previous skb are copied just past the fragment headers in the new skb's linear area. The linear area is therefore undersized by fraggap bytes while pagedlen is overstated by the same amount, and the copy writes past skb->end into the trailing skb_shared_info. An unprivileged user can trigger this via a UDPv6 socket using MSG_MORE together with MSG_SPLICE_PAGES. The bad accounting was introduced by commit 773ba4fe9104 ("ipv6: avoid partial copy for zc"). Before commit ce650a166335 ("udp6: Fix __ip6_append_data()'s handling of MSG_SPLICE_PAGES"), the negative copy value caused -EINVAL to be returned. That later commit allowed MSG_SPLICE_PAGES to proceed in this case, making the corruption triggerable. The non-paged branch sets alloclen to fraglen, which already accounts for fraggap because datalen does. Bring the paged branch in line by adding fraggap to alloclen and subtracting it from pagedlen. After this adjustment, copy no longer collapses to -fraggap on the paged path, so remove the stale comment describing that old arithmetic. Since a negative copy is no longer expected for a valid MSG_SPLICE_PAGES case, remove the MSG_SPLICE_PAGES exception from the negative copy check.

Affected products

LinuxKernel
Affected versions
  • patch: 6.1.177
  • 773ba4fe9104a64a54d1c00f0fb6ffb95def2b03 <736b380e28d0480c7bc3e022f1950f31fe53a7c5
  • 6.0
  • patch: 6.6.144
  • 773ba4fe9104a64a54d1c00f0fb6ffb95def2b03 <14200d435af9a9eeb444f529fc2f689a236b7962
  • 773ba4fe9104a64a54d1c00f0fb6ffb95def2b03 <6374fb9edf72c67a118a2c214a0dddd04c921e0a
  • 773ba4fe9104a64a54d1c00f0fb6ffb95def2b03 <65fb14cbebb0cd0eff903a22d33537ddc8b95769
  • 773ba4fe9104a64a54d1c00f0fb6ffb95def2b03 <46f201f8b4c39633a1fa3dc12459f506d470993d
  • patch: 6.12.95
  • patch: 6.18.38
  • 773ba4fe9104a64a54d1c00f0fb6ffb95def2b03 <e9eacf19281ea2498b36291b56c9606118c2d74e
  • patch: 7.2

Open source packages OSV

Affected libraries according to OSV, with fixed versions.

Timeline

  1. Published

  2. Exploitation reported (ENISA)

  3. Added to the KEV catalog

  4. CISA remediation due date

References

Other exploited vulnerabilities from the same vendor

  • CVE-2026-46300Linux Kernel Missing Initialization of a Variable Vulnerability
    5.4 · Rising fast
  • CVE-2026-53266Linux Kernel Out-of-Bounds Write Vulnerability
    4.7 · Actively exploited
  • CVE-2025-39964Linux Kernel Race Condition Vulnerability
    4.4 · Actively exploited
  • CVE-2025-39682Linux Kernel Improper Check for Unusual or Exceptional Conditions Vulnerability
    5.8 · Actively exploited
  • CVE-2022-0995Linux Kernel Out-of-Bounds Write Vulnerability
    4.6 · Actively exploited
  • CVE-2022-0492Linux Kernel Improper Authentication Vulnerability
    4.5 · Actively exploited

Are you affected?

CheckOps reads your SBOMs and scans, and alerts you as soon as one of your dependencies is exploited.

Get notified at launch

Sources: CISA KEV · ENISA EUVD · FIRST EPSS · OSV. Public data aggregated by CheckOps, updated automatically. Source texts remain the property of their authors. All exploited vulnerabilities