netfilter: nf_tables: use timestamp to check for set element timeout
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 0d40e8cb1d1f56a994cdd2e015af622fdca9ed4d, Kernel 383182db8d58c4237772ba0764cded4938a235c3, Kernel 7395dfacfff65e9938ac0889dafa1ab01e987d15 and 5 more.
In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: use timestamp to check for set element timeout Add a timestamp field at the beginning of the transaction, store it in the nftables per-netns area. Update set backend .insert, .deactivate and sync gc path to use the timestamp, this avoids that an element expires while control plane transaction is still unfinished. .lookup and .update, which are used from packet path, still use the current time to check if the element has expired. And .get path and dump also since this runs lockless under rcu read size lock. Then, there is async gc which also needs to check the current time since it runs asynchronously from a workqueue.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =4.1, >=c3e1b005ed1cc068fc9d454a6e745830d55d251d <0d40e8cb1d1f56a994cdd2e015af622fdca9ed4d, >=c3e1b005ed1cc068fc9d454a6e745830d55d251d <383182db8d58c4237772ba0764cded4938a235c3, >=c3e1b005ed1cc068fc9d454a6e745830d55d251d <7395dfacfff65e9938ac0889dafa1ab01e987d15, >=c3e1b005ed1cc068fc9d454a6e745830d55d251d <7b17de2a71e56c10335b565cc7ad238e6d984379, >=c3e1b005ed1cc068fc9d454a6e745830d55d251d <7fa2e2960fff8322ce2ded57b5f8e9cbc450b967, >=c3e1b005ed1cc068fc9d454a6e745830d55d251d <b45176b869673417ace338b87cf9cdb66e2eeb01, >=c3e1b005ed1cc068fc9d454a6e745830d55d251d <eaf1a29ea5d7dba8e84e9e9f3b3f47d0cd540bfe, >=c3e1b005ed1cc068fc9d454a6e745830d55d251d <f8dfda798650241c1692058713ca4fef8e429061 | 0d40e8cb1d1f56a994cdd2e015af622fdca9ed4d, 383182db8d58c4237772ba0764cded4938a235c3, 7395dfacfff65e9938ac0889dafa1ab01e987d15, 7b17de2a71e56c10335b565cc7ad238e6d984379, 7fa2e2960fff8322ce2ded57b5f8e9cbc450b967, b45176b869673417ace338b87cf9cdb66e2eeb01, eaf1a29ea5d7dba8e84e9e9f3b3f47d0cd540bfe, f8dfda798650241c1692058713ca4fef8e429061 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket