CVE-2026-68336: bonding: fix devconf_all NULL dereference when IPv6 is disabled

Published Aug 10, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

bonding: fix devconfall NULL dereference when IPv6 is disabled

When booting with the 'ipv6.disable=1' parameter, the devconfall is never initialized because inet6init() exits before addrconfinit() is called which initializes it. bondsendvalidate(), however, will still call bondnssendall() even ipv6 is indeed disabled. It will lead to NULL derefence of net->ipv6.devconfall in ip6polroute().

BUG: kernel NULL pointer dereference, address: 000000000000000c [...] Workqueue: bond0 bondarpmonitor [bonding] RIP: 0010:ip6polroute+0x69/0x480 [...] Call Trace: <TASK> ? srsoreturnthunk+0x5/0x5f ? pfxip6polrouteoutput+0x10/0x10 fib6rulelookup+0xfe/0x260 ? wakeuppreempt+0x8a/0x90 ? srsoreturnthunk+0x5/0x5f ? srsoreturnthunk+0x5/0x5f ? schedbalancerq+0x369/0x810 ip6routeoutputflags+0xd7/0x170 bondnssendall+0xde/0x280 [bonding] bondabarpprobe+0x296/0x320 [bonding] ? srsoreturnthunk+0x5/0x5f bondactivebackuparpmon+0xb4/0x2c0 [bonding] processonework+0x196/0x370 workerthread+0x1af/0x320 ? srsoreturnthunk+0x5/0x5f ? pfxworkerthread+0x10/0x10 kthread+0xe3/0x120 ? pfxkthread+0x10/0x10 retfromfork+0x199/0x260 ? pfxkthread+0x10/0x10 retfromforkasm+0x1a/0x30 </TASK>

Fix this by adding ipv6modenabled() condition check in the caller.

Affected Software

1 affected component
Linux Kernel

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    If you boot with 'ipv6.disable=1', ensure the caller of ip6_pol_route() includes an ipv6_mod_enabled() condition check before dereferencing net->ipv6.devconf_all (fix for kernel NULL pointer dereference at ip6_pol_route()).

    Linux kernel ipv6.disable = 1

Event History

Aug 10, 2026
CVE Published
via MITRE·12:03 PM
Data Sourced
via MITRE·12:03 PM
Description
Data Sourced
via NVD·01:20 PM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-68336?

CVE-2026-68336 has a risk score of 22, indicating a significant impact due to a NULL pointer dereference.

2

How do I fix CVE-2026-68336?

To fix CVE-2026-68336, ensure that you are using an updated version of the Linux kernel where the vulnerability has been patched.

3

What systems are affected by CVE-2026-68336?

CVE-2026-68336 affects systems running affected versions of the Linux kernel with the IPv6 disabled parameter.

4

What type of vulnerability is CVE-2026-68336?

CVE-2026-68336 is categorized as a Null Pointer Dereference vulnerability.

5

What happens if CVE-2026-68336 is exploited?

Exploitation of CVE-2026-68336 can lead to system instability or crashes when IPv6 is disabled.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203