Hello Lucas,
On 7/12/19 3:26 PM, Lucas Stach wrote:
> Find_next_bit works on a long type, which causes a OOB read on the
> u32 input when used on ARM64.
>
> Signed-off-by: Lucas Stach <l.stach@xxxxxxxxxxxxxx>
> ---
> drivers/pci/controller/dwc/pcie-designware-host.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/pci/controller/dwc/pcie-designware-host.c b/drivers/pci/controller/dwc/pcie-designware-host.c
> index 77db32529319..81a2139d68d6 100644
> --- a/drivers/pci/controller/dwc/pcie-designware-host.c
> +++ b/drivers/pci/controller/dwc/pcie-designware-host.c
> @@ -78,15 +78,16 @@ static struct msi_domain_info dw_pcie_msi_domain_info = {
> irqreturn_t dw_handle_msi_irq(struct pcie_port *pp)
> {
> int i, pos, irq;
> - u32 val, num_ctrls;
> + u32 num_ctrls;
> irqreturn_t ret = IRQ_NONE;
> + unsigned long val;
>
> num_ctrls = pp->num_vectors / MAX_MSI_IRQS_PER_CTRL;
>
> for (i = 0; i < num_ctrls; i++) {
> dw_pcie_rd_own_conf(pp, PCIE_MSI_INTR0_STATUS +
> (i * MSI_REG_CTRL_BLOCK_SIZE),
> - 4, &val);
> + 4, (u32 *)&val);
Wouldn't this still be wrong on big-endian 64-bit systems?
You're writing the first 4 bytes here, leaving the higher 4 uninitialized.
find_next_bit will read the lowest-valued 32-bits, i.e. the highest
four on ARM64, which are uninitialized.
> if (!val)
> continue;
>
>
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
