CVE-2026-68336
bonding: fix devconf_all NULL dereference when IPv6 is disabled
In the Linux kernel, the following vulnerability has been resolved: bonding: fix devconf_all NULL dereference when IPv6 is disabled When booting with the 'ipv6.disable=1' parameter, the devconf_all is never initialized because inet6_init() exits before addrconf_init() is called which initializes it. bond_send_validate(), however, will still call bond_ns_send_all() even ipv6 is indeed disabled. It will lead to NULL derefence of net->ipv6.devconf_all in ip6_pol_route(). BUG: kernel NULL pointer dereference, address: 000000000000000c [...] Workqueue: bond0 bond_arp_monitor [bonding] RIP: 0010:ip6_pol_route+0x69/0x480 [...] Call Trace: <TASK> ? srso_return_thunk+0x5/0x5f ? __pfx_ip6_pol_route_output+0x10/0x10 fib6_rule_lookup+0xfe/0x260 ? wakeup_preempt+0x8a/0x90 ? srso_return_thunk+0x5/0x5f ? srso_return_thunk+0x5/0x5f ? sched_balance_rq+0x369/0x810 ip6_route_output_flags+0xd7/0x170 bond_ns_send_all+0xde/0x280 [bonding] bond_ab_arp_probe+0x296/0x320 [bonding] ? srso_return_thunk+0x5/0x5f bond_activebackup_arp_mon+0xb4/0x2c0 [bonding] process_one_work+0x196/0x370 worker_thread+0x1af/0x320 ? srso_return_thunk+0x5/0x5f ? __pfx_worker_thread+0x10/0x10 kthread+0xe3/0x120 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x199/0x260 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> Fix this by adding ipv6_mod_enabled() condition check in the caller.
Fixes and workarounds
No remediation reported in collected sources.
Missing remediation information is not evidence that no patch exists.
Affected products and versions
| Product | Versions | Authority |
|---|---|---|
| Linux Linux |
≥ 4e24be018eb9dbcefa4b01c07e298b147dc1a4d7; < 451c2d5422a309393aa8ae161fc1a527c2f19ab2 (affected, git) ≥ 4e24be018eb9dbcefa4b01c07e298b147dc1a4d7; < 2a4bad24ac5296b262ad821aa5e08bb265e6b154 (affected, git) ≥ 4e24be018eb9dbcefa4b01c07e298b147dc1a4d7; < 690ce66782778e8c4b1fdd79c0b0890a100e9522 (affected, git) ≥ 4e24be018eb9dbcefa4b01c07e298b147dc1a4d7; < 992dce02bdabbd9883255ea9b36494e34a7821d7 (affected, git) ≥ 4e24be018eb9dbcefa4b01c07e298b147dc1a4d7; < 738039ad21e20ca2c5bbde2f5a4f5ad5fb718038 (affected, git) ≥ 4e24be018eb9dbcefa4b01c07e298b147dc1a4d7; < 1c975de3343cdef506f2eecc833cc1f14b0401c4 (affected, git) Other versions: unaffected |
CNA: Linux |
| Linux Linux |
5.18 (affected) ≥ 0; < 5.18 (unaffected, semver) ≥ 6.1.183; ≤ 6.1.* (unaffected, semver) ≥ 6.6.148; ≤ 6.6.* (unaffected, semver) ≥ 6.12.101; ≤ 6.12.* (unaffected, semver) ≥ 6.18.42; ≤ 6.18.* (unaffected, semver) ≥ 7.1.6; ≤ 7.1.* (unaffected, semver) ≥ 7.2; ≤ * (unaffected, original_commit_for_fix) Other versions: affected |
CNA: Linux |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
No CVSS assessment reported. An unscored record is not a low-severity determination.
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://git.kernel.org/stable/c/451c2d5422a309393aa8ae161fc1a527c2f19ab2CNA: Linux
- https://git.kernel.org/stable/c/2a4bad24ac5296b262ad821aa5e08bb265e6b154CNA: Linux
- https://git.kernel.org/stable/c/690ce66782778e8c4b1fdd79c0b0890a100e9522CNA: Linux
- https://git.kernel.org/stable/c/992dce02bdabbd9883255ea9b36494e34a7821d7CNA: Linux
- https://git.kernel.org/stable/c/738039ad21e20ca2c5bbde2f5a4f5ad5fb718038CNA: Linux
- https://git.kernel.org/stable/c/1c975de3343cdef506f2eecc833cc1f14b0401c4CNA: Linux
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.