CVE-2022-49904: net, neigh: Fix null-ptr-deref in neigh_table_clear()
In the Linux kernel, the following vulnerability has been resolved:
net, neigh: Fix null-ptr-deref in neigh_table_clear()
When IPv6 module gets initialized but hits an error in the middle,
kenel panic with:
KASAN: null-ptr-deref in range [0x0000000000000598-0x000000000000059f]
CPU: 1 PID: 361 Comm: insmod
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996)
RIP: 0010:__neigh_ifdown.isra.0+0x24b/0x370
RSP: 0018:ffff888012677908 EFLAGS: 00000202
...
Call Trace:
<TASK>
neigh_table_clear+0x94/0x2d0
ndisc_cleanup+0x27/0x40 [ipv6]
inet6_init+0x21c/0x2cb [ipv6]
do_one_initcall+0xd3/0x4d0
do_init_module+0x1ae/0x670
...
Kernel panic - not syncing: Fatal exception
When ipv6 initialization fails, it will try to cleanup and calls:
neigh_table_clear()
neigh_ifdown(tbl, NULL)
pneigh_queue_purge(&tbl->proxy_queue, dev_net(dev == NULL))
# dev_net(NULL) triggers null-ptr-deref.
Fix it by passing NULL to pneigh_queue_purge() in neigh_ifdown() if dev
is NULL, to make kernel not panic immediately.
Security readout for executives and security teams
Plain-English summary
This Linux kernel flaw can cause a system crash during IPv6 module initialization failure cleanup. It affects availability, not confidentiality or integrity. The source bundle rates it medium with CVSS 5.5 because exploitation is local, needs privileges, and results in kernel panic rather than data compromise.
Executive priority
Treat this as a routine but important availability patch. It is not currently evidenced as internet-exploitable or actively exploited, but kernel panics can disrupt shared servers and critical workloads. Patch through normal kernel maintenance, with higher priority for multi-user Linux environments.
Technical view
A null pointer dereference occurs in neigh_table_clear() through neigh_ifdown(tbl, NULL), where dev_net(NULL) is reached while cleaning up after a failed IPv6 initialization path. The kernel fix changes cleanup behavior so pneigh_queue_purge() receives NULL when dev is NULL.
Likely exposure
Exposure is limited to Linux systems running affected kernel versions or unpatched backports, especially where local users or processes can trigger relevant IPv6 module initialization paths. Remote network-only exposure is not supported by the source bundle.
Exploitation context
The bundle does not show active exploitation, and KEV is false. Available evidence describes a local crash scenario observed through insmod and a failed IPv6 initialization path. No public weaponization details are included in the provided sources.
Researcher notes
Evidence is strongest for a null pointer dereference during IPv6 cleanup after initialization failure. The source bundle identifies stable kernel commits and CVSS AV:L/PR:L/A:H. It does not prove remote reachability, data exposure, privilege escalation, or real-world exploitation.
Mitigation direction
Update affected Linux kernels to vendor builds containing the stable fix.
Check distribution advisories for backported fixes matching the referenced kernel commits.
Prioritize multi-user systems and workloads where local code execution is available.
Restrict unnecessary local administrative access until patched.
Monitor for unexpected kernel panics around IPv6 module initialization.
Validation and detection
Inventory running Linux kernel versions across hosts.
Compare versions against affected ranges: 4.14.299 through 6.1 indicators in the bundle.
Confirm vendor kernel packages include the referenced stable fix or equivalent backport.
Review crash logs for neigh_table_clear, __neigh_ifdown, ndisc_cleanup, or inet6_init traces.
Validate production systems remain stable after kernel update and reboot.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-476: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-476 · source CWE mapping
NULL Pointer Dereference
NULL Pointer Dereference represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.