Bug 2348647 (CVE-2024-58006) - CVE-2024-58006 kernel: PCI: dwc: ep: Prevent changing BAR size/flags in pci_epc_set_bar()
Summary: CVE-2024-58006 kernel: PCI: dwc: ep: Prevent changing BAR size/flags in pci_e...
Keywords:
Status: NEW
Alias: CVE-2024-58006
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-02-27 03:06 UTC by OSIDB Bzimport
Modified: 2025-02-27 20:33 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2025-02-27 03:06:19 UTC
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.)

Comment 1 Mauro Matteo Cascella 2025-02-27 20:24:27 UTC
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2025022655-CVE-2024-58006-9855@gregkh/T


Note You need to log in before you can comment on or make changes to this bug.