linux-kernel - Re: [PATCH] AppArmor: Modify Makefile to avoid Oops

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:	Thu, 18 Oct 2012 01:01:19 -0700
From:	John Johansen <john.johansen@...onical.com>
To:	Hiromu Yakura <hiromu1996@...il.com>
CC:	linux-security-module@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	James Morris <james.l.morris@...cle.com>
Subject: Re: [PATCH] AppArmor: Modify Makefile to avoid Oops

On 10/18/2012 12:19 AM, Hiromu Yakura wrote:
> In my environment, AppArmor cause Oops every time when cupsd launch.
> 
> This is the log of Oops:
> [  114.876511] general protection fault: 0000 [#1] SMP 

<snip>

> It seems that bad address was passed for the second argument of 
> audit_log_untrustedstring() at audit_cb() in capability.c:
>  52     audit_log_untrustedstring(ab, capability_names[sa->u.cap]);
> 
> The array "capability_names" is defined in capability_names.h but the content 
> of this is generated by Makefile from include/linux/capability.h
> However, capability.h was moved to include/uapi/linux/capability.h and because 
> of this, the array is empty.
> That's why, sa->u.cap become out of range this and segmentation fault caused.
> 
> Let's fix it.
> 
> Cc: James Morris <james.l.morris@...cle.com>
> Cc: John Johansen <john.johansen@...onical.com>
> 
Thanks Hiromu,

but this was fixed a few hours ago
http://marc.info/?t=135050396600008&r=1&w=2


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