CVE-2024-35886 in Linux
Sumário
de VulDB • 19/06/2026
No, this is not a kernel panic.
This is a **kernel oops** (specifically, a **NULL pointer dereference** or similar invalid memory access) that occurred in the IPv6 forwarding information base (FIB) code during netlink socket destruction.
### Key Evidence: 1. **RIP points to `fib6_dump_done`**: The instruction pointer (`RIP`) is at `net/ipv6/ip6_fib.c:570`, which is inside the `fib6_dump_done` function. This function is called when a netlink dump (e.g., for `ip -6 route`) is completed. 2. **Call Trace**: The trace shows the crash happened during `netlink_sock_destruct_work`, which is part of cleaning up a netlink socket. The recursion in `fib6_dump_done` (shown as repeated calls) suggests a potential stack overflow or infinite recursion due to a bug in how the dump is being finalized. 3. **No "Kernel panic - not syncing"**: A kernel panic would explicitly state that. An oops is a recoverable error (in theory), though it often leads to system instability or a forced reboot if critical. 4. **Workqueue Context**: The crash occurred in a workqueue (`events`), which is common for deferred cleanup tasks.
### Likely Cause: This looks like a **bug in the IPv6 FIB dump cleanup code**, possibly triggered by: - A race condition during netlink socket destruction. - Corrupted or invalid pointers in the FIB dump context. - A known issue in older kernels (the BIOS date suggests an older QEMU environment, but the kernel version isn't specified).
### Recommendation: 1. **Check kernel logs** (`dmesg`) for more context before and after the oops. 2. **Update the kernel** if possible, as this may be a known bug fixed in newer versions. 3. **Avoid triggering the dump** (e.g., `ip -6 route`) during heavy network changes or socket teardown if this is reproducible. 4. If this is in a production environment, consider **rebooting** if the system is unstable, as oopses can leave the kernel in an inconsistent state.
This is a **bug**, not a panic, but it should be investigated and fixed.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.