What is the severity of CVE-2021-47246?

CVE-2021-47246 is classified as a medium severity vulnerability in the Linux kernel due to potential memory management issues.

How do I fix CVE-2021-47246?

To fix CVE-2021-47246, update your Linux kernel to a version that includes the security patch addressing this vulnerability.

Which Linux kernel versions are affected by CVE-2021-47246?

CVE-2021-47246 affects Linux kernel versions from 4.19 to 5.12.x and specific release candidates of 5.13.

What type of vulnerability is CVE-2021-47246?

CVE-2021-47246 is a vulnerability related to memory management in the Linux kernel, specifically involving page reclaim for dead peer hairpin.

Is there a workaround for CVE-2021-47246 if I cannot update the kernel?

There is no widely known workaround for CVE-2021-47246, and the recommended action is to patch your kernel as soon as possible.

Vulnerability/
CVE-2021-47246

medium

5.5

CWE

401

21/5/2024

29/4/2025

CVE-2021-47246: net/mlx5e: Fix page reclaim for dead peer hairpin

First published: Tue May 21 2024(Updated: )

In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Fix page reclaim for dead peer hairpin When adding a hairpin flow, a firmware-side send queue is created for the peer net device, which claims some host memory pages for its internal ring buffer. If the peer net device is removed/unbound before the hairpin flow is deleted, then the send queue is not destroyed which leads to a stack trace on pci device remove: [ 748.005230] mlx5_core 0000:08:00.2: wait_func:1094:(pid 12985): MANAGE_PAGES(0x108) timeout. Will cause a leak of a command resource [ 748.005231] mlx5_core 0000:08:00.2: reclaim_pages:514:(pid 12985): failed reclaiming pages: err -110 [ 748.001835] mlx5_core 0000:08:00.2: mlx5_reclaim_root_pages:653:(pid 12985): failed reclaiming pages (-110) for func id 0x0 [ 748.002171] ------------[ cut here ]------------ [ 748.001177] FW pages counter is 4 after reclaiming all pages [ 748.001186] WARNING: CPU: 1 PID: 12985 at drivers/net/ethernet/mellanox/mlx5/core/pagealloc.c:685 mlx5_reclaim_startup_pages+0x34b/0x460 [mlx5_core] [ +0.002771] Modules linked in: cls_flower mlx5_ib mlx5_core ptp pps_core act_mirred sch_ingress openvswitch nsh xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xt_addrtype iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter rpcrdma rdma_ucm ib_iser libiscsi scsi_transport_iscsi rdma_cm ib_umad ib_ipoib iw_cm ib_cm ib_uverbs ib_core overlay fuse [last unloaded: pps_core] [ 748.007225] CPU: 1 PID: 12985 Comm: tee Not tainted 5.12.0+ #1 [ 748.001376] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 [ 748.002315] RIP: 0010:mlx5_reclaim_startup_pages+0x34b/0x460 [mlx5_core] [ 748.001679] Code: 28 00 00 00 0f 85 22 01 00 00 48 81 c4 b0 00 00 00 31 c0 5b 5d 41 5c 41 5d 41 5e 41 5f c3 48 c7 c7 40 cc 19 a1 e8 9f 71 0e e2 <0f> 0b e9 30 ff ff ff 48 c7 c7 a0 cc 19 a1 e8 8c 71 0e e2 0f 0b e9 [ 748.003781] RSP: 0018:ffff88815220faf8 EFLAGS: 00010286 [ 748.001149] RAX: 0000000000000000 RBX: ffff8881b4900280 RCX: 0000000000000000 [ 748.001445] RDX: 0000000000000027 RSI: 0000000000000004 RDI: ffffed102a441f51 [ 748.001614] RBP: 00000000000032b9 R08: 0000000000000001 R09: ffffed1054a15ee8 [ 748.001446] R10: ffff8882a50af73b R11: ffffed1054a15ee7 R12: fffffbfff07c1e30 [ 748.001447] R13: dffffc0000000000 R14: ffff8881b492cba8 R15: 0000000000000000 [ 748.001429] FS: 00007f58bd08b580(0000) GS:ffff8882a5080000(0000) knlGS:0000000000000000 [ 748.001695] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 748.001309] CR2: 000055a026351740 CR3: 00000001d3b48006 CR4: 0000000000370ea0 [ 748.001506] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 748.001483] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 748.001654] Call Trace: [ 748.000576] ? mlx5_satisfy_startup_pages+0x290/0x290 [mlx5_core] [ 748.001416] ? mlx5_cmd_teardown_hca+0xa2/0xd0 [mlx5_core] [ 748.001354] ? mlx5_cmd_init_hca+0x280/0x280 [mlx5_core] [ 748.001203] mlx5_function_teardown+0x30/0x60 [mlx5_core] [ 748.001275] mlx5_uninit_one+0xa7/0xc0 [mlx5_core] [ 748.001200] remove_one+0x5f/0xc0 [mlx5_core] [ 748.001075] pci_device_remove+0x9f/0x1d0 [ 748.000833] device_release_driver_internal+0x1e0/0x490 [ 748.001207] unbind_store+0x19f/0x200 [ 748.000942] ? sysfs_file_ops+0x170/0x170 [ 748.001000] kernfs_fop_write_iter+0x2bc/0x450 [ 748.000970] new_sync_write+0x373/0x610 [ 748.001124] ? new_sync_read+0x600/0x600 [ 748.001057] ? lock_acquire+0x4d6/0x700 [ 748.000908] ? lockdep_hardirqs_on_prepare+0x400/0x400 [ 748.001126] ? fd_install+0x1c9/0x4d0 [ 748.000951] vfs_write+0x4d0/0x800 [ 748.000804] ksys_write+0xf9/0x1d0 [ 748.000868] ? __x64_sys_read+0xb0/0xb0 [ 748.000811] ? filp_open+0x50/0x50 [ 748.000919] ? syscall_enter_from_user_mode+0x1d/0x50 [ 748.001223] do_syscall_64+0x3f/0x80 [ 748.000892] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 748.00 ---truncated---

Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Affected Software	Affected Version	How to fix
Red Hat Kernel-devel
Linux Kernel	>=4.19<5.4.128
Linux Kernel	>=5.5<5.10.46
Linux Kernel	>=5.11<5.12.13
Linux Kernel	=5.13-rc1
Linux Kernel	=5.13-rc2
Linux Kernel	=5.13-rc3
Linux Kernel	=5.13-rc4
Linux Kernel	=5.13-rc5
Linux Kernel	=5.13-rc6

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2021-47246?
CVE-2021-47246 is classified as a medium severity vulnerability in the Linux kernel due to potential memory management issues.
How do I fix CVE-2021-47246?
To fix CVE-2021-47246, update your Linux kernel to a version that includes the security patch addressing this vulnerability.
Which Linux kernel versions are affected by CVE-2021-47246?
CVE-2021-47246 affects Linux kernel versions from 4.19 to 5.12.x and specific release candidates of 5.13.
What type of vulnerability is CVE-2021-47246?
CVE-2021-47246 is a vulnerability related to memory management in the Linux kernel, specifically involving page reclaim for dead peer hairpin.
Is there a workaround for CVE-2021-47246 if I cannot update the kernel?
There is no widely known workaround for CVE-2021-47246, and the recommended action is to patch your kernel as soon as possible.

