Bug 2536371 (CVE-2026-92482) - CVE-2026-92482 kernel: pinctrl: mediatek: use devm_gpiochip_add_data() for GPIO chip
Summary: CVE-2026-92482 kernel: pinctrl: mediatek: use devm_gpiochip_add_data() for GP...
Keywords:
Status: NEW
Alias: CVE-2026-92482
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-09-17 17:35 UTC by OSIDB Bzimport
Modified: 2026-10-20 11:12 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-09-17 17:35:00 UTC
In the Linux kernel, the following vulnerability has been resolved:

pinctrl: mediatek: use devm_gpiochip_add_data() for GPIO chip

The gpio_chip is allocated with device-managed memory but registered with
the non-managed gpiochip_add_data(). This was harmless while the drivers
were built-in, but once they can be built as modules and unbound/rmmod'd,
devm frees the gpio_chip's memory while it is still registered, causing a
use-after-free.

Register it with devm_gpiochip_add_data() so it shares the same
device-managed lifecycle, which also lets the manual gpiochip_remove()
error paths go away.


Note You need to log in before you can comment on or make changes to this bug.