CVE-2022-49525: media: cx25821: Fix the warning when removing the module
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().
Security readout for executives and security teams
Plain-English summary
CVE-2022-49525 is a Linux kernel issue in the cx25821 media driver. The documented problem is a warning and leaked proc entry when the module is removed. The source does not describe remote attack, privilege escalation, data exposure, or active exploitation.
Executive priority
Treat as routine kernel maintenance unless cx25821 is used in production or stability warnings are observed. Prioritize through normal patch cycles, not emergency response, based on current evidence.
Technical view
In the cx25821 driver, module removal could call pci_disable_device() before freeing the IRQ. This left a non-empty /proc IRQ directory entry and generated a kernel warning. The referenced kernel stable commits change teardown order to free the IRQ before disabling the PCI device.
Likely exposure
Exposure appears limited to Linux systems with affected kernel builds where the cx25821 media driver is present and used or loadable. Systems without this driver or hardware are less likely to be practically affected. Distribution backports may change version-based conclusions.
Exploitation context
The only documented trigger is removing the cx25821 module. The bundle reports KEV=false and provides no evidence of active exploitation or public weaponization. Business impact is unclear from the available sources.
Researcher notes
The CVE record lacks CVSS, CWE, and explicit security impact. Analysis should focus on affected driver presence, stable-branch fix inclusion, and whether vendor kernels backported the teardown-order change.
Mitigation direction
Update to a kernel or vendor package containing the referenced stable fixes.
Check distribution advisories for backported fixes before relying on upstream version numbers.
If cx25821 is not needed, consider disabling it under vendor-approved configuration guidance.
Validation and detection
Inventory Linux kernels and confirm whether cx25821 is present or loadable.
Check vendor kernel changelogs for the referenced cx25821 IRQ teardown fix.
Review kernel logs for cx25821 removal warnings if the module is used.
Confirm remediation through package metadata or kernel source containing the fix.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2022-49525 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
10Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Feb 26, 2025, 02:13 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.