From: Richard Weinberger <richard@nod.at>
To: Andy Lutomirski <luto@amacapital.net>
Cc: the arch/x86 maintainers <x86@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Out-of-bounds access in vread_hpet()
Date: Tue, 10 Jun 2014 08:36:34 +0200 [thread overview]
Message-ID: <5396A772.1060103@nod.at> (raw)
FYI:
________________________________________________________________________________________________________
*** CID 1222081: Out-of-bounds access (ARRAY_VS_SINGLETON)
/arch/x86/vdso/vclock_gettime.c: 38 in vread_hpet()
32 #ifdef CONFIG_HPET_TIMER
33 extern u8 hpet_page
34 __attribute__((visibility("hidden")));
35
36 static notrace cycle_t vread_hpet(void)
37 {
>>> CID 1222081: Out-of-bounds access (ARRAY_VS_SINGLETON)
>>> Using "&hpet_page" as an array. This might corrupt or misinterpret adjacent memory locations.
38 return *(const volatile u32 *)(&hpet_page + HPET_COUNTER);
39 }
40 #endif
41
42 #ifndef BUILD_VDSO32
43
Thanks,
//richard
next reply other threads:[~2014-06-10 6:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-10 6:36 Richard Weinberger [this message]
2014-06-10 16:13 ` Out-of-bounds access in vread_hpet() Andy Lutomirski
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=5396A772.1060103@nod.at \
--to=richard@nod.at \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=peterz@infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox