media: ipu6: Do not free aux device pdata after init
- 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.12.110, 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: media: ipu6: Do not free aux device pdata after init ipu6_bus_initialize_device() stores the isys/psys pdata pointer in struct ipu6_bus_device and initializes the auxiliary device. After that point, error unwinding must drop the auxiliary device reference and let ipu6_bus_release() free both the bus device and adev->pdata. The isys and psys init paths already call put_device() when MMU initialization fails, and ipu6_bus_add_device() calls auxiliary_device_uninit() on auxiliary_device_add() failure. Both paths therefore run the bus release callback. The extra kfree(pdata) in the callers can release the same object a second time. Remove the manual pdata frees after the auxiliary device has been initialized. This issue was found by a static analysis checker and confirmed by manual source review.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From cb3117b074aefb0320d8d728a0a7f277a121adbd · fixed in faa1eb97f0e66bf122f44b62be6b323f86333e9f; From cb3117b074aefb0320d8d728a0a7f277a121adbd · fixed in 5323ed5a7bb2568191ec676b2035b0396105aa05; From cb3117b074aefb0320d8d728a0a7f277a121adbd · fixed in 7d102d1f0631807a491a140f67c9628dea85dfd2; From cb3117b074aefb0320d8d728a0a7f277a121adbd · fixed in 9be07216af4cfc4813e1a46ce26407d31ea845de
- Linux Linux
6.10
- KernelLinux
From 6.10.0 · fixed in 6.12.110; From 6.13.0 · fixed in 6.18.52; From 6.19.0 · fixed in 7.2.6