Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2023-54066: media: dvb-usb-v2: gl861: Fix null-ptr-deref in gl861_i2c_master_xfer

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.19% (FIRST EPSS).
  • Fixed version: Linux Linux 2a33fc57133d6f39d62285df6706aeb1714967f1, 578b67614ae0e4fba3945b66a4c8f9ae77115bcb, 72af676551efe820e309a6c7681c2c4372f37376.

Low priority for now. Upgrade to Linux Linux 2a33fc57133d6f39d62285df6706aeb1714967f1, 578b67614ae0e4fba3945b66a4c8f9ae77115bcb, 72af676551efe820e309a6c7681c2c4372f37376 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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()")

—No exploit Fix available
Published
Dec 24, 2025
Updated
Jun 17, 2026
EPSS
0.1% · 9th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2023-54066

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.5affected
    • 1ea76d16569b7fc242b860c7e19549be028b13d1 and later · before 578b67614ae0e4fba3945b66a4c8f9ae77115bcbaffected · git
    • 1ea76d16569b7fc242b860c7e19549be028b13d1 and later · before 2a33fc57133d6f39d62285df6706aeb1714967f1affected · git
    • 1ea76d16569b7fc242b860c7e19549be028b13d1 and later · before dfcd3c010209927b9f45b860f046635dc32e32e1affected · git
    • 1ea76d16569b7fc242b860c7e19549be028b13d1 and later · before 72af676551efe820e309a6c7681c2c4372f37376affected · git
    • 1ea76d16569b7fc242b860c7e19549be028b13d1 and later · before b97719a66970601cd3151a3e2020f4454a1c4ff6affected · git
    • before 5.5not affected · semver
    • 5.10.197 and later · up to and including 5.10.*not affected · semver
    • 5.15.133 and later · up to and including 5.15.*not affected · semver
    • 6.1.55 and later · up to and including 6.1.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.55-16.1.55-1
Debian:13linuxbefore 6.5.6-16.5.6-1

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2023-54064Dec 24, 2025 · ipmi:ssif: Fix a memory leak when scanning for an adapter
    0Monitor
  • ← EarlierCVE-2023-54065Dec 24, 2025 · net: dsa: realtek: fix out-of-bounds access
    31Monitor
  • Later →CVE-2023-54067Dec 24, 2025 · btrfs: fix race when deleting free space root from the dirty cow roots list
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux2a33fc57133d6f39d62285df6706aeb1714967f1Vendor (CNA)
Linux Linux578b67614ae0e4fba3945b66a4c8f9ae77115bcbVendor (CNA)
Linux Linux72af676551efe820e309a6c7681c2c4372f37376Vendor (CNA)
Linux Linuxb97719a66970601cd3151a3e2020f4454a1c4ff6Vendor (CNA)
Linux Linuxdfcd3c010209927b9f45b860f046635dc32e32e1Vendor (CNA)
debian:linux6.1.55-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records