CVE-2026-93051: misc: ad525x_dpot: use driver core groups for sysfs files
In the Linux kernel, the following vulnerability has been resolved:
misc: ad525xdpot: use driver core groups for sysfs files
addpotprobe() 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 devgroups for the I2C and SPI drivers and use an isvisible() 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.
Event History
Frequently Asked Questions
Which systems are exposed to this issue?
Systems using the Linux kernel AD525x digital potentiometer driver over I2C or SPI may be affected. Exposure depends on whether the relevant driver is present and a supported RDAC device is probed.
What condition leads to the vulnerability?
The issue is associated with the driver's manual creation of per-RDAC sysfs files and an optional command sysfs group during probe. Partial sysfs setup or teardown could leave sysfs state that the driver must manually track and remove.
What changes in the resolved implementation?
Device attributes are managed through driver-core dev_groups for both I2C and SPI drivers. An is_visible() callback limits exposed attributes to those supported by the detected device, while the driver core creates files after successful probe and removes them before driver data is freed.