CVE-2024-35816: firewire: ohci: prevent leak of left-over IRQ on unbind
In the Linux kernel, the following vulnerability has been resolved:
firewire: ohci: prevent leak of left-over IRQ on unbind
Commit 5a95f1ded28691e6 ("firewire: ohci: use devres for requested IRQ")
also removed the call to free_irq() in pci_remove(), leading to a
leftover irq of devm_request_irq() at pci_disable_msi() in pci_remove()
when unbinding the driver from the device
remove_proc_entry: removing non-empty directory 'irq/136', leaking at
least 'firewire_ohci'
Call Trace:
? remove_proc_entry+0x19c/0x1c0
? __warn+0x81/0x130
? remove_proc_entry+0x19c/0x1c0
? report_bug+0x171/0x1a0
? console_unlock+0x78/0x120
? handle_bug+0x3c/0x80
? exc_invalid_op+0x17/0x70
? asm_exc_invalid_op+0x1a/0x20
? remove_proc_entry+0x19c/0x1c0
unregister_irq_proc+0xf4/0x120
free_desc+0x3d/0xe0
? kfree+0x29f/0x2f0
irq_free_descs+0x47/0x70
msi_domain_free_locked.part.0+0x19d/0x1d0
msi_domain_free_irqs_all_locked+0x81/0xc0
pci_free_msi_irqs+0x12/0x40
pci_disable_msi+0x4c/0x60
pci_remove+0x9d/0xc0 [firewire_ohci
01b483699bebf9cb07a3d69df0aa2bee71db1b26]
pci_device_remove+0x37/0xa0
device_release_driver_internal+0x19f/0x200
unbind_store+0xa1/0xb0
remove irq with devm_free_irq() before pci_disable_msi()
also remove it in fail_msi: of pci_probe() as this would lead to
an identical leak
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue can leave a FireWire OHCI interrupt resource behind when the driver is unbound from a device. The public record shows a resource leak and kernel warning, not remote compromise or active exploitation. Business urgency depends on whether affected Linux kernels and FireWire hardware or drivers exist in your fleet.
Executive priority
Track as a low-priority kernel maintenance item unless your environment relies on FireWire hardware or frequent driver bind/unbind workflows. There is no source-supported evidence of active exploitation, but affected kernels should still receive normal vendor security updates.
Technical view
The regression came from commit 5a95f1ded286, which moved FireWire OHCI IRQ handling to devres but removed explicit free_irq handling. During pci_remove or pci_probe MSI failure handling, pci_disable_msi can encounter a leftover devm_request_irq allocation. Stable fixes add devm_free_irq before MSI teardown.
Likely exposure
Exposure appears limited to Linux systems running affected kernel versions with the firewire_ohci PCI driver path present, especially where device unbind or MSI failure paths occur. The source bundle does not identify application-level, network, or cloud-service exposure.
Exploitation context
The provided sources do not report active exploitation, and the CVE is not marked KEV. The described impact is an IRQ/proc resource leak during driver unbind or probe failure, with a kernel warning trace. No public source in the bundle claims privilege escalation, data theft, or remote execution.
Researcher notes
Evidence is narrow and kernel-specific. The root cause is cleanup ordering around devm_request_irq and MSI teardown in firewire_ohci. The public bundle provides affected version data and stable commit references, but no CVSS, CWE, exploitability analysis, or broader impact statement.
Mitigation direction
Update to a vendor kernel containing the referenced stable FireWire OHCI fixes.
Prioritize distribution advisories for affected Linux kernel branches.
Confirm change windows for systems with FireWire hardware or firewire_ohci loaded.
If no package is available, follow vendor guidance before applying kernel patches manually.
Validation and detection
Inventory Linux hosts for affected kernel versions and FireWire OHCI usage.
Verify patched kernels include one of the referenced stable commits or distro backports.
Review kernel logs for remove_proc_entry warnings involving irq and firewire_ohci.
In staging, confirm driver removal no longer leaves IRQ proc entries.
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-2024-35816 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.