CVE-2024-58006
Linux Kernel vulnerability
- Published27 Feb 2025
Description
In the Linux kernel, the following vulnerability has been resolved: PCI: dwc: ep: Prevent changing BAR size/flags in pci_epc_set_bar() In commit 4284c88fff0e ("PCI: designware-ep: Allow pci_epc_set_bar() update inbound map address") set_bar() was modified to support dynamically changing the backing physical address of a BAR that was already configured. This means that set_bar() can be called twice, without ever calling clear_bar() (as calling clear_bar() would clear the BAR's PCI address assigned by the host). This can only be done if the new BAR size/flags does not differ from the existing BAR configuration. Add these missing checks. If we allow set_bar() to set e.g. a new BAR size that differs from the existing BAR size, the new address translation range will be smaller than the BAR size already determined by the host, which would mean that a read past the new BAR size would pass the iATU untranslated, which could allow the host to read memory not belonging to the new struct pci_epf_bar. While at it, add comments which clarifies the support for dynamically changing the physical address of a BAR. (Which was also missing.)
CVSS 3.1 breakdown
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HAffected products
Remediation
References
Frequently asked
Is CVE-2024-58006 being actively exploited?
CVE-2024-58006 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.24%.
How severe is CVE-2024-58006?
CVE-2024-58006 has a CVSS 3.1 base score of 9.6, rated critical. EPSS estimates a 0.24% probability of exploitation.
Which products are affected by CVE-2024-58006?
Affected products include Linux Kernel.
How do I fix CVE-2024-58006?
Upgrade affected software to a fixed version, for example Linux Kernel 6.12.14 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2024-58006 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.