CVE-2024-46761

pci/hotplug/pnv_php: Fix hotplug driver crash on Powernv

MEDIUM

5.5

CVSS Score

Published: September 18, 2024 at 07:12 AM UTC

Updated: June 17, 2026 at 07:55 AM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.5

Exploit prediction

EPSS 0.3%

SSVC

No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: pci/hotplug/pnv_php: Fix hotplug driver crash on Powernv The hotplug driver for powerpc (pci/hotplug/pnv_php.c) causes a kernel crash when we try to hot-unplug/disable the PCIe switch/bridge from the PHB. The crash occurs because although the MSI data structure has been released during disable/hot-unplug path and it has been assigned with NULL, still during unregistration the code was again trying to explicitly disable the MSI which causes the NULL pointer dereference and kernel crash. The patch fixes the check during unregistration path to prevent invoking pci_disable_msi/msix() since its data structure is already freed.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

v ≥ 4.10.2v ≥ 4.9.14v < 4.19.3224.10.2 ≤ v < 4.114.11 ≤ v < 4.19.3224.11 ≤ v < 5.10.2264.11 ≤ v < 5.15.1674.11 ≤ v < 5.4.2844.11 ≤ v < 6.1.1104.11 ≤ v < 6.10.104.11 ≤ v < 6.114.11 ≤ v < 6.6.514.20 ≤ v < 5.4.2844.9.14 ≤ v < 4.105.11 ≤ v < 5.15.1675.16 ≤ v < 6.1.1105.5 ≤ v < 5.10.2266.2 ≤ v < 6.6.516.7 ≤ v < 6.10.101fb738a3dc1304250c755e5e31715137c1c44c504.10.2 4.11 4.9.1449f4b08e61547a5ccd2db551d994c4503efe5666bc4c9766324a7e9fda48de58691796430c8511bf

Vendor states this is fixed in 335e35b748527f0c06ded9eebb65387f60647fda (fixed)

Vendor states this is fixed in 438d522227374042b5c8798f8ce83bbe479dca4d (fixed)

Vendor states this is fixed in 4eb4085c1346d19d4a05c55246eb93e74e671048 (fixed)

Vendor states this is fixed in b82d4d5c736f4fd2ed224c35f554f50d1953d21e (fixed)

Vendor states this is fixed in bc1faed19db95abf0933b104910a3fb01b138f59 (fixed)

Vendor states this is fixed in bfc44075b19740d372f989f21dd03168bfda0689 (fixed)

Vendor states this is fixed in c0d8094dc740cfacf3775bbc6a1c4720459e8de4 (fixed)

Vendor states this is fixed in c4c681999d385e28f84808bbf3a85ea8e982da55 (fixed)

Affected range stops below 4.10, so it looks safe — our inference, not a vendor statement

Vendor states this is fixed in 4.11 (unaffected)

Vendor states this is fixed in 4.19.322 (unaffected)

Vendor states this is fixed in 5.10.226 (unaffected)

Vendor states this is fixed in 5.15.167 (unaffected)

Vendor states this is fixed in 5.4.284 (unaffected)

Vendor states this is fixed in 6.1.110 (unaffected)

Vendor states this is fixed in 6.10.10 (unaffected)

Vendor states this is fixed in 6.11 (unaffected)

Vendor states this is fixed in 6.6.51 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references