CVE-2026-53006 — Kernel
CRITICALCVE-2026-53006 is a critical-severity (CVSS 9.8) Use After Free vulnerability in Kernel. A fix is available for Kernel — see the affected versions and patch details below.
ipv6: fix possible UAF in icmpv6_rcv()
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2026-53006 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,987 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
KernelReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Linux packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐧Linux | Kernel | ≥ 4.4.0&&< 5.10.258 | 5.10.258 |
Affected Products
linux kernellinuxenterprise linuxredhatDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Kernel, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update Kernel to 5.10.258 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-53006 is resolved across your whole dependency graph.
Workarounds
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Enterprise Linux 10 | kernel-0:6.12.0-211.40.1.el10_2 | RHSA-2026:47017 |
| Red Hat Enterprise Linux 10.0 Extended Update Support | kernel-0:6.12.0-55.103.1.el10_0 | RHSA-2026:64767 |
| Red Hat Enterprise Linux 8 | kernel-rt-0:4.18.0-553.148.1.rt7.489.el8_10 | RHSA-2026:47010 |
| Red Hat Enterprise Linux 8 | kernel-0:4.18.0-553.148.1.el8_10 | RHSA-2026:47011 |
| Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support | kernel-0:4.18.0-305.206.1.el8_4 | RHSA-2026:65710 |
| Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support | kernel-0:4.18.0-372.213.1.el8_6 | RHSA-2026:65711 |
| Red Hat Enterprise Linux 8.8 Telecommunications Update Service | kernel-0:4.18.0-477.163.1.el8_8 | RHSA-2026:61932 |
| Red Hat Enterprise Linux 9 | kernel-0:5.14.0-687.30.1.el9_8 | RHSA-2026:45192 |
Frequently Asked Questions
Is CVE-2026-53006 in your dependencies?
Find it across Linux, including transitive dependencies.