From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-53006: ipv6: fix possible UAF in icmpv6_rcv()
Date: Wed, 24 Jun 2026 17:30:30 +0100 [thread overview]
Message-ID: <2026062448-CVE-2026-53006-2b02@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ipv6: fix possible UAF in icmpv6_rcv()
Caching saddr and daddr before pskb_pull() is problematic
since skb->head can change.
Remove these temporary variables:
- We only access &ipv6_hdr(skb)->saddr and &ipv6_hdr(skb)->daddr
when net_dbg_ratelimited() is called in the slow path.
- Avoid potential future misuse after pskb_pull() call.
The Linux kernel CVE team has assigned CVE-2026-53006 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.4 with commit 4b3418fba0fe819197e3359d5ddbef84ba2c59de and fixed in 5.10.258 with commit 7bff2c8fe5c35ae58bf73104f53db3676e6e5d94
Issue introduced in 4.4 with commit 4b3418fba0fe819197e3359d5ddbef84ba2c59de and fixed in 5.15.209 with commit aff0f28f5be803de2452ce702631c021fcd9ce8a
Issue introduced in 4.4 with commit 4b3418fba0fe819197e3359d5ddbef84ba2c59de and fixed in 6.1.175 with commit 38bdbc897c0d83a3e2b925a51b69420f1feba29a
Issue introduced in 4.4 with commit 4b3418fba0fe819197e3359d5ddbef84ba2c59de and fixed in 6.6.141 with commit 0069813e6ca9309eca78022bcb3aeb1e9ef90a12
Issue introduced in 4.4 with commit 4b3418fba0fe819197e3359d5ddbef84ba2c59de and fixed in 6.12.91 with commit 1e1f0f89ee4692a64be3f3707ff8ac1ae57b03e7
Issue introduced in 4.4 with commit 4b3418fba0fe819197e3359d5ddbef84ba2c59de and fixed in 6.18.33 with commit 7c66b368c6ff453f99cb39d84af93e908e51eef2
Issue introduced in 4.4 with commit 4b3418fba0fe819197e3359d5ddbef84ba2c59de and fixed in 7.0.10 with commit 085e31a811ef234ef8c3e219c4636dfebfe7e10f
Issue introduced in 4.4 with commit 4b3418fba0fe819197e3359d5ddbef84ba2c59de and fixed in 7.1 with commit f996edd7615e686ada141b7f3395025729ff8ccb
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-53006
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
net/ipv6/icmp.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/7bff2c8fe5c35ae58bf73104f53db3676e6e5d94
https://git.kernel.org/stable/c/aff0f28f5be803de2452ce702631c021fcd9ce8a
https://git.kernel.org/stable/c/38bdbc897c0d83a3e2b925a51b69420f1feba29a
https://git.kernel.org/stable/c/0069813e6ca9309eca78022bcb3aeb1e9ef90a12
https://git.kernel.org/stable/c/1e1f0f89ee4692a64be3f3707ff8ac1ae57b03e7
https://git.kernel.org/stable/c/7c66b368c6ff453f99cb39d84af93e908e51eef2
https://git.kernel.org/stable/c/085e31a811ef234ef8c3e219c4636dfebfe7e10f
https://git.kernel.org/stable/c/f996edd7615e686ada141b7f3395025729ff8ccb
reply other threads:[~2026-06-24 16:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026062448-CVE-2026-53006-2b02@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.