LiveActive security incident?Get immediate response
CVE Record

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

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2023-54284 is a Linux kernel media-driver bounds-checking issue. A user-provided byte can make a calculated length go negative before data is repacked for the av7110 decoder. The public record says the bad behavior is not clearly proven, but the kernel fix adds a safety check.

Executive priority

Treat as a targeted kernel hygiene item, not an emergency based on current evidence. Prioritize patching where Linux media/DVB functionality is present, and include it in normal kernel update cycles unless vendor guidance raises severity.

Technical view

In write_ts_to_decoder(), buf[4] originates from ts_play() user input. The code calculates len - (buf[4] + 1) - 4 before calling av7110_ipack_instant_repack(). Stable fixes add bounds checking to prevent underflow and remove an unreachable zero-length branch.

Likely exposure

Exposure appears limited to Linux systems using the av7110 media/DVB driver path. The bundle does not indicate remote reachability, broad default exposure, or affected distributions. Validate kernel versions and whether this driver is present or enabled.

Exploitation context

The source bundle marks KEV as false and provides no evidence of active exploitation, public exploit use, or weaponized details. The upstream description also says it is unclear whether passing a negative length necessarily causes harmful behavior.

Researcher notes

The record lacks CVSS, CWE, and a demonstrated impact. Analysis should focus on reachability of ts_play(), the av7110 driver configuration, and whether downstream kernels backported one of the stable commits. Avoid assuming privilege escalation or denial of service without evidence.

Mitigation direction

  • Update to a kernel build incorporating the referenced stable fixes.
  • Check Linux distribution advisories for packaged fixed kernel versions.
  • Prioritize systems using media/DVB hardware or the av7110 driver.
  • If patch timing is unclear, follow vendor guidance for interim risk handling.

Validation and detection

  • Inventory Linux kernel versions across affected assets.
  • Confirm whether the av7110 driver is built, loaded, or operationally required.
  • Map running kernels against the CVE record and referenced stable commits.
  • Verify patched kernels include the bounds-checking change in write_ts_to_decoder().
Prepared
Confidence
medium
Sources
6

Public sources used

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

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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
10Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxfd46d16d602ab7fd53cef7ff55b9dcb0b47ad3bf, fd46d16d602ab7fd53cef7ff55b9dcb0b47ad3bf, fd46d16d602ab7fd53cef7ff55b9dcb0b47ad3bf, fd46d16d602ab7fd53cef7ff55b9dcb0b47ad3bf, fd46d16d602ab7fd53cef7ff55b9dcb0b47ad3bf, fd46d16d602ab7fd53cef7ff55b9dcb0b47ad3bf, fd46d16d602ab7fd53cef7ff55b9dcb0b47ad3bf, fd46d16d602ab7fd53cef7ff55b9dcb0b47ad3bf, fd46d16d602ab7fd53cef7ff55b9dcb0b47ad3bfunaffected
LinuxLinux2.6.31, 0, 4.14.315, 4.19.283, 5.4.243, 5.10.211, 5.15.111, 6.1.28, 6.2.15, 6.3.2, 6.4affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.