CVE-2026-99470
media: cx23885: unregister DVB bus when SP2 CI setup fails
What happened?
In the Linux kernel, the following vulnerability has been resolved:
media: cx23885: unregister DVB bus when SP2 CI setup fails
The DVBSKY S950C, DVBSKY T980C and TechnoTrend CT2-4500 CI paths register the DVB bus before attaching their SP2 CI client. If that client cannot be created, bound, or pinned, the current error path removes the I2C frontend components and only deallocates the frontend list, leaving the registered DVB adapter behind. Removing an I2C demod before unregistering the DVB bus can also expose the use-after-free ordering fixed for the normal remove path.
Unregister the DVB bus immediately when SP2 CI setup fails, before the existing I2C client cleanup. The bus helper empties the frontend list, so the later frontend deallocation has nothing left to release. Keep failures from vb2_dvb_register_bus() on the existing cleanup path. Also release an unbound SP2 client and propagate the actual I2C creation or CI registration error.
This issue was identified during our ongoing static-analysis research while reviewing kernel code.
Affected software and versions
| Software | Version information | Fixed version |
|---|---|---|
| LinuxLinux | affected: 2b0aac3011bc7a9db27791bed4978554263ef079 to < 262bca0d6761f4fd8755e8e223ea666d6cb81f1b; affected: 2b0aac3011bc7a9db27791bed4978554263ef079 to < cbe537c64b8fb1d0cf4bee20f89204fa51e384e5; affected: 2b0aac3011bc7a9db27791bed4978554263ef079 to < 47b32af13359e1bf859a449daa7a1b389bd93cb9; affected: 2b0aac3011bc7a9db27791bed4978554263ef079 to < 22f552ff726a82a086be4ef02ce5099a0e8624b6 | See vendor advisory |
| LinuxLinux | affected: 4.0; unaffected: 0 to < 4.0; 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.
How to respond
- Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
- 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.
- Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.
Sources and remediation references
- https://www.cve.org/CVERecord?id=CVE-2026-99470
- https://git.kernel.org/stable/c/262bca0d6761f4fd8755e8e223ea666d6cb81f1b
- https://git.kernel.org/stable/c/cbe537c64b8fb1d0cf4bee20f89204fa51e384e5
- https://git.kernel.org/stable/c/47b32af13359e1bf859a449daa7a1b389bd93cb9
- https://git.kernel.org/stable/c/22f552ff726a82a086be4ef02ce5099a0e8624b6