From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2022-49525: media: cx25821: Fix the warning when removing the module
Date: Wed, 26 Feb 2025 03:13:19 +0100 [thread overview]
Message-ID: <2025022611-CVE-2022-49525-efd9@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
media: cx25821: Fix the warning when removing the module
When removing the module, we will get the following warning:
[ 14.746697] remove_proc_entry: removing non-empty directory 'irq/21', leaking at least 'cx25821[1]'
[ 14.747449] WARNING: CPU: 4 PID: 368 at fs/proc/generic.c:717 remove_proc_entry+0x389/0x3f0
[ 14.751611] RIP: 0010:remove_proc_entry+0x389/0x3f0
[ 14.759589] Call Trace:
[ 14.759792] <TASK>
[ 14.759975] unregister_irq_proc+0x14c/0x170
[ 14.760340] irq_free_descs+0x94/0xe0
[ 14.760640] mp_unmap_irq+0xb6/0x100
[ 14.760937] acpi_unregister_gsi_ioapic+0x27/0x40
[ 14.761334] acpi_pci_irq_disable+0x1d3/0x320
[ 14.761688] pci_disable_device+0x1ad/0x380
[ 14.762027] ? _raw_spin_unlock_irqrestore+0x2d/0x60
[ 14.762442] ? cx25821_shutdown+0x20/0x9f0 [cx25821]
[ 14.762848] cx25821_finidev+0x48/0xc0 [cx25821]
[ 14.763242] pci_device_remove+0x92/0x240
Fix this by freeing the irq before call pci_disable_device().
The Linux kernel CVE team has assigned CVE-2022-49525 to this issue.
Affected and fixed versions
===========================
Fixed in 4.9.318 with commit 4d6295b6d986476232332fffd08575b185f90d81
Fixed in 4.14.283 with commit 5beb85ff7d005ddb7bf604a4f2dc76f01b84b318
Fixed in 4.19.247 with commit 258639bc55a586ee6df92d89786ccf1c71546d70
Fixed in 5.4.198 with commit 222292930c8ecc3516e03ec1f9fa8448be7ff496
Fixed in 5.10.121 with commit 3f94169affa33c9db4a439d88f09cb2ed3a33332
Fixed in 5.15.46 with commit 1f0fc1dfb5fdd456657519a97fab83691b96c6a0
Fixed in 5.17.14 with commit 9d92291698e5cc35a2b8a1106a01ddd7d60ade2d
Fixed in 5.18.3 with commit 005fd553f5f10fe8618d92f94ad10f9051eac331
Fixed in 5.19 with commit 2203436a4d24302871617373a7eb21bc17e38762
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-49525
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/media/pci/cx25821/cx25821-core.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/4d6295b6d986476232332fffd08575b185f90d81
https://git.kernel.org/stable/c/5beb85ff7d005ddb7bf604a4f2dc76f01b84b318
https://git.kernel.org/stable/c/258639bc55a586ee6df92d89786ccf1c71546d70
https://git.kernel.org/stable/c/222292930c8ecc3516e03ec1f9fa8448be7ff496
https://git.kernel.org/stable/c/3f94169affa33c9db4a439d88f09cb2ed3a33332
https://git.kernel.org/stable/c/1f0fc1dfb5fdd456657519a97fab83691b96c6a0
https://git.kernel.org/stable/c/9d92291698e5cc35a2b8a1106a01ddd7d60ade2d
https://git.kernel.org/stable/c/005fd553f5f10fe8618d92f94ad10f9051eac331
https://git.kernel.org/stable/c/2203436a4d24302871617373a7eb21bc17e38762
reply other threads:[~2025-02-26 2:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2025022611-CVE-2022-49525-efd9@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.