[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID:
<PH7PR11MB57687107A3D1BBB00B9A62D6A0722@PH7PR11MB5768.namprd11.prod.outlook.com>
Date: Wed, 17 Jan 2024 15:21:58 +0000
From: "Yang, Chenyuan" <cy54@...inois.edu>
To: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-mtd@...ts.infradead.org" <linux-mtd@...ts.infradead.org>
Subject: WARNING: zero-size vmalloc in ubi_read_volume_table
Hello,
We detected one crash, “WARNING: zero-size vmalloc in ubi_read_volume_table” for the volume management system UBI (under linux/drivers/mtd/ubi) by using our generated syscall specification for it.
This crash is triggered by `create_empty_lvol` (https://elixir.bootlin.com/linux/v6.7/source/drivers/mtd/ubi/vtbl.c#L484), which allocates a zero-size memory by using `vzalloc`. Additionally, this issue is associated with the `/dev/ubi_ctrl` driver, particularly when using IOCTL with the command value UBI_IOCATT. The size allocated can be manipulated through the `ubi_attach_req` argument by altering the `vid_hdr_offset` and `max_beb_per1024` fields.
To fix this issue, it would be better to implement a check step in the `create_empty_lvol` function.
The crash is reproducible by a C program, which is attached in the file.
If you have any questions or require more information, please feel free to contact us.
Best,
Chenyuan
Content of type "text/html" skipped
Download attachment "repro.cprog" of type "application/octet-stream" (1225 bytes)
Download attachment "repro.log" of type "application/octet-stream" (15879 bytes)
Download attachment "repro.prog" of type "application/octet-stream" (640 bytes)
Download attachment "repro.report" of type "application/octet-stream" (2569 bytes)
Powered by blists - more mailing lists