In the Linux kernel, the following vulnerability has been resolved: mmc: davinci: Don't strip remove function when driver is builtin Using __exit for the remove function results in the remove callback being discarded with CONFIG_MMC_DAVINCI=y. When such a device gets unbound (e.g. using sysfs or hotplug), the driver is just removed without the cleanup being performed. This results in resource leaks. Fix it by compiling in the remove callback unconditionally. This also fixes a W=1 modpost warning: WARNING: modpost: drivers/mmc/host/davinci_mmc: section mismatch in reference: davinci_mmcsd_driver+0x10 (section: .data) -> davinci_mmcsd_remove (section: .exit.text)
The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor.
Link | Tags |
---|---|
https://git.kernel.org/stable/c/6ff7cfa02baabec907f6f29ea76634e6256d2ec4 | patch mailing list |
https://git.kernel.org/stable/c/aea35157bb9b825faa0432bd0f7fbea37ff39aa1 | patch mailing list |
https://git.kernel.org/stable/c/5ee241f72edc6dce5051a5f100eab6cc019d873e | patch mailing list |
https://git.kernel.org/stable/c/7590da4c04dd4aa9c262da0231e978263861c6eb | patch mailing list |
https://git.kernel.org/stable/c/1d5ed0efe51d36b9ae9b64f133bf41cdbf56f584 | patch mailing list |
https://git.kernel.org/stable/c/55c421b364482b61c4c45313a535e61ed5ae4ea3 | patch mailing list |