misc: ad525x_dpot: use driver core groups for sysfs files
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 4eb174bee6f8623fed1af0072f1bebfc3b513a52 · < c7ff7a70f405a3c6fde39ed00a36d9f4fecaf3ab| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
misc: ad525x_dpot: use driver core groups for sysfs files
ad_dpot_probe() creates per-RDAC sysfs files manually and then optionally creates the command sysfs group. This leaves probe responsible for rolling back partial sysfs state and makes remove responsible for matching every file that probe created.
Move the device attributes into driver core dev_groups for the I2C and SPI drivers and use an is_visible() callback to expose only the attributes supported by the probed device. With this shape, the driver core creates the sysfs files only after probe succeeds and removes them before the remove callback frees the driver data.
From the CVE record · Linux
The Linux kernel ad525x_dpot driver manually creates sysfs files during probe and removes them during device removal. The fix moves those files under driver core management so they are created only after probe succeeds and removed before driver data is freed. The input does not specify an attacker action or the conditions needed to exploit this issue.
Engineers running Linux kernels with the ad525x_dpot driver should check their versions; affected versions are not specified.