HIGH 8.8

CVE-2026-53275: Linux Kernel IPv6 MLD Query Use-After-Free Vulnerability

A memory safety flaw exists in how the Linux kernel processes IPv6 Multicast Listener Discovery (MLD) queries. When the kernel receives an MLD query packet, it saves a pointer to the multicast group address early in processing. However, later in the same function, the kernel may reallocate the packet buffer to add more data. After this reallocation, the saved pointer becomes invalid—it points to freed memory. If the code then tries to read from this invalid pointer, the kernel crashes or behaves unpredictably. An attacker on the same local network can send a specially crafted MLD query to trigger this condition, potentially causing a denial of service or worse.

Source data · NVD / CISA · public domain

CVSS
3.1 · 8.8 HIGH · CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weaknesses (CWE)
CWE-416
Affected products
7 configuration(s)
Published / Modified
2026-06-25 / 2026-07-08

NVD description (verbatim)

In the Linux kernel, the following vulnerability has been resolved: ipv6: mcast: Fix use-after-free when processing MLD queries When processing an MLD query, a pointer to the multicast group address is retrieved when initially parsing the packet. This pointer is later dereferenced without being reloaded despite the fact that the skb header might have been reallocated following the pskb_may_pull() calls, leading to a use-after-free [1]. Fix by copying the multicast group address when the packet is initially parsed. [1] BUG: KASAN: slab-use-after-free in __mld_query_work (net/ipv6/mcast.c:1512) Read of size 8 at addr ffff8881154b8e90 by task kworker/4:1/118 Workqueue: mld mld_query_work Call Trace: <TASK> dump_stack_lvl (lib/dump_stack.c:94 lib/dump_stack.c:120) print_address_description.constprop.0 (mm/kasan/report.c:378) print_report (mm/kasan/report.c:482) kasan_report (mm/kasan/report.c:595) __mld_query_work (net/ipv6/mcast.c:1512) mld_query_work (net/ipv6/mcast.c:1563) process_one_work (kernel/workqueue.c:3314) worker_thread (kernel/workqueue.c:3397 kernel/workqueue.c:3478) kthread (kernel/kthread.c:436) ret_from_fork (arch/x86/kernel/process.c:158) ret_from_fork_asm (arch/x86/entry/entry_64.S:245) </TASK> [...] Freed by task 118: kasan_save_stack (mm/kasan/common.c:57) kasan_save_track (mm/kasan/common.c:78) kasan_save_free_info (mm/kasan/generic.c:584) __kasan_slab_free (mm/kasan/common.c:253 mm/kasan/common.c:285) kfree (./include/linux/kasan.h:235 mm/slub.c:2689 mm/slub.c:6251 mm/slub.c:6566) pskb_expand_head (net/core/skbuff.c:2335) __pskb_pull_tail (net/core/skbuff.c:2878 (discriminator 4)) __mld_query_work (net/ipv6/mcast.c:1495 (discriminator 1)) mld_query_work (net/ipv6/mcast.c:1563) process_one_work (kernel/workqueue.c:3314) worker_thread (kernel/workqueue.c:3397 kernel/workqueue.c:3478) kthread (kernel/kthread.c:436) ret_from_fork (arch/x86/kernel/process.c:158) ret_from_fork_asm (arch/x86/entry/entry_64.S:245)

7 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

CVE-2026-53275 is a use-after-free vulnerability in the IPv6 multicast listener discovery (MLD) handling code (net/ipv6/mcast.c). During MLD query processing in __mld_query_work(), a pointer to the multicast group address is extracted early via packet parsing. Subsequent calls to pskb_may_pull() and pskb_expand_head() can reallocate the socket buffer (skb), invalidating the original pointer. The code then dereferences this stale pointer without reloading it, triggering a KASAN slab-use-after-free detection. The fix copies the multicast group address into a local variable at parse time, eliminating the dependency on the pointer remaining valid across buffer reallocations. This is a classic memory safety issue arising from pointer lifetime management in kernel packet-handling code.

Business impact

This vulnerability can cause kernel panic or denial of service on systems with IPv6 enabled. Any attacker capable of sending network packets to an affected host (typically from the same local network segment, given the AV:A vector) can crash the system or cause unpredictable behavior. For organizations running critical services on Linux servers with IPv6—especially those in cloud or data-center environments where multicast traffic may be present—an unexpected kernel crash disrupts availability. The HIGH severity rating reflects both the certainty of triggering the flaw and the direct impact on system stability.

Affected systems

The Linux kernel is affected. Based on the CVE record, multiple kernel versions are impacted. Verify the exact affected versions, patch versions, and distribution timelines against the official Linux kernel security advisories and your vendor's documentation. Systems with IPv6 enabled are at risk; however, exploitability may be constrained by network topology (the vulnerability requires local network access to send the malicious MLD query).