agent/references
agent/title
agent/type
agent/description
agent/first-publish-date
agent/author
agent/event
collector/mitre-cve
source/MITRE
agent/source
agent/guess-ai
agent/software-canonical-lookup
agent/software-canonical-lookup-request
collector/nvd-api
source/NVD
agent/remedy
agent/weakness
agent/last-modified-date
agent/severity
agent/softwarecombine
agent/tags
vendor/linux
canonical/red hat kernel-devel
canonical/linux kernel
version/linux kernel/4.19
version/linux kernel/5.5
version/linux kernel/5.11
version/linux kernel/5.13-rc1
version/linux kernel/5.13-rc2
version/linux kernel/5.13-rc3
version/linux kernel/5.13-rc4
version/linux kernel/5.13-rc5
version/linux kernel/5.13-rc6

CVE-2021-47246: net/mlx5e: Fix page reclaim for dead peer hairpin

Remedy

Remedy

Remedy

Remedy

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2021-47246?

How do I fix CVE-2021-47246?

Which Linux kernel versions are affected by CVE-2021-47246?

What type of vulnerability is CVE-2021-47246?

Is there a workaround for CVE-2021-47246 if I cannot update the kernel?

Company

Resources

Contact

Frequently Asked Questions

What is the severity of CVE-2021-47246?

How do I fix CVE-2021-47246?

Which Linux kernel versions are affected by CVE-2021-47246?

What type of vulnerability is CVE-2021-47246?

Is there a workaround for CVE-2021-47246 if I cannot update the kernel?