linux-kernel - Re: [BUG] x86: apic: Possible null pointer dereference by apic_ack

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Sun, 11 Oct 2015 10:30:59 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	William Breathitt Gray <vilhelm.gray@...il.com>
cc:	mingo@...hat.com, hpa@...or.com, jiang.liu@...ux.intel.com,
	x86@...nel.org, linux-kernel@...r.kernel.org
Subject: Re: [BUG] x86: apic: Possible null pointer dereference by
 apic_ack_edge

On Sat, 10 Oct 2015, William Breathitt Gray wrote:
> In mainline kernel version 4.3-rc4, the following line located in the
> apic_ack_edge function definition can result in a null pointer dereference:
> 
>         irq_complete_move(irqd_cfg(data));
>         
> The irqd_cfg function may return a value of NULL.

data is never NULL when apic_ack_edge() is called.

Thanks,

	tglx
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/