CVE-2026-68336: bonding: fix devconf_all NULL dereference when IPv6 is disabled
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.18% (FIRST EPSS).
- Fixed version: Linux Linux 1c975de3343cdef506f2eecc833cc1f14b0401c4, 2a4bad24ac5296b262ad821aa5e08bb265e6b154, 451c2d5422a309393aa8ae161fc1a527c2f19ab2; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.150.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 1c975de3343cdef506f2eecc833cc1f14b0401c4, 2a4bad24ac5296b262ad821aa5e08bb265e6b154, 451c2d5422a309393aa8ae161fc1a527c2f19ab2; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.150.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 10, 2026
- Updated
- Aug 19, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.18affected
- 4e24be018eb9dbcefa4b01c07e298b147dc1a4d7 and later · before 451c2d5422a309393aa8ae161fc1a527c2f19ab2affected · git
- 4e24be018eb9dbcefa4b01c07e298b147dc1a4d7 and later · before 2a4bad24ac5296b262ad821aa5e08bb265e6b154affected · git
- 4e24be018eb9dbcefa4b01c07e298b147dc1a4d7 and later · before 690ce66782778e8c4b1fdd79c0b0890a100e9522affected · git
- 4e24be018eb9dbcefa4b01c07e298b147dc1a4d7 and later · before 992dce02bdabbd9883255ea9b36494e34a7821d7affected · git
- 4e24be018eb9dbcefa4b01c07e298b147dc1a4d7 and later · before 738039ad21e20ca2c5bbde2f5a4f5ad5fb718038affected · git
- 4e24be018eb9dbcefa4b01c07e298b147dc1a4d7 and later · before 1c975de3343cdef506f2eecc833cc1f14b0401c4affected · git
- before 5.18not affected · semver
- 6.1.183 and later · up to and including 6.1.*not affected · semver
- 6.6.148 and later · up to and including 6.6.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.101-1~deb12u1 | 6.12.101-1~deb12u1 |
| Debian:13 | linux | before 6.12.101-1 | 6.12.101-1 |
| Debian:14 | linux | before 7.1.6-1 | 7.1.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-68333Aug 10, 2026 · dpaa2-switch: put MAC endpoint device on disconnect0Monitor
- ← EarlierCVE-2026-68334Aug 10, 2026 · rxrpc: fix io_thread race in rxrpc_wake_up_io_thread()0Monitor
- Later →CVE-2026-68337Aug 10, 2026 · bpf: Reject redirect helpers without a bpf_net_context0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1c975de3343cdef506f2eecc833cc1f14b0401c4 | Vendor (CNA) |
| Linux Linux | 2a4bad24ac5296b262ad821aa5e08bb265e6b154 | Vendor (CNA) |
| Linux Linux | 451c2d5422a309393aa8ae161fc1a527c2f19ab2 | Vendor (CNA) |
| Linux Linux | 690ce66782778e8c4b1fdd79c0b0890a100e9522 | Vendor (CNA) |
| Linux Linux | 738039ad21e20ca2c5bbde2f5a4f5ad5fb718038 | Vendor (CNA) |
| Linux Linux | 992dce02bdabbd9883255ea9b36494e34a7821d7 | Vendor (CNA) |
| azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 | 6.6.150.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.101-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0800 · Aug 11, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/2a4bad24ac5296b262ad821aa5e08bb265e6b154
- git.kernel.org/stable/c/451c2d5422a309393aa8ae161fc1a527c2f19ab2
- git.kernel.org/stable/c/690ce66782778e8c4b1fdd79c0b0890a100e9522
- git.kernel.org/stable/c/738039ad21e20ca2c5bbde2f5a4f5ad5fb718038
- git.kernel.org/stable/c/992dce02bdabbd9883255ea9b36494e34a7821d7
Vendor advisories and official records. Exploit/PoC links are deliberately left out.