Linux
bpf: Fix netns reference imbalance in conntrack kfuncs
In the Linux kernel, the following vulnerability has been resolved: bpf: Fix netns reference imbalance in conntrack kfuncs The opts argument of the BPF conntrack kfuncs can point to a shared map value. __bpf_nf_ct_lookup() and __bpf_nf_ct_alloc_entry() read opts->netns_id separately when acquiring and releasing the network namespace reference. The reference imbalance can occur as follows: CPU 0 CPU 1 read opts->netns_id (-1) skip get_net_ns_by_id() write opts->netns_id (id) read opts->netns_id (id) put_net(net) /* no matching get */ The reverse transition leaks the reference. Repeating the unmatched put can destroy a live namespace and crash later users. The kernel reported: Oops: general protection fault, probably for non-canonical address KASAN: null-ptr-deref in range [0x00000000000000e8-0x00000000000000ef] RIP: 0010:bpf_prog_test_run_xdp+0x52c/0x1700 Call Trace: __sys_bpf+0x1662/0x50c0 __x64_sys_bpf+0x73/0xb0 do_syscall_64+0xf9/0x540 entry_SYSCALL_64_after_hwframe+0x77/0x7f Kernel panic - not syncing: Fatal exception Snapshot every input field of opts with READ_ONCE() before validating or using it. The netns_id snapshot keeps the namespace get/put pair balanced, while the other snapshots keep the remaining options from changing partway through an invocation. The individual reads can still observe an inconsistent combination during a concurrent update, but each selected field value remains stable for that invocation.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= aed8ee7feb44b6537af1e0b4f03365d42928be38, < cfde990193135a35637e55f69e83e4ab441e60ab
- >= aed8ee7feb44b6537af1e0b4f03365d42928be38, < fb22bedf0c4f4f05bfa6e4a7ec0fd97bbdff9ce8
- >= aed8ee7feb44b6537af1e0b4f03365d42928be38, < 41731d4290400cb898f15f049ae4018d45415e69
- >= aed8ee7feb44b6537af1e0b4f03365d42928be38, < 4af94462c0ca2187a02a1a6641020ae888c74d5c
- >= aed8ee7feb44b6537af1e0b4f03365d42928be38, < e5e060eb63d10b41ab60fd955649479d99b38210
- >= aed8ee7feb44b6537af1e0b4f03365d42928be38, < fdeba03fea78407a8c52faa99177c9f7f29f90eb
Fixed in cfde990193135a35637e55f69e83e4ab441e60ab, fb22bedf0c4f4f05bfa6e4a7ec0fd97bbdff9ce8, 41731d4290400cb898f15f049ae4018d45415e69, 4af94462c0ca2187a02a1a6641020ae888c74d5c, e5e060eb63d10b41ab60fd955649479d99b38210, fdeba03fea78407a8c52faa99177c9f7f29f90eb
- 6.0
Fixed in 0, 6.1.191, 6.6.160, 6.12.114, 6.18.57, 7.1.9, 7.2
Mitigation
Upgrade Linux to cfde990193135a35637e55f69e83e4ab441e60ab or fb22bedf0c4f4f05bfa6e4a7ec0fd97bbdff9ce8 or 41731d4290400cb898f15f049ae4018d45415e69 or 4af94462c0ca2187a02a1a6641020ae888c74d5c or e5e060eb63d10b41ab60fd955649479d99b38210 or fdeba03fea78407a8c52faa99177c9f7f29f90eb or later.
Upgrade Linux to 0 or 6.1.191 or 6.6.160 or 6.12.114 or 6.18.57 or 7.1.9 or 7.2 or later.
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.