high CVSS 7.8

CVE-2022-49667·Kernel vulnerability

In the Linux kernel, the following vulnerability has been resolved: net: bonding: fix use-after-free after 802.3ad slave unbind commit 0622cab0341c ("bonding: fix 802.3ad aggregator reselection"), resolve case, when there is several aggregation groups in the same bond. bond_3ad_unbind_slave will invalidate (clear) aggregator when __agg_active_ports return zero. So, ad_clear_agg can be executed even, when num_of_ports!=0. Than bond_3ad_unbind_slave can be executed again for, previously cleared aggregator. NOTE: at this time bond_3ad_unbind_slave will not update slave ports list, because lag_ports==NULL. So, here we got slave ports, pointing to freed aggregator memory. Fix with checking actual number of ports in group (as was before commit 0622cab0341c ("bonding: fix 802.3ad aggregator reselection") ), before ad_clear_agg(). The KASAN logs are as follows: [ 767.617392] ================================================================== [ 767.630776] BUG: KASAN: use-after-free in bond_3ad_state_machine_handler+0x13dc/0x1470 [ 767.638764] Read of size 2 at addr ffff00011ba9d430 by task kworker/u8:7/767 [ 767.647361] CPU: 3 PID: 767 Comm: kworker/u8:7 Tainted: G O 5.15.11 #15 [ 767.655329] Hardware name: DNI AmazonGo1 A7040 board (DT) [ 767.660760] Workqueue: lacp_1 bond_3ad_state_machine_handler [ 767.666468] Call trace: [ 767.668930] dump_backtrace+0x0/0x2d0 [ 767.672625] show_stack+0x24/0x30 [ 767.675965] dump_stack_lvl+0x68/0x84 [ 767.679659] print_address_description.constprop.0+0x74/0x2b8 [ 767.685451] kasan_report+0x1f0/0x260 [ 767.689148] __asan_load2+0x94/0xd0 [ 767.692667] bond_3ad_state_machine_handler+0x13dc/0x1470

Severity
high
Software
Kernel
Fixed in
5.18.10
Published
2025-02-26

Affected versions

From: 5.16

Until: 5.18.10

Fixed in: 5.18.10

How to fix this CVE

Update your Linux kernel to version 5.18.10 or later to resolve a use-after-free vulnerability in the 802.3ad bonding driver. This flaw occurs when slave interfaces are unbound from a bonded group, causing the aggregator to be prematurely cleared while ports still reference freed memory. Apply the patch immediately if you use network bonding on your systems.

sudo dnf update kernel kernel-devel

Defensia detects this vulnerability

How to check if you are affected

  1. Check installed kernel version: uname -r — verify it is 5.18.10 or later, or an earlier stable branch with the backport
  2. Verify bonding driver is loaded: lsmod | grep bonding — if output is empty, this CVE does not apply to your system
  3. Check active bonding interfaces: cat /proc/net/bonding/bond* — confirm if 802.3ad mode is in use (Mode: 802.3ad)
  4. Search kernel logs for KASAN warnings: sudo dmesg | grep -i 'use-after-free\|bond_3ad\|kasan' — presence indicates possible exploitation or memory corruption events
  5. Verify patch applied: grep -r '0622cab0341c' /boot/ || grep 'ad_clear_agg' /boot/config-$(uname -r) — confirms if the specific fix is present

FAQ

What is CVE-2022-49667?

This is a use-after-free memory corruption vulnerability in the Linux kernel's 802.3ad bonding driver. When slave interfaces are unbound from a bonded group, a premature aggregator clearing can occur, leaving slave port structures pointing to freed memory that may be later accessed by the state machine handler.

Is CVE-2022-49667 being actively exploited?

No, this vulnerability is not listed in the CISA Known Exploited Vulnerabilities catalog and no public exploits are available. However, it can cause kernel crashes and memory corruption on affected systems using bonded network interfaces.

What versions of Kernel are affected by CVE-2022-49667?

