Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 9 days later

    Published

  3. · 19 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-47666, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (15 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 869ddbdcae3b4fb83b99889abae31544c149b210 – < ddc501f4130f4baa787cb6cfa309af697179f475
    • affected 869ddbdcae3b4fb83b99889abae31544c149b210 – < a5d954802bda1aabcba49633cd94bad91c94113f
    • affected 869ddbdcae3b4fb83b99889abae31544c149b210 – < e23ee0cc5bded07e700553aecc333bb20c768546
    • affected 869ddbdcae3b4fb83b99889abae31544c149b210 – < 7b1d779647afaea9185fa2f150b1721e7c1aae89
    • affected 869ddbdcae3b4fb83b99889abae31544c149b210 – < f14d3e1aa613311c744af32d75125e95fc8ffb84
    • affected 869ddbdcae3b4fb83b99889abae31544c149b210 – < e4f949ef1516c0d74745ee54a0f4882c1f6c7aea
  • Linux · Linux

    • affected 4.15
    • unaffected < 4.15
    • unaffected 5.10.247 – ≤ 5.10.*
    • unaffected 5.15.197 – ≤ 5.15.*
    • unaffected 6.1.159 – ≤ 6.1.*
    • unaffected 6.6.51 – ≤ 6.6.*
    • unaffected 6.10.10 – ≤ 6.10.*
    • unaffected 6.11 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-47666 badge
[![CVE-2024-47666](https://cveledger.app/badge/CVE-2024-47666.svg)](https://cveledger.app/cve/CVE-2024-47666)

Record last updated .