CVE-2024-36950: firewire: ohci: mask bus reset interrupts between ISR and bottom half
Noroxi assessment
Priority: Monitor (action score 17/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.26% (FIRST EPSS).
- Someone with local access to the system can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 31279bbca40d2f40cb3bbb6d538ec9620a645dec, 4f9cc355c328fc4f41cbd9c4cd58b235184fa420, 5982887de60c1b84f9c0ca07c835814d07fd1da0.
Low priority for now. Upgrade to Linux Linux 31279bbca40d2f40cb3bbb6d538ec9620a645dec, 4f9cc355c328fc4f41cbd9c4cd58b235184fa420, 5982887de60c1b84f9c0ca07c835814d07fd1da0 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: firewire: ohci: mask bus reset interrupts between ISR and bottom half In the FireWire OHCI interrupt handler, if a bus reset interrupt has occurred, mask bus reset interrupts until bus_reset_work has serviced and cleared the interrupt. Normally, we always leave bus reset interrupts masked. We infer the bus reset from the self-ID interrupt that happens shortly thereafter. A scenario where we unmask bus reset interrupts was introduced in 2008 in a007bb857e0b26f5d8b73c2ff90782d9c0972620: If OHCI_PARAM_DEBUG_BUSRESETS (8) is set in the debug parameter bitmask, we will unmask bus reset interrupts so we can log them. irq_handler logs the bus reset interrupt. However, we can't clear the bus reset event flag in irq_handler, because we won't service the event until later. irq_handler exits with the event flag still set. If the corresponding interrupt is still unmasked, the first bus reset will usually freeze the system due to irq_handler being called again each time it exits. This freeze can be reproduced by loading firewire_ohci with "modprobe firewire_ohci debug=-1" (to enable all debugging output). Apparently there are also some cases where bus_reset_work will get called soon enough to clear the event, and operation will continue normally. This freeze was first reported a few months after a007bb85 was committed, but until now it was never fixed. The debug level could safely be set to -1 through sysfs after the module was loaded, but this would be ineffectual in logging bus reset interrupts since they were only unmasked during initialization. irq_handler will now leave the event flag set but mask bus reset interrupts, so irq_handler won't be called again and there will be no freeze. If OHCI_PARAM_DEBUG_BUSRESETS is enabled, bus_reset_work will unmask the interrupt after servicing the event, so future interrupts will be caught as desired. As a side effect to this change, OHCI_PARAM_DEBUG_BUSRESETS can now be enabled through sysfs in addition to during initial module loading. However, when enabled through sysfs, logging of bus reset interrupts will be effective only starting with the second bus reset, after bus_reset_work has executed.
- Published
- May 30, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 17th percentile
- CWE
- —
Report tools
Action score
17
Monitor
Low priority for now.
- CVSS
- 17 / 40 · 4.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux10.0
- linux linux kernel4.20 and later · before 5.4.276
- linux linux kernel5.5 and later · before 5.10.217
- linux linux kernel5.11 and later · before 5.15.159
- linux linux kernelbefore 4.19.314
- linux linux kernel6.2 and later · before 6.6.31
- linux linux kernel6.7 and later · before 6.8.10
- linux linux kernel5.16 and later · before 6.1.91
- linux linux kernel6.9
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 2.6.26affected
- a007bb857e0b26f5d8b73c2ff90782d9c0972620 and later · before b3948c69d60279fce5b2eeda92a07d66296c8130affected · git
- a007bb857e0b26f5d8b73c2ff90782d9c0972620 and later · before 31279bbca40d2f40cb3bbb6d538ec9620a645decaffected · git
- a007bb857e0b26f5d8b73c2ff90782d9c0972620 and later · before fa273f312334246c909475c5868e6daab889cc8caffected · git
- a007bb857e0b26f5d8b73c2ff90782d9c0972620 and later · before 4f9cc355c328fc4f41cbd9c4cd58b235184fa420affected · git
- a007bb857e0b26f5d8b73c2ff90782d9c0972620 and later · before 6fafe3661712b143d9c69a7322294bd53f559d5daffected · git
- a007bb857e0b26f5d8b73c2ff90782d9c0972620 and later · before 5982887de60c1b84f9c0ca07c835814d07fd1da0affected · git
- a007bb857e0b26f5d8b73c2ff90782d9c0972620 and later · before 8643332aac0576581cfdf01798ea3e4e0d624b61affected · git
- a007bb857e0b26f5d8b73c2ff90782d9c0972620 and later · before 752e3c53de0fa3b7d817a83050b6699b8e9c6ec9affected · git
- before 2.6.26not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.94-1 | 6.1.94-1 |
| Debian:13 | linux | before 6.8.11-1 | 6.8.11-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2024-36948May 30, 2024 · drm/xe/xe_migrate: Cast to output precision before multiplying operands22Monitor
- ← EarlierCVE-2024-36949May 30, 2024 · amd/amdkfd: sync all devices to wait all processes being evicted18Monitor
- Later →CVE-2024-36951May 30, 2024 · drm/amdkfd: range check cp bad op exception interrupts22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 31279bbca40d2f40cb3bbb6d538ec9620a645dec | Vendor (CNA) |
| Linux Linux | 4f9cc355c328fc4f41cbd9c4cd58b235184fa420 | Vendor (CNA) |
| Linux Linux | 5982887de60c1b84f9c0ca07c835814d07fd1da0 | Vendor (CNA) |
| Linux Linux | 6fafe3661712b143d9c69a7322294bd53f559d5d | Vendor (CNA) |
| Linux Linux | 752e3c53de0fa3b7d817a83050b6699b8e9c6ec9 | Vendor (CNA) |
| Linux Linux | 8643332aac0576581cfdf01798ea3e4e0d624b61 | Vendor (CNA) |
| Linux Linux | b3948c69d60279fce5b2eeda92a07d66296c8130 | Vendor (CNA) |
| Linux Linux | fa273f312334246c909475c5868e6daab889cc8c | Vendor (CNA) |
| debian:linux | 6.1.94-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- Administrator privileges are required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (9 more)Show less
- git.kernel.org/stable/c/4f9cc355c328fc4f41cbd9c4cd58b235184fa420
- git.kernel.org/stable/c/5982887de60c1b84f9c0ca07c835814d07fd1da0
- git.kernel.org/stable/c/6fafe3661712b143d9c69a7322294bd53f559d5d
- git.kernel.org/stable/c/752e3c53de0fa3b7d817a83050b6699b8e9c6ec9
- git.kernel.org/stable/c/8643332aac0576581cfdf01798ea3e4e0d624b61
- git.kernel.org/stable/c/b3948c69d60279fce5b2eeda92a07d66296c8130
- git.kernel.org/stable/c/fa273f312334246c909475c5868e6daab889cc8c
- lists.debian.org/debian-lts-announce/2024/06/msg00019.html
- lists.debian.org/debian-lts-announce/2024/06/msg00020.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.