CVE-2026-43249·Kernel vulnerability
In the Linux kernel, the following vulnerability has been resolved: 9p/xen: protect xen_9pfs_front_free against concurrent calls The xenwatch thread can race with other back-end change notifications and call xen_9pfs_front_free() twice, hitting the observed general protection fault due to a double-free. Guard the teardown path so only one caller can release the front-end state at a time, preventing the crash. This is a fix for the following double-free: [ 27.052347] Oops: general protection fault, probably for non-canonical address 0x6b6b6b6b6b6b6b6b: 0000 [#1] SMP DEBUG_PAGEALLOC NOPTI [ 27.052357] CPU: 0 UID: 0 PID: 32 Comm: xenwatch Not tainted 6.18.0-02087-g51ab33fc0a8b-dirty #60 PREEMPT(none) [ 27.052363] RIP: e030:xen_9pfs_front_free+0x1d/0x150 [ 27.052368] Code: 90 90 90 90 90 90 90 90 90 90 90 90 90 41 55 41 54 55 48 89 fd 48 c7 c7 48 d0 92 85 53 e8 cb cb 05 00 48 8b 45 08 48 8b 55 00 <48> 3b 28 0f 85 f9 28 35 fe 48 3b 6a 08 0f 85 ef 28 35 fe 48 89 42 [ 27.052377] RSP: e02b:ffffc9004016fdd0 EFLAGS: 00010246 [ 27.052381] RAX: 6b6b6b6b6b6b6b6b RBX: ffff88800d66e400 RCX: 0000000000000000 [ 27.052385] RDX: 6b6b6b6b6b6b6b6b RSI: 0000000000000000 RDI: 0000000000000000 [ 27.052389] RBP: ffff88800a887040 R08: 0000000000000000 R09: 0000000000000000 [ 27.052393] R10: 0000000000000000 R11: 0000000000000000 R12: ffff888009e46b68 [ 27.052397] R13: 0000000000000200 R14: 0000000000000000 R15: ffff88800a887040 [ 27.052404] FS: 0000000000000000(0000) GS:ffff88808ca57000(0000) knlGS:0000000000000000 [ 27.052408] CS: e030 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 27.052412] CR2: 00007f9714004360 CR3: 0000000004834000 CR4: 0000000000050660 [ 27.052418] Call Trace: [ 27.052420] <TASK> [ 27.052422] xen_9pfs_front_changed+0x5d5/0x720 [ 27.052426] ? xenbus_otherend_changed+0x72/0x140 [ 27.052430] ? __pfx_xenwatch_thread+0x10/0x10 [ 27.052434] xenwatch_thread+0x94/0x1c0 [ 27.052438] ? __pfx_autoremove_wake_function+0x10/0x10 [ 27.052442] kthread+0xf8/0x240 [ 27.052445] ? __pfx_kthread+0x10/0x10 [ 27.052449] ? __pfx_kthread+0x10/0x10 [ 27.052452] ret_from_fork+0x16b/0x1a0 [ 27.052456] ? __pfx_kthread+0x10/0x10 [ 27.052459] ret_from_fork_asm+0x1a/0x30 [ 27.052463] </TASK> [ 27.052465] Modules linked in: [ 27.052471] ---[ end trace 0000000000000000 ]---
- Severity
- high
- Software
- Kernel
- Fixed in
- 6.19.6
- Published
How likely is exploitation
FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 0.31% — higher than 24% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.
Read the two together. CVE-2026-43249 scores 8.8 on CVSS, so a successful attack would be serious — but at 0.31%, almost nobody is currently attempting it. That is a different situation from a flaw under mass exploitation, and it is usually the difference between patching on your next maintenance window and patching tonight.
Affected versions
From: 6.19
Until: 6.19.6
Fixed in: 6.19.6
How to fix this CVE
Update your Linux kernel to version 6.19.6 or later to resolve a critical double-free vulnerability in the Xen 9pfs front-end driver. This race condition can be triggered when the xenwatch thread concurrently processes backend state changes, leading to kernel crashes. Apply the patch immediately if you are running Xen-based virtualization with 9pfs filesystem support.
sudo dnf update kernel kernel-develDefensia detects this vulnerability
How to check if you are affected
- Step 1: Check kernel version with `uname -r` and compare against 6.19.6 (vulnerable if ≤6.19.5)
- Step 2: Verify Xen 9pfs is in use by running `lsmod | grep xen_9pfs` — if module loads, the vulnerable code path is present
- Step 3: Search kernel logs for 'general protection fault' and 'xen_9pfs_front_free' using `dmesg | grep -i 'xen_9pfs\|general protection' or journalctl -b | grep -i 'xen_9pfs'`
- Step 4: After patching, verify the new kernel version with `uname -r` and confirm it is 6.19.6 or later
FAQ
What is CVE-2026-43249?
This vulnerability is a race condition in the Linux kernel's Xen 9pfs front-end driver where the xenwatch thread can simultaneously trigger the cleanup function (xen_9pfs_front_free) twice, causing a double-free memory corruption and kernel panic. The vulnerability affects systems using Xen virtualization with the 9pfs filesystem protocol.
Is CVE-2026-43249 being actively exploited?
No, there is no evidence of active exploitation in the wild. This is a kernel race condition that requires specific Xen and 9pfs configurations to trigger, making practical exploitation limited to affected virtualized environments.
What versions of Kernel are affected by CVE-2026-43249?
Linux kernel versions 6.19 through 6.19.5 are vulnerable. The fix is included in kernel 6.19.6 and all subsequent releases.
How do I check if my server is vulnerable to CVE-2026-43249?
Run `uname -r` to check your kernel version. If it shows 6.19.0 through 6.19.5, you are vulnerable. Additionally, run `lsmod | grep xen_9pfs` to confirm the vulnerable driver is loaded on your system.
Does Defensia detect CVE-2026-43249?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If the Linux kernel is installed on a monitored server, CVE-2026-43249 will appear in your dashboard with remediation steps.
Related Kernel CVEs
References
- https://git.kernel.org/stable/c/056709e2c6f121548df108a9fef2d1430b233e56
- https://git.kernel.org/stable/c/480aa6ffd4ac7036eea042047d0cca71bc2074bb
- https://git.kernel.org/stable/c/59e7707492576bdbfa8c1dbe7d90791df31e4773
- https://git.kernel.org/stable/c/a5d00dff97118a32fcf5fec7a4c3f864c4620c4e
- https://git.kernel.org/stable/c/bf841d43f7a33d75675ba7f4e214ac1c67913065
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-43249. Free for 1 server.
Get started free