CVE-2024-47666

published 9 Oct 2024 · updated 11 May 2026

scsi: pm80xx: Set phy->enable_completion only when we wait for it

5.5MediumCVSS 5.5EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 7b1d779647afaea9185fa2f150b1721e7c1aae89, Kernel a5d954802bda1aabcba49633cd94bad91c94113f, Kernel ddc501f4130f4baa787cb6cfa309af697179f475 and 3 more.

In the Linux kernel, the following vulnerability has been resolved: scsi: pm80xx: Set phy->enable_completion only when we wait for it pm8001_phy_control() populates the enable_completion pointer with a stack address, sends a PHY_LINK_RESET / PHY_HARD_RESET, waits 300 ms, and returns. The problem arises when a phy control response comes late. After 300 ms the pm8001_phy_control() function returns and the passed enable_completion stack address is no longer valid. Late phy control response invokes complete() on a dangling enable_completion pointer which leads to a kernel crash.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=4.15, >=869ddbdcae3b4fb83b99889abae31544c149b210 <7b1d779647afaea9185fa2f150b1721e7c1aae89, >=869ddbdcae3b4fb83b99889abae31544c149b210 <a5d954802bda1aabcba49633cd94bad91c94113f, >=869ddbdcae3b4fb83b99889abae31544c149b210 <ddc501f4130f4baa787cb6cfa309af697179f475, >=869ddbdcae3b4fb83b99889abae31544c149b210 <e23ee0cc5bded07e700553aecc333bb20c768546, >=869ddbdcae3b4fb83b99889abae31544c149b210 <e4f949ef1516c0d74745ee54a0f4882c1f6c7aea, >=869ddbdcae3b4fb83b99889abae31544c149b210 <f14d3e1aa613311c744af32d75125e95fc8ffb847b1d779647afaea9185fa2f150b1721e7c1aae89, a5d954802bda1aabcba49633cd94bad91c94113f, ddc501f4130f4baa787cb6cfa309af697179f475, e23ee0cc5bded07e700553aecc333bb20c768546, e4f949ef1516c0d74745ee54a0f4882c1f6c7aea, f14d3e1aa613311c744af32d75125e95fc8ffb84

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2024-47666 severity on Zeptric[![CVE-2024-47666](https://zeptric.io/badge/cve/CVE-2024-47666.svg)](https://zeptric.io/cve/CVE-2024-47666)