CVE-2026-23198: KVM: Don't clobber irqfd routing type when deassigning irqfd
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.15% (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 2284bc168b148a17b5ca3b37b3d95c411f18a08d, 4385b2f2843549bfb932e0dcf76bf4b065543a3c, 6d14ba1e144e796b5fc81044f08cfba9024ca195.
- Severity is disputed: the assigning authority (CNA) scores it 7.8, NVD 5.5.
Low priority for now. Upgrade to Linux Linux 2284bc168b148a17b5ca3b37b3d95c411f18a08d, 4385b2f2843549bfb932e0dcf76bf4b065543a3c, 6d14ba1e144e796b5fc81044f08cfba9024ca195 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: KVM: Don't clobber irqfd routing type when deassigning irqfd When deassigning a KVM_IRQFD, don't clobber the irqfd's copy of the IRQ's routing entry as doing so breaks kvm_arch_irq_bypass_del_producer() on x86 and arm64, which explicitly look for KVM_IRQ_ROUTING_MSI. Instead, to handle a concurrent routing update, verify that the irqfd is still active before consuming the routing information. As evidenced by the x86 and arm64 bugs, and another bug in kvm_arch_update_irqfd_routing() (see below), clobbering the entry type without notifying arch code is surprising and error prone. As a bonus, checking that the irqfd is active provides a convenient location for documenting _why_ KVM must not consume the routing entry for an irqfd that is in the process of being deassigned: once the irqfd is deleted from the list (which happens *before* the eventfd is detached), it will no longer receive updates via kvm_irq_routing_update(), and so KVM could deliver an event using stale routing information (relative to KVM_SET_GSI_ROUTING returning to userspace). As an even better bonus, explicitly checking for the irqfd being active fixes a similar bug to the one the clobbering is trying to prevent: if an irqfd is deactivated, and then its routing is changed, kvm_irq_routing_update() won't invoke kvm_arch_update_irqfd_routing() (because the irqfd isn't in the list). And so if the irqfd is in bypass mode, IRQs will continue to be posted using the old routing information. As for kvm_arch_irq_bypass_del_producer(), clobbering the routing type results in KVM incorrectly keeping the IRQ in bypass mode, which is especially problematic on AMD as KVM tracks IRQs that are being posted to a vCPU in a list whose lifetime is tied to the irqfd. Without the help of KASAN to detect use-after-free, the most common sympton on AMD is a NULL pointer deref in amd_iommu_update_ga() due to the memory for irqfd structure being re-allocated and zeroed, resulting in irqfd->irq_bypass_data being NULL when read by avic_update_iommu_vcpu_affinity(): BUG: kernel NULL pointer dereference, address: 0000000000000018 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 40cf2b9067 P4D 40cf2b9067 PUD 408362a067 PMD 0 Oops: Oops: 0000 [#1] SMP CPU: 6 UID: 0 PID: 40383 Comm: vfio_irq_test Tainted: G U W O 6.19.0-smp--5dddc257e6b2-irqfd #31 NONE Tainted: [U]=USER, [W]=WARN, [O]=OOT_MODULE Hardware name: Google, Inc. Arcadia_IT_80/Arcadia_IT_80, BIOS 34.78.2-0 09/05/2025 RIP: 0010:amd_iommu_update_ga+0x19/0xe0 Call Trace: <TASK> avic_update_iommu_vcpu_affinity+0x3d/0x90 [kvm_amd] __avic_vcpu_load+0xf4/0x130 [kvm_amd] kvm_arch_vcpu_load+0x89/0x210 [kvm] vcpu_load+0x30/0x40 [kvm] kvm_arch_vcpu_ioctl_run+0x45/0x620 [kvm] kvm_vcpu_ioctl+0x571/0x6a0 [kvm] __se_sys_ioctl+0x6d/0xb0 do_syscall_64+0x6f/0x9d0 entry_SYSCALL_64_after_hwframe+0x4b/0x53 RIP: 0033:0x46893b </TASK> ---[ end trace 0000000000000000 ]--- If AVIC is inhibited when the irfd is deassigned, the bug will manifest as list corruption, e.g. on the next irqfd assignment. list_add corruption. next->prev should be prev (ffff8d474d5cd588), but was 0000000000000000. (next=ffff8d8658f86530). ------------[ cut here ]------------ kernel BUG at lib/list_debug.c:31! Oops: invalid opcode: 0000 [#1] SMP CPU: 128 UID: 0 PID: 80818 Comm: vfio_irq_test Tainted: G U W O 6.19.0-smp--f19dc4d680ba-irqfd #28 NONE Tainted: [U]=USER, [W]=WARN, [O]=OOT_MODULE Hardware name: Google, Inc. Arcadia_IT_80/Arcadia_IT_80, BIOS 34.78.2-0 09/05/2025 RIP: 0010:__list_add_valid_or_report+0x97/0xc0 Call Trace: <TASK> avic_pi_update_irte+0x28e/0x2b0 [kvm_amd] kvm_pi_update_irte+0xbf/0x190 [kvm] kvm_arch_irq_bypass_add_producer+0x72/0x90 [kvm] irq_bypass_register_consumer+0xcd/0x170 [irqbypa ---truncated---
- Published
- Feb 14, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 4th percentile
- CWE
- CWE-476
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.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 5.5
- CNA · Linux
- 7.8
- 2.3 point gap
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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 |
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
- 4.4affected
- f70c20aaf141adb715a2d750c55154073b02a9c3 and later · before 959a063e7f12524bc1871ad1f519787967bbcd45affected · git
- f70c20aaf141adb715a2d750c55154073b02a9c3 and later · before 2284bc168b148a17b5ca3b37b3d95c411f18a08daffected · git
- f70c20aaf141adb715a2d750c55154073b02a9c3 and later · before 6d14ba1e144e796b5fc81044f08cfba9024ca195affected · git
- f70c20aaf141adb715a2d750c55154073b02a9c3 and later · before b61f9b2fcf181451d0a319889478cc53c001123eaffected · git
- f70c20aaf141adb715a2d750c55154073b02a9c3 and later · before ff48c9312d042bfbe826ca675e98acc6c623211caffected · git
- f70c20aaf141adb715a2d750c55154073b02a9c3 and later · before 4385b2f2843549bfb932e0dcf76bf4b065543a3caffected · git
- f70c20aaf141adb715a2d750c55154073b02a9c3 and later · before b4d37cdb77a0015f51fee083598fa227cc07aaf1affected · git
- before 4.4not affected · semver
- 5.10.250 and later · up to and including 5.10.*not affected · semver
Affected versions · NVD (7)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel4.4 and later · before 5.10.250
- linux linux kernel5.11 and later · before 5.15.200
- linux linux kernel5.16 and later · before 6.1.163
- linux linux kernel6.2 and later · before 6.6.124
- linux linux kernel6.7 and later · before 6.12.70
- linux linux kernel6.13 and later · before 6.18.10
- linux linux kernel6.19
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:11 | linux | before 5.10.251-1 | 5.10.251-1 |
| Debian:12 | linux | before 6.1.164-1 | 6.1.164-1 |
| Debian:13 | linux | before 6.12.73-1 | 6.12.73-1 |
| Debian:14 | linux | before 6.18.10-1 | 6.18.10-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-2026-23193Feb 14, 2026 · scsi: target: iscsi: Fix use-after-free in iscsit_dec_session_usage_count()31Monitor
- ← EarlierCVE-2026-23196Feb 14, 2026 · HID: Intel-thc-hid: Intel-thc: Add safety check for reading DMA buffer22Monitor
- Later →CVE-2026-23200Feb 14, 2026 · ipv6: Fix ECMP sibling count mismatch when clearing RTF_ADDRCONF22Monitor
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 | 2284bc168b148a17b5ca3b37b3d95c411f18a08d | Vendor (CNA) |
| Linux Linux | 4385b2f2843549bfb932e0dcf76bf4b065543a3c | Vendor (CNA) |
| Linux Linux | 6d14ba1e144e796b5fc81044f08cfba9024ca195 | Vendor (CNA) |
| Linux Linux | 959a063e7f12524bc1871ad1f519787967bbcd45 | Vendor (CNA) |
| Linux Linux | b4d37cdb77a0015f51fee083598fa227cc07aaf1 | Vendor (CNA) |
| Linux Linux | b61f9b2fcf181451d0a319889478cc53c001123e | Vendor (CNA) |
| Linux Linux | ff48c9312d042bfbe826ca675e98acc6c623211c | Vendor (CNA) |
| debian:linux | 6.1.164-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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · 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-476 · NULL Pointer DereferenceCVSS 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 (6 more)Show less
- git.kernel.org/stable/c/4385b2f2843549bfb932e0dcf76bf4b065543a3c
- git.kernel.org/stable/c/6d14ba1e144e796b5fc81044f08cfba9024ca195
- git.kernel.org/stable/c/959a063e7f12524bc1871ad1f519787967bbcd45
- git.kernel.org/stable/c/b4d37cdb77a0015f51fee083598fa227cc07aaf1
- git.kernel.org/stable/c/b61f9b2fcf181451d0a319889478cc53c001123e
- git.kernel.org/stable/c/ff48c9312d042bfbe826ca675e98acc6c623211c
Vendor advisories and official records. Exploit/PoC links are deliberately left out.