Skip to content
statance
MenuClose
unknown

CVE-2026-99439

media: rc: Ensure registered is cleared in error path

Published 19 Nov 2026 · Source updated 19 Nov 2026 · Retrieved 2026-11-19 15:23 UTC

Monitor this CVE ↗Full CVE monitoring on Pro and Business

What happened?

In the Linux kernel, the following vulnerability has been resolved:

media: rc: Ensure registered is cleared in error path

If rc_register_device() fails, ensure that registered is not set to true. If lirc_register() succeeded, then userspace could have an open file descriptor open. This leads to a use-after-free.

lirc_unregister() must be called with registered = false, else there is a possibility that an fd is open and polling, which would never return POLLERR unless registered is false.

Note that registered must be changed under dev->lock, many functions read registered under lock (e.g. lirc_ioctl).

Description supplied by CVE Program. Formatting is simplified; follow the original advisory for full details.

Affected software and versions

Source-provided software and version information
SoftwareVersion informationFixed version
LinuxLinuxaffected: 75977f5f5c4974c72bbedefbf09ad33ebbaa36f1 to < 4c94661218f2accf309372cac59ebe9e21853349; affected: e250b672d40a9e0d97a8895cbb301248bea0fce6 to < 63644a8b70dab7e67a8a6f563b7df9647324a41f; affected: dccc0c3ddf8f16071736f98a7d6dd46a2d43e037 to < 7a6e8c9726dfd1cb284708f7b179a6bc9bcd6e0e; affected: dccc0c3ddf8f16071736f98a7d6dd46a2d43e037 to < 37efd09ba2c62e46e3a3a793025c186f8cd1a417; affected: a7becb58f6b8a3a3efe5d3acfd52e2c107de6772; affected: 6.12.93 to < 6.12.117; affected: 6.18.35 to < 6.18.61; affected: 6.6.143 to < 6.7See vendor advisory
LinuxLinuxaffected: 7.1; unaffected: 0 to < 7.1; unaffected: 6.12.117 to ≤ 6.12.*; unaffected: 6.18.61 to ≤ 6.18.*; unaffected: 7.3.2 to ≤ 7.3.*; unaffected: 7.4-rc1 to ≤ *See vendor advisory

Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.

Is it being exploited?

This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.

CISA data retrieved 2026-11-19 21:16 UTC. Check CISA ↗

How to respond

  1. Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
  2. Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
  3. Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.

Sources and remediation references

This public advisory does not determine whether a particular server is affected. Records are refreshed as sources change; verify urgent decisions against the original advisory.

← Browse the public CVE feed