Kernel use-after-free risk in sysfs init; affects widely used Linux kernel; could disrupt kernel stability across deployments.
CVE-2026-46264
Linux kernel use-after-free in sysfs init during devm_add_action_or_reset.
Is CVE-2026-46264 being exploited?
Not confirmed. CVE-2026-46264 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.11% probability of exploitation in the next 30 days.
How severe is CVE-2026-46264?
CVE-2026-46264 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-46264?
Yes. A fix has been recorded for CVE-2026-46264. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-46264 affect?
CVE-2026-46264 affects Linux kernel (drm xe/sriov). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-46264?
Update to patched kernel and reboot.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Kernel crash/DoS via premature cleanup in kobject during early sysfs init; requires local access to trigger.
Patch when possible
- affected>= 5c170a4d9c530e872f2f788d95258fbaa39b4415 and < 6ae479b1919ee9bd0560fc7af649932dd420d010
- affected>= 5c170a4d9c530e872f2f788d95258fbaa39b4415 and < bf7172cd25ed182f30af2cbb9f80c730dc717d8e
- affected6.19
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.