[lkml]   [2003]   [May]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [CHECKER] 5 potential user-pointer errors that allow arbitrary reads from kernel

    Also, please note the word "Callstack" in the error reports doesn't really
    mean an actual call here. It means "functions are linked together if they
    are assigned to the same structure field".

    for example, the following error report is catched in this way:

    net/core/pktgen.c:proc_write treats its second arguemtn as tainted.
    we take it as a good code example, and require that all the other
    functions that are assigned to proc_dir_entry.write_proc must treat its
    second argument as tainted.

    sorry for the confusions.

    > ---------------------------------------------------------
    > [BUG] proc_dir_entry.write_proc can take tainted inputs
    > /home/junfeng/linux-2.5.63/drivers/usb/media/vicam.c:1117:vicam_write_proc_gain:
    > ERROR:TAINTED:1117:1117: passing tainted ptr 'buffer' to simple_strtoul
    > [Callstack:
    > /home/junfeng/linux-2.5.63/net/core/pktgen.c:991:vicam_write_proc_gain((tainted
    > 1))]
    > static int vicam_write_proc_gain(struct file *file, const char *buffer,
    > unsigned long count, void *data)
    > {
    > struct vicam_camera *cam = (struct vicam_camera *)data;
    > Error --->
    > cam->gain = simple_strtoul(buffer, NULL, 10);
    > return count;
    > }

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 13:35    [W:0.018 / U:2.000 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site