Skip to main content
VulnerabilityPublished Updated

CVE-2025-38044: Linux kernel · media: cx231xx: set device_caps for 417

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in e43fd82bb2110bf9d13d800cdc49cceddfd0ede5 : update Linux kernel when convenient.

Data as of 5 Nov 2026, 21:04 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-05.

Patch
Available – fixed in e43fd82bb2110bf9d13d800cdc49cceddfd0ede5, c91447e35b9bea60bda4408c48e7891d14351021, a79efc44b51432490538a55b9753a721f7d3ea42 +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 8c3854d03bd7b86e8f36e6d9b07b4a6bc20deccd, < e43fd82bb2110bf9d13d800cdc49cceddfd0ede5
Fixed in
  • e43fd82bb2110bf9d13d800cdc49cceddfd0ede5
LinuxLinuxAffected
  • ≥ 8c3854d03bd7b86e8f36e6d9b07b4a6bc20deccd, < c91447e35b9bea60bda4408c48e7891d14351021
Fixed in
  • c91447e35b9bea60bda4408c48e7891d14351021
LinuxLinuxAffected
  • ≥ 8c3854d03bd7b86e8f36e6d9b07b4a6bc20deccd, < a79efc44b51432490538a55b9753a721f7d3ea42
Fixed in
  • a79efc44b51432490538a55b9753a721f7d3ea42
LinuxLinuxAffected
  • ≥ 8c3854d03bd7b86e8f36e6d9b07b4a6bc20deccd, < 4731d5328f507ae8fd8a57abbca9119ec7a8d665
Fixed in
  • 4731d5328f507ae8fd8a57abbca9119ec7a8d665
LinuxLinuxAffected
  • ≥ 8c3854d03bd7b86e8f36e6d9b07b4a6bc20deccd, < 0884dd3abbe80307a2d4cbdbe5e312be164f8adb
Fixed in
  • 0884dd3abbe80307a2d4cbdbe5e312be164f8adb
LinuxLinuxAffected
  • ≥ 8c3854d03bd7b86e8f36e6d9b07b4a6bc20deccd, < 9d1a5be86dbe074bd8dd6bdd63a99d6bb66d5930
Fixed in
  • 9d1a5be86dbe074bd8dd6bdd63a99d6bb66d5930

Description

In the Linux kernel, the following vulnerability has been resolved: media: cx231xx: set device_caps for 417 The video_device for the MPEG encoder did not set device_caps. Add this, otherwise the video device can't be registered (you get a WARN_ON instead). Not seen before since currently 417 support is disabled, but I found this while experimenting with it.

References

Community reviews

Loading reviews…