Bug 2492363 (CVE-2026-53006) - CVE-2026-53006 kernel: ipv6: fix possible UAF in icmpv6_rcv()
Summary: CVE-2026-53006 kernel: ipv6: fix possible UAF in icmpv6_rcv()
Keywords:
Status: NEW
Alias: CVE-2026-53006
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-06-24 18:07 UTC by OSIDB Bzimport
Modified: 2026-09-08 00:23 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2026:45192 0 None None None 2026-07-24 14:31:42 UTC
Red Hat Product Errata RHSA-2026:47010 0 None None None 2026-07-28 03:29:20 UTC
Red Hat Product Errata RHSA-2026:47011 0 None None None 2026-07-28 03:40:43 UTC
Red Hat Product Errata RHSA-2026:47017 0 None None None 2026-07-28 06:29:40 UTC
Red Hat Product Errata RHSA-2026:61932 0 None None None 2026-09-01 09:29:00 UTC
Red Hat Product Errata RHSA-2026:62568 0 None None None 2026-09-02 11:02:45 UTC
Red Hat Product Errata RHSA-2026:64767 0 None None None 2026-09-08 00:23:49 UTC

Description OSIDB Bzimport 2026-06-24 18:07:59 UTC 
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.
Comment 1 Keith Grant 2026-06-25 19:35:09 UTC 
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2026062448-CVE-2026-53006-2b02@gregkh/T
Comment 3 errata-xmlrpc 2026-07-24 14:31:41 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2026:45192 https://access.redhat.com/errata/RHSA-2026:45192
Comment 4 errata-xmlrpc 2026-07-28 03:29:19 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2026:47010 https://access.redhat.com/errata/RHSA-2026:47010
Comment 5 errata-xmlrpc 2026-07-28 03:40:42 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2026:47011 https://access.redhat.com/errata/RHSA-2026:47011
Comment 6 errata-xmlrpc 2026-07-28 06:29:39 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10

Via RHSA-2026:47017 https://access.redhat.com/errata/RHSA-2026:47017
Comment 7 errata-xmlrpc 2026-09-01 09:28:59 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8.8 Update Services for SAP Solutions
  Red Hat Enterprise Linux 8.8 Telecommunications Update Service

Via RHSA-2026:61932 https://access.redhat.com/errata/RHSA-2026:61932
Comment 8 errata-xmlrpc 2026-09-02 11:02:44 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9.6 Extended Update Support

Via RHSA-2026:62568 https://access.redhat.com/errata/RHSA-2026:62568
Comment 9 errata-xmlrpc 2026-09-08 00:23:48 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10.0 Extended Update Support

Via RHSA-2026:64767 https://access.redhat.com/errata/RHSA-2026:64767
Note You need to log in before you can comment on or make changes to this bug.