platform/chrome: cros_ec_debugfs: Unregister panic notifier
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
platform/chrome: cros_ec_debugfs: Unregister panic notifier
cros_ec_debugfs_probe() registers notifier_panic with the EC panic notifier chain. The remove path tears down debugfs and the console log, but leaves the notifier registered. A later panic notification can call back into the removed instance and queue work that accesses released data.
Unregister the panic notifier before tearing down the debugfs and console log state.
This issue was found by a static analysis tool.
From the CVE record · Linux
The Linux kernel's cros_ec_debugfs removal path leaves a panic notifier registered after its instance is removed. If a panic notification occurs later, the callback can queue work that accesses released data. The input does not specify an attacker path, authentication requirement, or user interaction.
Engineers running Linux kernels with cros_ec_debugfs should check whether their versions are affected; no affected versions are specified.