mmc: davinci: Don't strip remove function when driver is builtin
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ b4cff4549b7a8c5fc8b88e3493b6287555f0512c · < 55c421b364482b61c4c45313a535e61ed5ae4ea3| No fix yet |
| Linux Linux |
|
|
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)
From the CVE record · Linux
When the davinci MMC driver is built into the Linux kernel with CONFIG_MMC_DAVINCI=y, its remove callback is discarded. If the device is unbound, such as through sysfs or hotplug, cleanup is skipped and resources leak.
Check Linux kernel installations with the davinci MMC driver built in using CONFIG_MMC_DAVINCI=y; affected versions were not provided.