Exploitability

Exploitability is relatively straightforward from a technical perspective: an attacker on the same local network (AV:A in CVSS) can craft and send a malicious MLD query packet with no authentication required (PR:N) and no user interaction needed (UI:N). The payload is a network packet, making it trivial to send. However, practical exploitation depends on network segmentation. In isolated or air-gapped networks, exposure may be limited. In flat network architectures or cloud environments where multicast is routed, the attack surface is broader. The vulnerability is not yet tracked in the CISA KEV catalog as of the data provided.

Remediation

Apply the Linux kernel patch that copies the multicast group address during initial packet parsing, ensuring the address value is not dependent on the packet buffer pointer. Patch availability varies by distribution; check your Linux vendor's security advisories (Red Hat, Canonical, SUSE, etc.) for specific patch versions and kernel release dates. Systems unable to patch immediately should consider disabling IPv6 if operationally feasible, or implementing network-level controls to restrict MLD query traffic to trusted sources.

Patch guidance

Identify the specific Linux kernel version and distribution in your environment. Consult your vendor's security advisory for CVE-2026-53275 to obtain the patched kernel version and installation instructions. Typical patching steps: (1) verify current kernel version with 'uname -r'; (2) download the patched kernel from your vendor's update repository; (3) test the patch in a non-production environment first; (4) schedule a maintenance window for production systems (kernel updates typically require a reboot); (5) reboot and verify the system boots successfully and the vulnerability is resolved. Maintain backups before patching.

Detection guidance

Monitor kernel logs and audit systems for KASAN warnings, kernel panics, or oops messages mentioning mcast.c or __mld_query_work(). Specifically, look for 'slab-use-after-free' or 'use-after-free in __mld_query_work' strings in dmesg or systemd journal. Network-based detection is harder; however, intrusion detection signatures can look for malformed MLD query packets with unusual payload sizes or structures designed to trigger buffer reallocation. Enable kernel Address Sanitizer (KASAN) in testing/staging environments to catch similar issues early.

Why prioritize this

This vulnerability warrants high priority patching due to its CVSS 8.8 (HIGH) score, the ease of triggering a crash from the local network, and the direct business impact of kernel panic on service availability. Although it requires network access (AV:A), local networks are common in cloud, data center, and corporate environments. No advanced exploitation skills or special conditions are needed. The absence from the CISA KEV catalog does not diminish the risk; it reflects lack of active weaponization or widespread attacks at publication time, not severity.

Risk score, explained

CVSS 8.8 reflects: (1) Attack Vector Adjacent (AV:A)—the attacker must be on the same network segment; (2) Attack Complexity Low (AC:L)—no special conditions needed; (3) Privileges Required None (PR:N)—no credentials or special rights; (4) User Interaction None (UI:N)—the flaw triggers automatically upon packet receipt; (5) Impact on Confidentiality, Integrity, and Availability all High (C:H/I:H/A:H)—the use-after-free can leak kernel memory, corrupt data, or crash the system. The HIGH severity is justified given the reliability and severity of impact.

Frequently asked questions

Can this vulnerability be exploited over the Internet?

No. The CVSS vector AV:A (Adjacent) means the attacker must be on the same local network segment. Exploiting this from the Internet is not feasible unless the attacker has local network access or the target routes multicast traffic across network boundaries (uncommon and typically disabled).

What happens if I disable IPv6 on my systems?

Disabling IPv6 eliminates the attack surface for this vulnerability because MLD queries are IPv6-specific. However, many modern systems and applications increasingly rely on IPv6. Disabling it is a temporary mitigation only; patching the kernel is the proper long-term fix.

Will my system definitely crash if targeted by this exploit?

In the vulnerable code path, yes—dereferencing a freed memory pointer triggers a kernel panic due to KASAN detection. However, the specific conditions (an MLD query that causes buffer reallocation) must occur. Most normal network traffic will not trigger it, but a malicious packet crafted to cause reallocation will reliably crash the kernel.

How do I know if my kernel is vulnerable?

Check your kernel version with 'uname -r' and cross-reference it against the Linux kernel advisory for CVE-2026-53275. Your Linux vendor (Red Hat, Ubuntu, SUSE, etc.) publishes a list of affected versions. If your version is listed as vulnerable and you have not applied the patch, assume you are affected.

This analysis is provided for educational and security awareness purposes. The information is based on the CVE record and official Linux kernel advisory. Specific patch versions, affected kernel releases, and remediation steps vary by Linux distribution and must be verified against your vendor's official security advisory. Test all patches in a non-production environment before deploying to production systems. This document does not constitute legal advice or a guarantee of security. Organizations should engage with their Linux vendor and security teams to assess risk and plan remediation for their specific infrastructure. Source: NVD (public-domain), retrieved 2026-08-03. Analysis generated by SEC.co (claude-haiku-4-5).