CVE-2024-26687: xen/events: close evtchn after mapping cleanup
Noroxi assessment
Priority: Monitor (action score 22/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.22% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 0fc88aeb2e32b76db3fe6a624b8333dbe621b8fd, 20980195ec8d2e41653800c45c8c367fa1b1f2b4, 585a344af6bcac222608a158fc2830ff02712af5; cbl2 kernel 5.15.176.3-3 on CBL Mariner 2.0 5.15.176.3-3; cbl2 kernel 5.15.182.1-1 on CBL Mariner 2.0 CBL-Mariner Releases.
- Mentioned 2 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 0fc88aeb2e32b76db3fe6a624b8333dbe621b8fd, 20980195ec8d2e41653800c45c8c367fa1b1f2b4, 585a344af6bcac222608a158fc2830ff02712af5; cbl2 kernel 5.15.176.3-3 on CBL Mariner 2.0 5.15.176.3-3; cbl2 kernel 5.15.182.1-1 on CBL Mariner 2.0 CBL-Mariner Releases 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: xen/events: close evtchn after mapping cleanup shutdown_pirq and startup_pirq are not taking the irq_mapping_update_lock because they can't due to lock inversion. Both are called with the irq_desc->lock being taking. The lock order, however, is first irq_mapping_update_lock and then irq_desc->lock. This opens multiple races: - shutdown_pirq can be interrupted by a function that allocates an event channel: CPU0 CPU1 shutdown_pirq { xen_evtchn_close(e) __startup_pirq { EVTCHNOP_bind_pirq -> returns just freed evtchn e set_evtchn_to_irq(e, irq) } xen_irq_info_cleanup() { set_evtchn_to_irq(e, -1) } } Assume here event channel e refers here to the same event channel number. After this race the evtchn_to_irq mapping for e is invalid (-1). - __startup_pirq races with __unbind_from_irq in a similar way. Because __startup_pirq doesn't take irq_mapping_update_lock it can grab the evtchn that __unbind_from_irq is currently freeing and cleaning up. In this case even though the event channel is allocated, its mapping can be unset in evtchn_to_irq. The fix is to first cleanup the mappings and then close the event channel. In this way, when an event channel gets allocated it's potential previous evtchn_to_irq mappings are guaranteed to be unset already. This is also the reverse order of the allocation where first the event channel is allocated and then the mappings are setup. On a 5.10 kernel prior to commit 3fcdaf3d7634 ("xen/events: modify internal [un]bind interfaces"), we hit a BUG like the following during probing of NVMe devices. The issue is that during nvme_setup_io_queues, pci_free_irq is called for every device which results in a call to shutdown_pirq. With many nvme devices it's therefore likely to hit this race during boot because there will be multiple calls to shutdown_pirq and startup_pirq are running potentially in parallel. ------------[ cut here ]------------ blkfront: xvda: barrier or flush: disabled; persistent grants: enabled; indirect descriptors: enabled; bounce buffer: enabled kernel BUG at drivers/xen/events/events_base.c:499! invalid opcode: 0000 [#1] SMP PTI CPU: 44 PID: 375 Comm: kworker/u257:23 Not tainted 5.10.201-191.748.amzn2.x86_64 #1 Hardware name: Xen HVM domU, BIOS 4.11.amazon 08/24/2006 Workqueue: nvme-reset-wq nvme_reset_work RIP: 0010:bind_evtchn_to_cpu+0xdf/0xf0 Code: 5d 41 5e c3 cc cc cc cc 44 89 f7 e8 2b 55 ad ff 49 89 c5 48 85 c0 0f 84 64 ff ff ff 4c 8b 68 30 41 83 fe ff 0f 85 60 ff ff ff <0f> 0b 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 0f 1f 44 00 00 RSP: 0000:ffffc9000d533b08 EFLAGS: 00010046 RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000006 RDX: 0000000000000028 RSI: 00000000ffffffff RDI: 00000000ffffffff RBP: ffff888107419680 R08: 0000000000000000 R09: ffffffff82d72b00 R10: 0000000000000000 R11: 0000000000000000 R12: 00000000000001ed R13: 0000000000000000 R14: 00000000ffffffff R15: 0000000000000002 FS: 0000000000000000(0000) GS:ffff88bc8b500000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000000 CR3: 0000000002610001 CR4: 00000000001706e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: ? show_trace_log_lvl+0x1c1/0x2d9 ? show_trace_log_lvl+0x1c1/0x2d9 ? set_affinity_irq+0xdc/0x1c0 ? __die_body.cold+0x8/0xd ? die+0x2b/0x50 ? do_trap+0x90/0x110 ? bind_evtchn_to_cpu+0xdf/0xf0 ? do_error_trap+0x65/0x80 ? bind_evtchn_to_cpu+0xdf/0xf0 ? exc_invalid_op+0x4e/0x70 ? bind_evtchn_to_cpu+0xdf/0xf0 ? asm_exc_invalid_op+0x12/0x20 ? bind_evtchn_to_cpu+0xdf/0x ---truncated---
- Published
- Apr 3, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 13th percentile
- CWE
- CWE-459
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 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.
Is your version affected? Check itNoroxi 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 |
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.37affected
- d46a78b05c0e37f76ddf4a7a67bf0b6c68bada55 and later · before 9470f5b2503cae994098dea9682aee15b313fa44affected · git
- d46a78b05c0e37f76ddf4a7a67bf0b6c68bada55 and later · before 0fc88aeb2e32b76db3fe6a624b8333dbe621b8fdaffected · git
- d46a78b05c0e37f76ddf4a7a67bf0b6c68bada55 and later · before ea592baf9e41779fe9a0424c03dd2f324feca3b3affected · git
- d46a78b05c0e37f76ddf4a7a67bf0b6c68bada55 and later · before 585a344af6bcac222608a158fc2830ff02712af5affected · git
- d46a78b05c0e37f76ddf4a7a67bf0b6c68bada55 and later · before 20980195ec8d2e41653800c45c8c367fa1b1f2b4affected · git
- d46a78b05c0e37f76ddf4a7a67bf0b6c68bada55 and later · before 9be71aa12afa91dfe457b3fb4a444c42b1ee036baffected · git
- d46a78b05c0e37f76ddf4a7a67bf0b6c68bada55 and later · before fa765c4b4aed2d64266b694520ecb025c862c5a9affected · git
- before 2.6.37not affected · semver
- 5.4.274 and later · up to and including 5.4.*not affected · semver
Affected versions · NVD (5)
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 kernel2.6.37 and later · before 6.1.81
- linux linux kernel6.2 and later · before 6.6.19
- linux linux kernel6.7 and later · before 6.7.6
- linux linux kernel6.8
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.82-1 | 6.1.82-1 |
| Debian:13 | linux | before 6.7.7-1 | 6.7.7-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-26685Apr 3, 2024 · nilfs2: fix potential bug in end_buffer_async_write22Monitor
- ← EarlierCVE-2024-26686Apr 3, 2024 · fs/proc: do_task_stat: use sig->stats_lock to gather the threads/children stats22Monitor
- Later →CVE-2024-26688Apr 3, 2024 · fs,hugetlb: fix NULL pointer dereference in hugetlbs_fill_super22Monitor
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 | 0fc88aeb2e32b76db3fe6a624b8333dbe621b8fd | Vendor (CNA) |
| Linux Linux | 20980195ec8d2e41653800c45c8c367fa1b1f2b4 | Vendor (CNA) |
| Linux Linux | 585a344af6bcac222608a158fc2830ff02712af5 | Vendor (CNA) |
| Linux Linux | 9470f5b2503cae994098dea9682aee15b313fa44 | Vendor (CNA) |
| Linux Linux | 9be71aa12afa91dfe457b3fb4a444c42b1ee036b | Vendor (CNA) |
| Linux Linux | ea592baf9e41779fe9a0424c03dd2f324feca3b3 | Vendor (CNA) |
| Linux Linux | fa765c4b4aed2d64266b694520ecb025c862c5a9 | Vendor (CNA) |
| cbl2 kernel 5.15.176.3-3 on CBL Mariner 2.0 | 5.15.176.3-3 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.182.1-1 on CBL Mariner 2.0 | CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.182.1-1 on CBL-Mariner 2.0 | 5.15.176.3-3 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.82-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.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2025-37908412 days apartmm, slab: clean up slab->obj_exts always31Monitor
- CVE-2022-3238506 days apartA double-free flaw was found in the Linux kernel’s NTFS3 subsystem in how a user triggers remount and umount simultaneously.31Monitor
- CVE-2021-4711019 days apartx86/kvm: Disable kvmclock on all CPUs on shutdown28Monitor
- CVE-2024-47693201 days apartIB/core: Fix ib_cache_setup_one error flow cleanup26Monitor
- CVE-2024-267560 days apartmd: Don't register sync_thread for reshape directly22Monitor
- CVE-2024-268031 days apartnet: veth: clear GRO when clearing XDP even when down22Monitor
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-0494 · May 16, 2024(Linux Kernel Güncellemesi)
- TR-24-0265 · Apr 4, 2024(Linux Kernel Güncellemesi)
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-459 · Incomplete CleanupCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/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 (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/20980195ec8d2e41653800c45c8c367fa1b1f2b4
- git.kernel.org/stable/c/585a344af6bcac222608a158fc2830ff02712af5
- git.kernel.org/stable/c/9470f5b2503cae994098dea9682aee15b313fa44
- git.kernel.org/stable/c/9be71aa12afa91dfe457b3fb4a444c42b1ee036b
- git.kernel.org/stable/c/ea592baf9e41779fe9a0424c03dd2f324feca3b3
- git.kernel.org/stable/c/fa765c4b4aed2d64266b694520ecb025c862c5a9
- lists.debian.org/debian-lts-announce/2024/06/msg00017.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.