The flaw occurs when a PCI device is probed: the match() callback is invoked without holding the device lock, allowing the driver core to read the driver_override field without synchronization. This oversight can trigger a use‑after‑free or memory corruption, potentially letting an attacker execute arbitrary kernel code or corrupt system memory. The weakness corresponds to CWE‑416 and CWE‑364.

The vulnerability affects the Linux kernel. No specific version range is supplied, but any kernel containing the unprotected driver_override access during PCI probe is at risk until the patch is applied. The upstream commit referenced in the advisories contains the fix, so kernel releases newer than that commit are safe.

Based on the description, it is inferred that the vulnerability could be exploited by an attacker who can influence driver_override during PCI probe, such as through loading a malicious PCI driver or tampering with device firmware. An attacker with module‑loading privileges could trigger the race condition that leads to a use‑after‑free or memory corruption. The CVSS score of 7.8 indicates a high severity vulnerability. The EPSS score of less than 1% indicates a very low yet non‑zero exploitation probability, and the vulnerability is not listed in CISA’s KEV catalog. Although no exploitation has been reported, the flaw could allow privilege escalation or arbitrary kernel code execution if successfully exploited.