Kernel panic via IPv6 cleanup null dereference
Published May 1, 2025 · Updated May 23, 2026
NULL pointer dereference in affected Linux kernel releases allows local users to crash the system during failed IPv6 initialization. neigh_ifdown passes a null device into dev_net while neigh_table_clear purges the proxy queue, dereferencing the null pointer. Exploitation requires local low-privilege access and a failing IPv6 module initialization path; the bounded impact is a kernel panic.
Summary
What happened
NULL pointer dereference in affected Linux kernel releases allows local users to crash the system during failed IPv6 initialization. neigh_ifdown passes a null device into dev_net while neigh_table_clear purges the proxy queue, dereferencing the null pointer. Exploitation requires local low-privilege access and a failing IPv6 module initialization path; the bounded impact is a kernel panic.
The record
- CVE
- CVE-2022-49904
- Published
- May 1, 2025
- Updated
- May 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 1, 2025CVE publishedPublication date reported by the CVE source.
- May 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=05fdce1ae744dee43c9181fd063c9c0db4f777f2 <b736592de2aa53aee2d48d6b129bc0c892007bbe
- Affected versionversion=2dd5ed474115150d8175825bc3b56c6385c3a83b
- Affected versionversion=4.14.292 <4.14.299
- Affected versionversion=4.19.257 <4.19.265
- Affected versionversion=5.10.141 <5.10.154
- Affected versionversion=5.15.65 <5.15.78
- Affected versionversion=5.19.7 <5.20
- Affected versionversion=51be9dd391fd25872b95708a0250f2f7722d2d8e <b49f6b2f21f543d4dc88fb7b1ec2adccb822f27c
- Affected versionversion=5.4.212 <5.4.224
- Affected versionversion=6.0
- Affected versionversion=66ba215cb51323e4e55e38fd5f250e0fae0cbc94 <a99a8ec4c62180c889482a2ff6465033e0743458
- Affected versionversion=66ba215cb51323e4e55e38fd5f250e0fae0cbc94 <f8017317cb0b279b8ab98b0f3901a2e0ac880dad
- Affected versionversion=9bbaed571c4bf1b62ac8703cb359dc090efc3455 <0d38b4ca6679e72860ff8730e79bb99d0e9fa3b0
- Affected versionversion=c35adafe42bd6c3bf2aca0a3f523dabc38fc23c8 <1c89642e7f2b7ecc9635610653f5c2f0276c0051
- Affected versionversion=db6fa03d80ab076238fc806c9925d1f8b9639d1b <2b45d6d0c41cb9593868e476681efb1aae5078a1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo