Skip to main content
CVE-2025-68819VulnerabilityPublished Updated

CVE-2025-68819: Linux kernel · media: dvb-usb: dtv5100: fix out-of-bounds in dtv5100_i2c_msg() rlen value is a

Source GCVE Database

0

Not known to be exploited · CVSS 7.8 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 2026-10-25.

What to do

AI-suggested

A fix has been applied to the Linux kernel to add proper range checking for the rlen parameter in dtv5100_i2c_msg(). Users and administrators should update to the latest patched kernel versions that include this fix. Patch status is not explicitly confirmed in the provided data; therefore, verify with the official Linux kernel advisories or vendor updates for the exact patched versions and apply them accordingly.

Description

A vulnerability in the Linux kernel's media subsystem for dvb-usb devices using the dtv5100 driver allows an out-of-bounds write due to improper validation of a user-controlled length value in the dtv5100_i2c_msg() function. This can lead to memory corruption. The issue arises because the rlen parameter is not checked against the size of the destination buffer, st->data. A fix has been implemented to add proper range checking to prevent this vulnerability.

References

Community reviews

Loading reviews…