drm/amd/display: Fix DM I2C teardown race
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.18.52, 7.2.6
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Fix DM I2C teardown race DM I2C adapters can remain visible to userspace while DM teardown is already in progress. A concurrent i2c-dev transfer may then enter amdgpu_dm_i2c_xfer() after the backing DM state has been torn down, leading to a NULL pointer dereference. Create a devres group around the DM I2C adapter lifetime and release it at the start of dm_hw_fini(), before HPD, IRQ, and DM state are torn down. This removes the I2C adapters first and waits for in-flight users to drain before the structures used by amdgpu_dm_i2c_xfer() disappear. This fixes a teardown ordering race seen during device removal: BUG: kernel NULL pointer dereference RIP: amdgpu_dm_i2c_xfer+0x122/0x1c0 [amdgpu] Call Trace: __i2c_transfer i2c_transfer i2cdev_ioctl_rdwr
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 5b3eca05cfb02ed0dbd7097c056fb08ce5f76fe3 · fixed in 8ee385305e8902fa6fbfd66b5a112238292567b6; From 5b3eca05cfb02ed0dbd7097c056fb08ce5f76fe3 · fixed in 6970ec944567f109ac4240f9aea58158ee8a18cd; From 5b3eca05cfb02ed0dbd7097c056fb08ce5f76fe3 · fixed in e4ae30a12aa95942814957d8bc1ce7366a7107d7
- Linux Linux
6.18
- KernelLinux
From 6.18.0 · fixed in 6.18.52; From 6.19.0 · fixed in 7.2.6