PatchSiren cyber security CVE debrief
CVE-2026-98106 Linux CVE debrief
A Linux kernel vulnerability allows a device-private folio to be migrated multiple times, potentially causing a soft lockup and RCU stall. The issue arises when a folio is migrated to system memory by a CPU fault and remains reachable through the raw-PFN eviction path. Successfully migrated device-private folios are now marked to prevent double migration.
- Vendor
- Linux
- Product
- Unknown
- CVSS
- Unknown
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-09-25
- Original CVE updated
- 2026-09-25
- Advisory published
- 2026-09-25
- Advisory updated
- 2026-09-25
Who should care
Linux kernel administrators and developers should assess exposure and prioritize verification of affected systems, especially those using device-private folios, to prevent potential soft lockup and RCU stall issues. They should verify Linux kernel versions and configurations for exposure, assess system vulnerability to device-private folio migration issues, and apply patches or updates to address the vulnerability. Additionally, they should review compens
Why it matters
Linux kernel administrators and developers should assess exposure and prioritize verification of affected systems, especially those using device-private folios, to prevent potential soft lockup and RCU stall.
- Potential soft lockup and RCU stall
- Verification of affected systems required
- Patch application necessary to prevent double migration
Technical summary
The Linux kernel vulnerability CVE-2026-98106 allows a device-private folio to be migrated multiple times, potentially causing a soft lockup and RCU stall. A patch has been applied to mark successfully migrated device-private folios and prevent double migration. This patch ensures that successfully migrated device-private folios are marked to prevent double migration, which can cause soft lockup and RCU stall issues in the Linux kernel. The patch modifies the migration process to avoid attempting to migrate the same folio multiple times.
Defensive priority
Linux kernel administrators and developers should assess exposure and prioritize verification of affected systems, especially those using device-private folios.
Recommended defensive actions
- Verify Linux kernel versions and configurations for exposure
- Assess system vulnerability to device-private folio migration issues
- Apply patches or updates to address the vulnerability
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
Evidence notes
The issue was observed as a soft lockup and RCU stall with a specific call trace. A patch has been applied to mark successfully migrated device-private folios and prevent double migration. Linux kernel administrators and developers should verify affected systems, especially those using device-private folios, and assess exposure to potential soft lockup and RCU stall.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-98106 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-98106
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-98106 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-98106
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/62451f540c46bf5c51143a1c8681b472608bd54d
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/c4126f1db36e6b2e1c79b0e30a8a2de91c568f4c
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.