Linux kernel versions 5.16 through 5.18.9 are vulnerable. The fix was included in 5.18.10 and backported to stable branches 5.17.x and 5.15.x.

How do I check if my server is vulnerable to CVE-2022-49667?

Run: uname -r && lsmod | grep bonding — if your kernel version is between 5.16 and 5.18.9 AND bonding is loaded, you are vulnerable. Confirm 802.3ad mode with: cat /proc/net/bonding/bond0

Does Defensia detect CVE-2022-49667?

Yes — Defensia's CVE advisory scanner compares installed kernel versions against the NVD database. If Linux kernel is installed on a monitored server and the version falls within the vulnerable range (5.16-5.18.9), CVE-2022-49667 will appear in your dashboard with remediation steps and affected interface details.

Related Kernel CVEs

CVE-2024-42256CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: cifs: Fix server re-repick on subrequest retry When a subrequest is marked for needing retry, netfs will call cifs_prepare_write() which will make cifs repick the server for the op before renegotiating credits; it then calls cifs_issue_write() which invokes smb2_async_writev() - which re-repicks the server. If a different server is then selected, this causes the increment of server->in_flight to happen against one record and the decrement to happen against another, leading to misaccounting. Fix this by just removing the repick code in smb2_async_writev(). As this is only called from netfslib-driven code, cifs_prepare_write() should always have been called first, and so server should never be NULL and the preparatory step is repeated in the event that we do a retry. The problem manifests as a warning looking something like: WARNING: CPU: 4 PID: 72896 at fs/smb/client/smb2ops.c:97 smb2_add_credits+0x3f0/0x9e0 [cifs] ... RIP: 0010:smb2_add_credits+0x3f0/0x9e0 [cifs] ... smb2_writev_callback+0x334/0x560 [cifs] cifs_demultiplex_thread+0x77a/0x11b0 [cifs] kthread+0x187/0x1d0 ret_from_fork+0x34/0x60 ret_from_fork_asm+0x1a/0x30 Which may be triggered by a number of different xfstests running against an Azure server in multichannel mode. generic/249 seems the most repeatable, but generic/215, generic/249 and generic/308 may also show it.
CVE-2024-36031CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: keys: Fix overwrite of key expiration on instantiation The expiry time of a key is unconditionally overwritten during instantiation, defaulting to turn it permanent. This causes a problem for DNS resolution as the expiration set by user-space is overwritten to TIME64_MAX, disabling further DNS updates. Fix this by restoring the condition that key_set_expiry is only called when the pre-parser sets a specific expiry.
CVE-2024-38612CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: ipv6: sr: fix invalid unregister error path The error path of seg6_init() is wrong in case CONFIG_IPV6_SEG6_LWTUNNEL is not defined. In that case if seg6_hmac_init() fails, the genl_unregister_family() isn't called. This issue exist since commit 46738b1317e1 ("ipv6: sr: add option to control lwtunnel support"), and commit 5559cea2d5aa ("ipv6: sr: fix possible use-after-free and null-ptr-deref") replaced unregister_pernet_subsys() with genl_unregister_family() in this error path.
CVE-2024-38623CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: Use variable length array instead of fixed size Should fix smatch warning: ntfs_set_label() error: __builtin_memcpy() 'uni->name' too small (20 vs 256)
CVE-2021-47548CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: ethernet: hisilicon: hns: hns_dsaf_misc: fix a possible array overflow in hns_dsaf_ge_srst_by_port() The if statement: if (port >= DSAF_GE_NUM) return; limits the value of port less than DSAF_GE_NUM (i.e., 8). However, if the value of port is 6 or 7, an array overflow could occur: port_rst_off = dsaf_dev->mac_cb[port]->port_rst_off; because the length of dsaf_dev->mac_cb is DSAF_MAX_PORT_NUM (i.e., 6). To fix this possible array overflow, we first check port and if it is greater than or equal to DSAF_MAX_PORT_NUM, the function returns.

References

Track CVEs across your fleet automatically

Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2022-49667. Free for 1 server.

Get started free