Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2023-54284: media: av7110: prevent underflow in write_ts_to_decoder()

Noroxi assessment

Priority: Monitor (action score 28/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.15% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 423350af9e27f005611bd881b1df2cab66de943d, 620b983589e0223876bf1463b01100a9c67b56ba, 6606e2404ee9e20a3ae5b42fc3660d41b739ed3e.

Low priority for now. Upgrade to Linux Linux 423350af9e27f005611bd881b1df2cab66de943d, 620b983589e0223876bf1463b01100a9c67b56ba, 6606e2404ee9e20a3ae5b42fc3660d41b739ed3e 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: av7110: prevent underflow in write_ts_to_decoder() The buf[4] value comes from the user via ts_play(). It is a value in the u8 range. The final length we pass to av7110_ipack_instant_repack() is "len - (buf[4] + 1) - 4" so add a check to ensure that the length is not negative. It's not clear that passing a negative len value does anything bad necessarily, but it's not best practice. With the new bounds checking the "if (!len)" condition is no longer possible or required so remove that.

HighCVSS 7.1 · v3.1—No exploit Fix available
Published
Dec 30, 2025
Updated
Aug 5, 2026
EPSS
0.1% · 4th percentile
CWE
—

Report tools

JSON

Action score

28

Monitor

Low priority for now.

CVSS
28 / 40 · 7.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CNA vs NVD score

NVD
—
CNA · Linux
7.1
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

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-54284

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.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

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

    • 2.6.31affected
    • fd46d16d602ab7fd53cef7ff55b9dcb0b47ad3bf and later · before 6680af5be9f08d830567e9118f76d3e64684db8faffected · git
    • fd46d16d602ab7fd53cef7ff55b9dcb0b47ad3bf and later · before 6606e2404ee9e20a3ae5b42fc3660d41b739ed3eaffected · git
    • fd46d16d602ab7fd53cef7ff55b9dcb0b47ad3bf and later · before 620b983589e0223876bf1463b01100a9c67b56baaffected · git
    • fd46d16d602ab7fd53cef7ff55b9dcb0b47ad3bf and later · before 86ba65e5357bfbb6c082f68b265a292ee1bdde1daffected · git
    • fd46d16d602ab7fd53cef7ff55b9dcb0b47ad3bf and later · before ca4ce92e3ec9fd3c7c936b912b95c53331d5159caffected · git
    • fd46d16d602ab7fd53cef7ff55b9dcb0b47ad3bf and later · before 423350af9e27f005611bd881b1df2cab66de943daffected · git
    • fd46d16d602ab7fd53cef7ff55b9dcb0b47ad3bf and later · before 77eeb4732135c18c2fdfab80839645b393f3e774affected · git
    • fd46d16d602ab7fd53cef7ff55b9dcb0b47ad3bf and later · before 7b93ab60fe9ed04be0ff155bc30ad39dea23e22baffected · git
    • fd46d16d602ab7fd53cef7ff55b9dcb0b47ad3bf and later · before eed9496a0501357aa326ddd6b71408189ed872ebaffected · git

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.37-16.1.37-1
Debian:13linuxbefore 6.3.7-16.3.7-1

Same product

linux: all records

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-54282Dec 30, 2025 · media: tuners: qt1010: replace BUG_ON with a regular error
    0Monitor
  • ← EarlierCVE-2023-54283Dec 30, 2025 · bpf: Address KCSAN report on bpf_lru_list
    0Monitor
  • Later →CVE-2023-54286Dec 30, 2025 · wifi: iwlwifi: dvm: Fix memcpy: detected field-spanning write backtrace
    30Monitor

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 Linux423350af9e27f005611bd881b1df2cab66de943dVendor (CNA)
Linux Linux620b983589e0223876bf1463b01100a9c67b56baVendor (CNA)
Linux Linux6606e2404ee9e20a3ae5b42fc3660d41b739ed3eVendor (CNA)
Linux Linux6680af5be9f08d830567e9118f76d3e64684db8fVendor (CNA)
Linux Linux77eeb4732135c18c2fdfab80839645b393f3e774Vendor (CNA)
Linux Linux7b93ab60fe9ed04be0ff155bc30ad39dea23e22bVendor (CNA)
Linux Linux86ba65e5357bfbb6c082f68b265a292ee1bdde1dVendor (CNA)
Linux Linuxca4ce92e3ec9fd3c7c936b912b95c53331d5159cVendor (CNA)
Linux Linuxeed9496a0501357aa326ddd6b71408189ed872ebVendor (CNA)
debian:linux6.1.37-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.

Credits

All researchers

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

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H

nvd-secondary

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

Show all references (8 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records