VULNpocalypse

CVE-2026-53362: Linux Kernel Unspecified Vulnerability

Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.

Generated by VEDAS. Scores as of 2026-11-01 19:19 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.

What it is

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.

Description quoted from the CVE record (assigned by Linux, published 2026-07-04).

Weakness: CWE-122 Heap-based Buffer Overflow

How it can be exploited

Exploitable with local access with low attack complexity needing low privileges and no user interaction. Impact: confidentiality high, integrity high, availability high. CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

CISA assessment (SSVC): CISA assesses exploitation as active. Automatable: no. Technical impact: total.

On CISA KEV since
2026-08-27
US federal deadline
2026-08-30
Ransomware use
Not known

Public exploit evidence (Exploit Observer)

Also known as: BDU:2026-09713, EUVD-2026-41669, GHSA-3x6f-vm7x-cgm7

VEDAS cluster: VEDAS:BARNACLEBLAST

Exploit Observer has no public exploit code that names this CVE or one of its aliases.

Research and write-ups (2)

Vulnerability databases and vendor advisories (12)

Catalogue entries, not exploit evidence.

291 more references returned by Exploit Observer did not name this CVE or an alias, so they are left out.

VEDAS data as of 2026-11-01T17:12 UTC; fetched 2026-11-02.

Live scores

EPSS
0.007
low predicted chance of attack
VEDAS
0.975
strong exploit evidence
On CISA KEV
Yes, since 2026-08-27
Detection rule
Out of scope (local)
EPSS (chance of attack)
100.1Added to CISA KEV 2026-08-27CVE-2026-53362 EPSS over time2026-082026-11-01
VEDAS (exploit evidence)
100.9Added to CISA KEV 2026-08-27CVE-2026-53362 VEDAS over time2026-082026-11-01

Thin horizontal line: the “likely” (EPSS 0.10) or “strong” (VEDAS 0.90) threshold. Shaded “no data” areas are periods when cve-scores did not publish. The vertical line is the day CISA added it to its exploited list.

Who is affected

ProductAffectedNot affected
Linux Linuxfrom 773ba4fe9104 before 14200d435af9 (git commit)
from 773ba4fe9104 before 65fb14cbebb0 (git commit)
from 773ba4fe9104 before 46f201f8b4c3 (git commit)
from 773ba4fe9104 before 6374fb9edf72 (git commit)
from 773ba4fe9104 before e9eacf19281e (git commit)
from 773ba4fe9104 before 736b380e28d0 (git commit)		Not stated
Linux Linuxversion 6.00 is not affected (up to 6.0); 6.1.177 is not affected; 6.6.144 is not affected; 6.12.95 is not affected

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

Exploit Observer also maps it to: amazon.com_inc. amazon_linux_2023, linux linux_kernel, red_hat,_inc. red_hat_enterprise_linux, red_hat,_inc. red_hat_enterprise_linux_for_nvidia, ооо_«ред_софт» ред_ос, ооо_«русбитех-астра» astra_linux_special_edition, сообщество_свободного_программного_обеспечения debian_gnu/linux, сообщество_свободного_программного_обеспечения linux.

How to fix it

CISA required action: 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.

Vendor guidance:

How to detect it

This bug needs local access to exploit. VEDAS signatures cover remotely exploitable bugs for now, so there is no network rule or remote check for it. Patch it and watch your endpoint telemetry for unusual local activity.

Advisories on this CVE

References

Government sources

Other references

Other databases

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, CISA KEV, cve-scores (EPSS and VEDAS), Exploit Observer. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.