linux-cve-announce - CVE-2022-50352: net: hns: fix possible memory leak in hnae_ae

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025091641-CVE-2022-50352-8531@gregkh>
Date: Tue, 16 Sep 2025 18:11:48 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2022-50352: net: hns: fix possible memory leak in hnae_ae_register()

From: Greg Kroah-Hartman <gregkh@...nel.org>

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

net: hns: fix possible memory leak in hnae_ae_register()

Inject fault while probing module, if device_register() fails,
but the refcount of kobject is not decreased to 0, the name
allocated in dev_set_name() is leaked. Fix this by calling
put_device(), so that name can be freed in callback function
kobject_cleanup().

unreferenced object 0xffff00c01aba2100 (size 128):
  comm "systemd-udevd", pid 1259, jiffies 4294903284 (age 294.152s)
  hex dump (first 32 bytes):
    68 6e 61 65 30 00 00 00 18 21 ba 1a c0 00 ff ff  hnae0....!......
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  backtrace:
    [<0000000034783f26>] slab_post_alloc_hook+0xa0/0x3e0
    [<00000000748188f2>] __kmem_cache_alloc_node+0x164/0x2b0
    [<00000000ab0743e8>] __kmalloc_node_track_caller+0x6c/0x390
    [<000000006c0ffb13>] kvasprintf+0x8c/0x118
    [<00000000fa27bfe1>] kvasprintf_const+0x60/0xc8
    [<0000000083e10ed7>] kobject_set_name_vargs+0x3c/0xc0
    [<000000000b87affc>] dev_set_name+0x7c/0xa0
    [<000000003fd8fe26>] hnae_ae_register+0xcc/0x190 [hnae]
    [<00000000fe97edc9>] hns_dsaf_ae_init+0x9c/0x108 [hns_dsaf]
    [<00000000c36ff1eb>] hns_dsaf_probe+0x548/0x748 [hns_dsaf]

The Linux kernel CVE team has assigned CVE-2022-50352 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 4.4 with commit 6fe6611ff275522a4e4c0359e2f46cdd07780d2f and fixed in 4.9.332 with commit a3c148955c22fe1d94d7a2096005679c1f22eddf
	Issue introduced in 4.4 with commit 6fe6611ff275522a4e4c0359e2f46cdd07780d2f and fixed in 4.14.298 with commit 3b78453cca046d3b03853f0d077ad3ad130db886
	Issue introduced in 4.4 with commit 6fe6611ff275522a4e4c0359e2f46cdd07780d2f and fixed in 4.19.264 with commit 7ae1345f6ad715acbcdc9e1ac28153684fd498bb
	Issue introduced in 4.4 with commit 6fe6611ff275522a4e4c0359e2f46cdd07780d2f and fixed in 5.4.221 with commit dfc0337c6dceb6449403b33ecb141f4a1458a1e9
	Issue introduced in 4.4 with commit 6fe6611ff275522a4e4c0359e2f46cdd07780d2f and fixed in 5.10.152 with commit 2974f3b330ef25f5d34a4948d04290c2cd7802cf
	Issue introduced in 4.4 with commit 6fe6611ff275522a4e4c0359e2f46cdd07780d2f and fixed in 5.15.76 with commit 91f8f5342bee726ed5692583d58f69e7cc9ae60e
	Issue introduced in 4.4 with commit 6fe6611ff275522a4e4c0359e2f46cdd07780d2f and fixed in 6.0.6 with commit 02dc0db19d944b4a90941db505ecf1aaec714be4
	Issue introduced in 4.4 with commit 6fe6611ff275522a4e4c0359e2f46cdd07780d2f and fixed in 6.1 with commit ff2f5ec5d009844ec28f171123f9e58750cef4bf

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2022-50352
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	drivers/net/ethernet/hisilicon/hns/hnae.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/a3c148955c22fe1d94d7a2096005679c1f22eddf
	https://git.kernel.org/stable/c/3b78453cca046d3b03853f0d077ad3ad130db886
	https://git.kernel.org/stable/c/7ae1345f6ad715acbcdc9e1ac28153684fd498bb
	https://git.kernel.org/stable/c/dfc0337c6dceb6449403b33ecb141f4a1458a1e9
	https://git.kernel.org/stable/c/2974f3b330ef25f5d34a4948d04290c2cd7802cf
	https://git.kernel.org/stable/c/91f8f5342bee726ed5692583d58f69e7cc9ae60e
	https://git.kernel.org/stable/c/02dc0db19d944b4a90941db505ecf1aaec714be4
	https://git.kernel.org/stable/c/ff2f5ec5d009844ec28f171123f9e58750cef4bf