CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Called exploited 54 days after disclosure.
Measured from the CVE publication date to the earliest of 3 KEV catalogues that list it.
The life of this vulnerability
- CVE published
- First KEV listing54d
- Last sightingsame day
Gaps are compressed to equal steps. The elapsed time is printed under each.
Which catalogues call it exploited
- CISA KEVUS federallisted Aug 27, 2026
- EUVDENISA, European Unionlisted Aug 27, 2026
- VulnCheck KEVcommercial researchlisted Aug 27, 2026
- CIRCLaggregator, mirrors the abovelisted Aug 27, 2026, not counted
3 catalogues list it. CIRCL aggregates the others and is shown but not counted.
Public exploitation evidence
- reported exploitationeuvd.enisa.europa.eu/enisa/EUVD-2026-41669
- reported exploitationprevidian.com/CVE-2026-53362
- reported exploitationwww.cisa.gov/sites/default/files/feeds/known_exploited_vulne
3 public reports collected from VulnCheck and CIRCL, first on Aug 27, 2026. Each links to its original source. We have not verified them.
Description
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 b
Required action (CISA)
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.
References
- NVD record for CVE-2026-53362
- CVE.org record
- CISA Known Exploited Vulnerabilities catalog
- git.kernel.org/stable/c/14200d435af9a9eeb444f529fc2f689a236b7962
- git.kernel.org/stable/c/65fb14cbebb0cd0eff903a22d33537ddc8b95769
- git.kernel.org/stable/c/46f201f8b4c39633a1fa3dc12459f506d470993d
- git.kernel.org/stable/c/6374fb9edf72c67a118a2c214a0dddd04c921e0a