Book møte

Sårbarheter

CVE-2026-53362

Linux Kernel Unspecified Vulnerability

Utnyttes aktivt (CISA KEV) Høy 7.8 CVSS 3.1

Beskrivelse

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.

Beskrivelsen gjengis slik kilden har publisert den, på engelsk.

Nøkkelfakta

Publisert
2026-07-04
Sist endret
2026-08-28
Tildelt av
416baaa9-dc9f-4396-8d5f-8c081fb06d67
CVSS-vektor
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Scoret av
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Sannsynlighet for utnyttelse
0.3 % høyere enn 18 % av alle kjente sårbarheter
EPSS, neste 30 dager, modell v2026.06.15
Rettelse finnes
Ja, se referansene

Aktivt utnyttet

CISA førte denne sårbarheten inn i katalogen over kjente utnyttede sårbarheter 2026-08-27, med utbedringsfrist 2026-08-30 for amerikanske føderale etater.

Pålagt tiltak: 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.

Berørte produkter

Leverandør Produkt Versjoner Status
Linux Linux Kernel ≥ 6.0, < 6.1.177 Berørt
Linux Linux Kernel ≥ 6.13, < 6.18.38 Berørt
Linux Linux Kernel ≥ 6.19, < 7.1.3 Berørt
Linux Linux Kernel ≥ 6.2, < 6.6.144 Berørt
Linux Linux Kernel ≥ 6.7, < 6.12.95 Berørt

Svakhetstype

  • CWE-787: Out-of-bounds Write

    The product writes data past the end, or before the beginning, of the intended buffer.

  • CWE-122: Heap-based Buffer Overflow

    A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().

Referanser

Relatert hos Berigo

Artikler

Berører dette dere?

En sårbarhet betyr bare noe hvis dere kjører produktet, i en berørt versjon, et sted en angriper kommer til.

Sjekk aktivalisten deres Bla i alle sårbarheter