xen-netfront: Fix NULL sring after live migration
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.26% (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 99859947517e446058ad7243ee81d2f9801fa3dd, d50b7914fae04d840ce36491d22133070b18cca9, e6860c889f4ad50b6ab696f5ea154295d72cf27a.
Low priority for now. Upgrade to Linux Linux 99859947517e446058ad7243ee81d2f9801fa3dd, d50b7914fae04d840ce36491d22133070b18cca9, e6860c889f4ad50b6ab696f5ea154295d72cf27a 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-netfront: Fix NULL sring after live migration A NAPI is setup for each network sring to poll data to kernel The sring with source host is destroyed before live migration and new sring with target host is setup after live migration. The NAPI for the old sring is not deleted until setup new sring with target host after migration. With busy_poll/busy_read enabled, the NAPI can be polled before got deleted when resume VM. BUG: unable to handle kernel NULL pointer dereference at 0000000000000008 IP: xennet_poll+0xae/0xd20 PGD 0 P4D 0 Oops: 0000 [#1] SMP PTI Call Trace: finish_task_switch+0x71/0x230 timerqueue_del+0x1d/0x40 hrtimer_try_to_cancel+0xb5/0x110 xennet_alloc_rx_buffers+0x2a0/0x2a0 napi_busy_loop+0xdb/0x270 sock_poll+0x87/0x90 do_sys_poll+0x26f/0x580 tracing_map_insert+0x1d4/0x2f0 event_hist_trigger+0x14a/0x260 finish_task_switch+0x71/0x230 __schedule+0x256/0x890 recalc_sigpending+0x1b/0x50 xen_sched_clock+0x15/0x20 __rb_reserve_next+0x12d/0x140 ring_buffer_lock_reserve+0x123/0x3d0 event_triggers_call+0x87/0xb0 trace_event_buffer_commit+0x1c4/0x210 xen_clocksource_get_cycles+0x15/0x20 ktime_get_ts64+0x51/0xf0 SyS_ppoll+0x160/0x1a0 SyS_ppoll+0x160/0x1a0 do_syscall_64+0x73/0x130 entry_SYSCALL_64_after_hwframe+0x41/0xa6 ... RIP: xennet_poll+0xae/0xd20 RSP: ffffb4f041933900 CR2: 0000000000000008 ---[ end trace f8601785b354351c ]--- xen frontend should remove the NAPIs for the old srings before live migration as the bond srings are destroyed There is a tiny window between the srings are set to NULL and the NAPIs are disabled, It is safe as the NAPI threads are still frozen at that time
- Published
- Oct 21, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 16th percentile
- CWE
- CWE-476
Report tools
Action score
22
Monitor
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.
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 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel2.6.24 and later · before 4.19.269
- linux linux kernel4.20 and later · before 5.4.227
- linux linux kernel5.5 and later · before 5.10.159
- linux linux kernel5.11 and later · before 5.15.83
- linux linux kernel5.16 and later · before 6.0.13
- linux linux kernel6.1
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.24affected
- 4ec2411980d0fd2995e8dea8a06fe57aa47523cb and later · before 99859947517e446058ad7243ee81d2f9801fa3ddaffected · git
- 4ec2411980d0fd2995e8dea8a06fe57aa47523cb and later · before ed773dd798bf720756d20021b8d8a4a3d7184bdaaffected · git
- 4ec2411980d0fd2995e8dea8a06fe57aa47523cb and later · before e6860c889f4ad50b6ab696f5ea154295d72cf27aaffected · git
- 4ec2411980d0fd2995e8dea8a06fe57aa47523cb and later · before e6e897d4fe2f89c0bd94600a40bedf5e6e75e050affected · git
- 4ec2411980d0fd2995e8dea8a06fe57aa47523cb and later · before f2dd60fd3fe98bd36a91b0c6e10bfe9d66258f84affected · git
- 4ec2411980d0fd2995e8dea8a06fe57aa47523cb and later · before d50b7914fae04d840ce36491d22133070b18cca9affected · git
- before 2.6.24not affected · semver
- 4.19.269 and later · up to and including 4.19.*not affected · semver
- 5.4.227 and later · up to and including 5.4.*not 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.4-1 | 6.1.4-1 |
| Red Hat:enterprise_linux:9::appstream | kernel-64k-debug-debuginfo | before 0:5.14.0-570.12.1.el9_6 | 0:5.14.0-570.12.1.el9_6 |
| Red Hat:enterprise_linux:9::appstream | kernel-64k-debug-devel | before 0:5.14.0-570.12.1.el9_6 | 0:5.14.0-570.12.1.el9_6 |
| Red Hat:enterprise_linux:9::appstream | kernel-64k-debug-devel-matched | before 0:5.14.0-570.12.1.el9_6 | 0:5.14.0-570.12.1.el9_6 |
| Red Hat:enterprise_linux:9::appstream | kernel-64k-debuginfo | before 0:5.14.0-570.12.1.el9_6 | 0:5.14.0-570.12.1.el9_6 |
| Red Hat:enterprise_linux:9::appstream | kernel-64k-devel | before 0:5.14.0-570.12.1.el9_6 | 0:5.14.0-570.12.1.el9_6 |
| Red Hat:enterprise_linux:9::appstream | kernel-64k-devel-matched | before 0:5.14.0-570.12.1.el9_6 | 0:5.14.0-570.12.1.el9_6 |
| Red Hat:enterprise_linux:9::appstream | kernel-debug-debuginfo | before 0:5.14.0-570.12.1.el9_6 | 0:5.14.0-570.12.1.el9_6 |
| Red Hat:enterprise_linux:9::appstream | kernel-debug-devel | before 0:5.14.0-570.12.1.el9_6 | 0:5.14.0-570.12.1.el9_6 |
| Red Hat:enterprise_linux:9::appstream | kernel-debug-devel-matched | before 0:5.14.0-570.12.1.el9_6 | 0:5.14.0-570.12.1.el9_6 |
| Red Hat:enterprise_linux:9::appstream | kernel-debuginfo | before 0:5.14.0-570.12.1.el9_6 | 0:5.14.0-570.12.1.el9_6 |
| Red Hat:enterprise_linux:9::appstream | kernel-debuginfo-common-aarch64 | before 0:5.14.0-570.12.1.el9_6 | 0:5.14.0-570.12.1.el9_6 |
| Red Hat:enterprise_linux:9::appstream | kernel-debuginfo-common-ppc64le | before 0:5.14.0-570.12.1.el9_6 | 0:5.14.0-570.12.1.el9_6 |
| Red Hat:enterprise_linux:9::appstream | kernel-debuginfo-common-s390x | before 0:5.14.0-570.12.1.el9_6 | 0:5.14.0-570.12.1.el9_6 |
| Red Hat:enterprise_linux:9::appstream | kernel-debuginfo-common-x86_64 | before 0:5.14.0-570.12.1.el9_6 | 0:5.14.0-570.12.1.el9_6 |
| Red Hat:enterprise_linux:9::appstream | kernel-devel | before 0:5.14.0-570.12.1.el9_6 | 0:5.14.0-570.12.1.el9_6 |
| Red Hat:enterprise_linux:9::appstream | kernel-devel-matched | before 0:5.14.0-570.12.1.el9_6 | 0:5.14.0-570.12.1.el9_6 |
| Red Hat:enterprise_linux:9::appstream | kernel-doc | before 0:5.14.0-570.12.1.el9_6 | 0:5.14.0-570.12.1.el9_6 |
| Red Hat:enterprise_linux:9::appstream | kernel-rt-64k-debug-debuginfo | before 0:5.14.0-570.12.1.el9_6 | 0:5.14.0-570.12.1.el9_6 |
| Red Hat:enterprise_linux:9::appstream | kernel-rt-64k-debuginfo | before 0:5.14.0-570.12.1.el9_6 | 0:5.14.0-570.12.1.el9_6 |
| Red Hat:enterprise_linux:9::appstream | kernel-rt-debug-debuginfo | before 0:5.14.0-570.12.1.el9_6 | 0:5.14.0-570.12.1.el9_6 |
| Red Hat:enterprise_linux:9::appstream | kernel-rt-debuginfo | before 0:5.14.0-570.12.1.el9_6 | 0:5.14.0-570.12.1.el9_6 |
| Red Hat:enterprise_linux:9::appstream | kernel-tools-debuginfo | before 0:5.14.0-570.12.1.el9_6 | 0:5.14.0-570.12.1.el9_6 |
| Red Hat:enterprise_linux:9::appstream | kernel-zfcpdump-debuginfo | before 0:5.14.0-570.12.1.el9_6 | 0:5.14.0-570.12.1.el9_6 |
+72
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- 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
- CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV83Now
Published before and after this one in the same product
- ← EarlierCVE-2022-48967Oct 21, 2024 · NFC: nci: Bounds check struct nfc_target arrays28Monitor
- ← EarlierCVE-2022-48968Oct 21, 2024 · octeontx2-pf: Fix potential memory leak in otx2_init_tc()22Monitor
- Later →CVE-2022-48970Oct 21, 2024 · af_unix: Get user_ns from in_skb in unix_diag_get_exact().22Monitor
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 | 99859947517e446058ad7243ee81d2f9801fa3dd | Vendor (CNA) |
| Linux Linux | d50b7914fae04d840ce36491d22133070b18cca9 | Vendor (CNA) |
| Linux Linux | e6860c889f4ad50b6ab696f5ea154295d72cf27a | Vendor (CNA) |
| Linux Linux | e6e897d4fe2f89c0bd94600a40bedf5e6e75e050 | Vendor (CNA) |
| Linux Linux | ed773dd798bf720756d20021b8d8a4a3d7184bda | Vendor (CNA) |
| Linux Linux | f2dd60fd3fe98bd36a91b0c6e10bfe9d66258f84 | Vendor (CNA) |
| debian:linux | 6.1.4-1 · Debian:12 | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:5.14.0-570.12.1.el9_6 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:5.14.0-570.12.1.el9_6 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:5.14.0-570.12.1.el9_6 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:5.14.0-570.12.1.el9_6 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:5.14.0-570.12.1.el9_6 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:5.14.0-570.12.1.el9_6 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:5.14.0-570.12.1.el9_6 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:5.14.0-570.12.1.el9_6 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:5.14.0-570.12.1.el9_6 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:5.14.0-570.12.1.el9_6 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-aarch64 | 0:5.14.0-570.12.1.el9_6 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-ppc64le | 0:5.14.0-570.12.1.el9_6 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| suse:kernel-default | 4.12.14-122.234.1 · SUSE:Linux Enterprise Live Patching 12 SP5 | Package registry (OSV) |
| suse:kernel-source | 4.12.14-122.234.1 · SUSE:Linux Enterprise Server 12 SP5-LTSS | Package registry (OSV) |
| suse:kernel-syms | 4.12.14-122.234.1 · SUSE:Linux Enterprise Server 12 SP5-LTSS | Package registry (OSV) |
| suse:kgraft-patch-SLE12-SP5_Update_62 | 1-8.3.1 · SUSE:Linux Enterprise Live Patching 12 SP5 | 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
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.
- 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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/d50b7914fae04d840ce36491d22133070b18cca9
- git.kernel.org/stable/c/e6860c889f4ad50b6ab696f5ea154295d72cf27a
- git.kernel.org/stable/c/e6e897d4fe2f89c0bd94600a40bedf5e6e75e050
- git.kernel.org/stable/c/ed773dd798bf720756d20021b8d8a4a3d7184bda
- git.kernel.org/stable/c/f2dd60fd3fe98bd36a91b0c6e10bfe9d66258f84
Vendor advisories and official records. Exploit/PoC links are deliberately left out.