netfilter: nf_tables: make nft_object rhltable per table
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 4d44175aa5bb5f68772b1eb0306554812294ca52 · < 7d4789b58761d9d48d9b5f5e7e0a510c3bbfb3af| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
netfilter: nf_tables: make nft_object rhltable per table
The nft_object rhltable is global, this allows for accessing objects that are being dismangled from lookup path by other existing netns. Given the nft_obj_destroy() releases the object inmediately, this might lead to use-after-free of these objects that are being released. Make the existing rhltable per table to address this issue to deal with with the nft_rcv_nl_event() path too.
Update nft_obj_lookup() to take the table as non-const, otherwise, compiler complains when passing the objname_ht to rhltable_lookup().
From the CVE record · Linux
A global nft_object lookup table in the Linux kernel's netfilter nf_tables can let an existing network namespace access objects being removed by another. Because those objects are freed immediately, this may cause a use-after-free. The input does not specify authentication or user-interaction requirements.
Teams running Linux kernels with netfilter nf_tables should check their deployments; affected versions are not specified.