Linux Kernel up to 5.18.1 net/netfilter/core.c __nft_release_hooks privilege escalation

Summaryinfo

A vulnerability identified as problematic has been detected in Linux Kernel up to 5.18.1. Impacted is the function __nft_release_hooks of the file net/netfilter/core.c. Performing a manipulation results in an unknown weakness. This vulnerability is cataloged as CVE-2022-49558. There is no exploit available. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in Linux Kernel up to 5.18.1. It has been classified as problematic. This affects the function __nft_release_hooks of the file net/netfilter/core.c. The impact remains unknown. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: double hook unregistration in netns path __nft_release_hooks() is called from pre_netns exit path which unregisters the hooks, then the NETDEV_UNREGISTER event is triggered which unregisters the hooks again. [ 565.221461] WARNING: CPU: 18 PID: 193 at net/netfilter/core.c:495 __nf_unregister_net_hook+0x247/0x270 [...] [ 565.246890] CPU: 18 PID: 193 Comm: kworker/u64:1 Tainted: G E 5.18.0-rc7+ #27 [ 565.253682] Workqueue: netns cleanup_net [ 565.257059] RIP: 0010:__nf_unregister_net_hook+0x247/0x270 [...] [ 565.297120] Call Trace: [ 565.300900] [ 565.304683] nf_tables_flowtable_event+0x16a/0x220 [nf_tables] [ 565.308518] raw_notifier_call_chain+0x63/0x80 [ 565.312386] unregister_netdevice_many+0x54f/0xb50 Unregister and destroy netdev hook from netns pre_exit via kfree_rcu so the NETDEV_UNREGISTER path see unregistered hooks.

It is possible to read the advisory at git.kernel.org. This vulnerability is uniquely identified as CVE-2022-49558 since 02/26/2025. The exploitability is told to be difficult. Technical details of the vulnerability are known, but there is no available exploit.

The vulnerability scanner Nessus provides a plugin with the ID 271309 (EulerOS 2.0 SP13 : kernel (EulerOS-SA-2025-2264)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 4.19.316, 5.4.262, 5.10.198, 5.15.45, 5.17.13 or 5.18.2 eliminates this vulnerability. Applying the patch c73955a09408e7374d9abfd0e78ce3de9cda0635/b09e6ccf0d12f9356e8e3508d3e3dce126298538/3fac8ce48fa9fd61ee9056d3ed48b2edefca8b82/9c413a8c8bb49cc16796371805ecb260e885bb2b/a3940dcf552f2393d1e8f263b386593f98abe829/86c0154f4c3a56c5db8b9dd09e3ce885382c2c19/f9a43007d3f7ba76d5e7f9421094f00f2ef202f8 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the databases at Tenable (271309) and EUVD (EUVD-2022-54674). Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Type

• Operating System

Vendor

• Linux

Name

• Kernel

Version

• 4.19.315
• 5.4.261
• 5.10.197
• 5.15.0
• 5.15.1
• 5.15.2
• 5.15.3
• 5.15.4
• 5.15.5
• 5.15.6
• 5.15.7
• 5.15.8
• 5.15.9
• 5.15.10
• 5.15.11
• 5.15.12
• 5.15.13
• 5.15.14
• 5.15.15
• 5.15.16
• 5.15.17
• 5.15.18
• 5.15.19
• 5.15.20
• 5.15.21
• 5.15.22
• 5.15.23
• 5.15.24
• 5.15.25
• 5.15.26
• 5.15.27
• 5.15.28
• 5.15.29
• 5.15.30
• 5.15.31
• 5.15.32
• 5.15.33
• 5.15.34
• 5.15.35
• 5.15.36
• 5.15.37
• 5.15.38
• 5.15.39
• 5.15.40
• 5.15.41
• 5.15.42
• 5.15.43
• 5.15.44
• 5.17.0
• 5.17.1
• 5.17.2
• 5.17.3
• 5.17.4
• 5.17.5
• 5.17.6
• 5.17.7
• 5.17.8
• 5.17.9
• 5.17.10
• 5.17.11
• 5.17.12
• 5.18.0
• 5.18.1

License

• open-source

Website

• Vendor: https://www.kernel.org/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion