This is a note to let you know that I've just added the patch titled

    fs: prevent use after free in auditing when symlink following was denied

to the 3.6-stable tree which can be found at:
    
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary

The filename of the patch is:
     
fs-prevent-use-after-free-in-auditing-when-symlink-following-was-denied.patch
and it can be found in the queue-3.6 subdirectory.

If you, or anyone else, feels it should not be added to the stable tree,
please let <[email protected]> know about it.


>From ffd8d101a3a7d3f2e79deee1e342801703b6dc70 Mon Sep 17 00:00:00 2001
From: Sasha Levin <[email protected]>
Date: Thu, 4 Oct 2012 19:56:40 -0400
Subject: fs: prevent use after free in auditing when symlink following was 
denied

From: Sasha Levin <[email protected]>

commit ffd8d101a3a7d3f2e79deee1e342801703b6dc70 upstream.

Commit "fs: add link restriction audit reporting" has added auditing of failed
attempts to follow symlinks. Unfortunately, the auditing was being done after
the struct path structure was released earlier.

Signed-off-by: Sasha Levin <[email protected]>
Signed-off-by: Al Viro <[email protected]>
Cc: Dave Jones <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>

---
 fs/namei.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- a/fs/namei.c
+++ b/fs/namei.c
@@ -692,9 +692,9 @@ static inline int may_follow_link(struct
        if (parent->i_uid == inode->i_uid)
                return 0;
 
+       audit_log_link_denied("follow_link", link);
        path_put_conditional(link, nd);
        path_put(&nd->path);
-       audit_log_link_denied("follow_link", link);
        return -EACCES;
 }
 


Patches currently in stable-queue which might be from [email protected] are

queue-3.6/fs-handle-failed-audit_log_start-properly.patch
queue-3.6/fs-prevent-use-after-free-in-auditing-when-symlink-following-was-denied.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to