From: William Breathitt Gray <vilhelm.gray@gmail.com>
To: tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
jiang.liu@linux.intel.com
Cc: x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [BUG] x86: apic: Possible null pointer dereference by apic_ack_edge
Date: Sat, 10 Oct 2015 16:54:51 -0400 [thread overview]
Message-ID: <56197B1B.60304@gmail.com> (raw)
Hello,
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. If NULL is passed to the
irq_complete_move function, then the struct apic_chip_data pointer 'data' of
the __irq_complete_move function will be defined, and subsequently dereferenced,
based on this incorrect NULL value passed through the 'cfg' parameter:
data = container_of(cfg, struct apic_chip_data, cfg);
if (likely(!data->move_in_progress))
Sincerely,
William Breathitt Gray
next reply other threads:[~2015-10-10 20:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-10 20:54 William Breathitt Gray [this message]
2015-10-11 8:30 ` [BUG] x86: apic: Possible null pointer dereference by apic_ack_edge Thomas Gleixner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56197B1B.60304@gmail.com \
--to=vilhelm.gray@gmail.com \
--cc=hpa@zytor.com \
--cc=jiang.liu@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.