CVE-2023-54066: media: dvb-usb-v2: gl861: Fix null-ptr-deref in gl861_i2c_master_xfer
In the Linux kernel, the following vulnerability has been resolved:
media: dvb-usb-v2: gl861: Fix null-ptr-deref in gl861_i2c_master_xfer
In gl861_i2c_master_xfer, msg is controlled by user. When msg[i].buf
is null and msg[i].len is zero, former checks on msg[i].buf would be
passed. Malicious data finally reach gl861_i2c_master_xfer. If accessing
msg[i].buf[0] without sanity check, null ptr deref would happen.
We add check on msg[i].len to prevent crash.
Similar commit:
commit 0ed554fd769a
("media: dvb-usb: az6027: fix null-ptr-deref in az6027_i2c_xfer()")
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel flaw in the GL861 DVB USB media driver. A malformed user-controlled transfer can trigger a null pointer dereference and crash the kernel. The available sources indicate a denial-of-service risk, not data theft or remote code execution.
Executive priority
Treat as a targeted availability risk for Linux systems using this media driver. It should be patched through normal kernel maintenance, faster where affected hardware or untrusted local users are present.
Technical view
The issue is in gl861_i2c_master_xfer within media/dvb-usb-v2/gl861. If msg[i].buf is null and msg[i].len is zero, earlier checks can pass and later access to msg[i].buf[0] can dereference null. Stable kernel commits add a length check.
Likely exposure
Exposure is likely limited to Linux systems running affected kernel versions with the GL861 DVB USB driver reachable. Downstream distribution kernels may have backported fixes, so package version alone may not prove exposure.
Exploitation context
The CVE record says msg is user-controlled and malicious data can reach the vulnerable function. No supplied source states public exploitation, KEV listing, remote exploitation, privilege escalation, or code execution.
Researcher notes
The source evidence supports a null pointer dereference denial-of-service condition. Affected-version detail is incomplete in the bundle, and no CVSS or CWE is provided. Analysis should focus on driver reachability, kernel backports, and whether local users can trigger the vulnerable path.
Mitigation direction
Apply vendor or distribution kernel updates containing the referenced stable fixes.
Prioritize systems using GL861 DVB USB media hardware or loading the gl861 driver.
If updates are unavailable, follow vendor guidance for disabling unused affected driver support.
Track distro advisories because Linux fixes may be backported without changing upstream version numbers.
Validation and detection
Check running kernel and distro advisory status against CVE-2023-54066.
Confirm whether the gl861 driver is present, loadable, or in active use.
Review kernel package changelogs for the referenced stable commit IDs.
Verify patched source includes a length check before accessing msg[i].buf[0].
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2023-54066 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
6Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Dec 24, 2025, 12:23 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.