linux-kernel - [BUG] gcov causes vread_tsc to increment kernel memory

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-next>] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.00.0907011245230.22887@gandalf.stny.rr.com>
Date:	Wed, 1 Jul 2009 12:54:41 -0400 (EDT)
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Peter Oberparleiter <oberpar@...ux.vnet.ibm.com>
cc:	LKML <linux-kernel@...r.kernel.org>
Subject: [BUG] gcov causes vread_tsc to increment kernel memory


On bootup of the latest kernel my init segfaults. Debugging it, I found 
that vread_tsc (a vsyscall) increments some strange kernel memory:

0000000000000000 <vread_tsc>:
   0:   55                      push   %rbp
   1:   48 ff 05 00 00 00 00    incq   0(%rip)        # 8 <vread_tsc+0x8>
                        4: R_X86_64_PC32        .bss+0x3c
   8:   48 89 e5                mov    %rsp,%rbp
   b:   66 66 90                xchg   %ax,%ax
   e:   48 ff 05 00 00 00 00    incq   0(%rip)        # 15 <vread_tsc+0x15>
                        11: R_X86_64_PC32       .bss+0x44
  15:   66 66 90                xchg   %ax,%ax
  18:   48 ff 05 00 00 00 00    incq   0(%rip)        # 1f <vread_tsc+0x1f>
                        1b: R_X86_64_PC32       .bss+0x4c
  1f:   0f 31                   rdtsc  
	

Those "incq" is very bad to happen in vsyscall memory, since userspace can 
not modify it. You need to make something prevent profiling of vsyscall 
memory (like I do with ftrace).

-- Steve

--
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/