Patch "clk: zynqmp: Fix stack-out-of-bounds in strncpy`" has been added to the 5.15-stable tree

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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

    clk: zynqmp: Fix stack-out-of-bounds in strncpy`

to the 5.15-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:
     clk-zynqmp-fix-stack-out-of-bounds-in-strncpy.patch
and it can be found in the queue-5.15 subdirectory.

If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@xxxxxxxxxxxxxxx> know about it.



commit 609855a73cbd05aca59b01447294fa91a6555c8c
Author: Ian Nam <young.kwan.nam@xxxxxxxxxx>
Date:   Tue May 10 12:31:54 2022 +0530

    clk: zynqmp: Fix stack-out-of-bounds in strncpy`
    
    [ Upstream commit dd80fb2dbf1cd8751efbe4e53e54056f56a9b115 ]
    
    "BUG: KASAN: stack-out-of-bounds in strncpy+0x30/0x68"
    
    Linux-ATF interface is using 16 bytes of SMC payload. In case clock name is
    longer than 15 bytes, string terminated NULL character will not be received
    by Linux. Add explicit NULL character at last byte to fix issues when clock
    name is longer.
    
    This fixes below bug reported by KASAN:
    
     ==================================================================
     BUG: KASAN: stack-out-of-bounds in strncpy+0x30/0x68
     Read of size 1 at addr ffff0008c89a7410 by task swapper/0/1
    
     CPU: 1 PID: 1 Comm: swapper/0 Not tainted 5.4.0-00396-g81ef9e7-dirty #3
     Hardware name: Xilinx Versal vck190 Eval board revA (QSPI) (DT)
     Call trace:
      dump_backtrace+0x0/0x1e8
      show_stack+0x14/0x20
      dump_stack+0xd4/0x108
      print_address_description.isra.0+0xbc/0x37c
      __kasan_report+0x144/0x198
      kasan_report+0xc/0x18
      __asan_load1+0x5c/0x68
      strncpy+0x30/0x68
      zynqmp_clock_probe+0x238/0x7b8
      platform_drv_probe+0x6c/0xc8
      really_probe+0x14c/0x418
      driver_probe_device+0x74/0x130
      __device_attach_driver+0xc4/0xe8
      bus_for_each_drv+0xec/0x150
      __device_attach+0x160/0x1d8
      device_initial_probe+0x10/0x18
      bus_probe_device+0xe0/0xf0
      device_add+0x528/0x950
      of_device_add+0x5c/0x80
      of_platform_device_create_pdata+0x120/0x168
      of_platform_bus_create+0x244/0x4e0
      of_platform_populate+0x50/0xe8
      zynqmp_firmware_probe+0x370/0x3a8
      platform_drv_probe+0x6c/0xc8
      really_probe+0x14c/0x418
      driver_probe_device+0x74/0x130
      device_driver_attach+0x94/0xa0
      __driver_attach+0x70/0x108
      bus_for_each_dev+0xe4/0x158
      driver_attach+0x30/0x40
      bus_add_driver+0x21c/0x2b8
      driver_register+0xbc/0x1d0
      __platform_driver_register+0x7c/0x88
      zynqmp_firmware_driver_init+0x1c/0x24
      do_one_initcall+0xa4/0x234
      kernel_init_freeable+0x1b0/0x24c
      kernel_init+0x10/0x110
      ret_from_fork+0x10/0x18
    
     The buggy address belongs to the page:
     page:ffff0008f9be1c88 refcount:0 mapcount:0 mapping:0000000000000000 index:0x0
     raw: 0008d00000000000 ffff0008f9be1c90 ffff0008f9be1c90 0000000000000000
     raw: 0000000000000000 0000000000000000 00000000ffffffff
     page dumped because: kasan: bad access detected
    
     addr ffff0008c89a7410 is located in stack of task swapper/0/1 at offset 112 in frame:
      zynqmp_clock_probe+0x0/0x7b8
    
     this frame has 3 objects:
      [32, 44) 'response'
      [64, 80) 'ret_payload'
      [96, 112) 'name'
    
     Memory state around the buggy address:
      ffff0008c89a7300: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
      ffff0008c89a7380: 00 00 00 00 f1 f1 f1 f1 00 04 f2 f2 00 00 f2 f2
     >ffff0008c89a7400: 00 00 f3 f3 00 00 00 00 00 00 00 00 00 00 00 00
                              ^
      ffff0008c89a7480: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
      ffff0008c89a7500: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
     ==================================================================
    
    Signed-off-by: Ian Nam <young.kwan.nam@xxxxxxxxxx>
    Signed-off-by: Shubhrajyoti Datta <shubhrajyoti.datta@xxxxxxxxxx>
    Link: https://lore.kernel.org/r/20220510070154.29528-3-shubhrajyoti.datta@xxxxxxxxxx
    Acked-by: Michal Simek <michal.simek@xxxxxxx>
    Signed-off-by: Stephen Boyd <sboyd@xxxxxxxxxx>
    Signed-off-by: Sasha Levin <sashal@xxxxxxxxxx>

diff --git a/drivers/clk/zynqmp/clkc.c b/drivers/clk/zynqmp/clkc.c
index eb25303eefed..2c9da6623b84 100644
--- a/drivers/clk/zynqmp/clkc.c
+++ b/drivers/clk/zynqmp/clkc.c
@@ -710,6 +710,13 @@ static void zynqmp_get_clock_info(void)
 				  FIELD_PREP(CLK_ATTR_NODE_INDEX, i);
 
 		zynqmp_pm_clock_get_name(clock[i].clk_id, &name);
+
+		/*
+		 * Terminate with NULL character in case name provided by firmware
+		 * is longer and truncated due to size limit.
+		 */
+		name.name[sizeof(name.name) - 1] = '\0';
+
 		if (!strcmp(name.name, RESERVED_CLK_NAME))
 			continue;
 		strncpy(clock[i].clk_name, name.name, MAX_NAME_LEN);



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux