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.
Metrics
Affected Vendors & Products
References
History
Mon, 19 Aug 2024 04:45:00 +0000
Type | Values Removed | Values Added |
---|---|---|
References |
|
Tue, 13 Aug 2024 23:00:00 +0000
Type | Values Removed | Values Added |
---|---|---|
CPEs | cpe:/a:redhat:rhel_e4s:9.0 |
Tue, 13 Aug 2024 06:30:00 +0000
Type | Values Removed | Values Added |
---|---|---|
CPEs | cpe:/a:redhat:rhel_e4s:9.0::nfv |
MITRE
Status: PUBLISHED
Assigner: Linux
Published: 2024-05-09T16:37:22.463Z
Updated: 2024-11-05T09:21:27.953Z
Reserved: 2024-02-25T13:47:42.677Z
Link: CVE-2024-27397
Vulnrichment
Updated: 2024-08-02T00:34:52.250Z
NVD
Status : Awaiting Analysis
Published: 2024-05-14T15:12:28.240
Modified: 2024-11-21T09:04:31.830
Link: CVE-2024-27397
Redhat