Menu

Star on GitHub · 3.4k

CVE-2026-98211

In the Linux kernel, the following vulnerability has been resolved: mmc: mmci: Fix use-after-free in busy-timeout work ux500_busy_complete() can queue ux500_busy_timeout_work for an R1b command,…

Published Oct 6, 2026EPSS 0.21%

Overview

CVE-2026-98211 is a known-severity vulnerability. It was published on October 6, 2026.

Technical description

In the Linux kernel, the following vulnerability has been resolved:

mmc: mmci: Fix use-after-free in busy-timeout work

ux500_busy_complete() can queue ux500_busy_timeout_work for an R1b

command, but mmci_remove() never cancels it. The work can subsequently

dereference the devm-allocated mmci_host after it has been released.

Mask the controller interrupts and disable the delayed work during

removal. This drains any queued instance and stops an IRQ handler that

is still in progress from queueing the work again once it has been

disabled.

This issue was found by an in-house static analysis tool.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-98211?

CVE-2026-98211 is a known-severity vulnerability. It was published on October 6, 2026.

How severe is CVE-2026-98211?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2026-98211?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-98211?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-98211 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

CyberStrike v2 is here — more intelligence, greater reach