net: openvswitch: conntrack: fix helper UAF due to extensions realloc
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ cae3a2627520c3795b54533c5328b77af3405dbe · < 5f23080a625dd7855ab91485c8d691a54a1979f0| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
net: openvswitch: conntrack: fix helper UAF due to extensions realloc
While calling the helpers, a raw pointer to the extensions area is wired into expectations list:
-> nf_ct_helper() -> helper->help() -> nf_ct_expect_related_report() -> nf_ct_expect_insert() -> hlist_add_head_rcu(&exp->lnode, &master_help->expectations)
In case the connection is not confirmed yet, more extensions can be added afterwards with *_ext_add() calls reallocating the extension space and leaving the now invalid pointer in the expectations list that is later accessed while removing the expectation.
Make sure that helpers are called at the end after all the other extensions are already added.
Note that the helper rejection now leaves the mark and labels set, but that's not different from how the NAT was handled before or how the mark and the labels were handled on confirmation failure. And there are no atomicity guarantees provided by the API anyway.
From the CVE record · Linux
The Linux kernel’s Open vSwitch conntrack code can leave an invalid pointer in an expectations list when adding extensions reallocates memory after a helper runs. Accessing that pointer later can cause a use-after-free. The input does not specify attack access requirements, authentication needs, or user interaction.
Engineers running Linux kernels with Open vSwitch conntrack should check the vendor advisory for affected versions; none are listed in the input.