Amlogic DroidLogic SubTitleService Infinite Loop via get_vob_spu()
Affects Nexbox A95X (Amlogic S905X) TV boxes up to build NEXBOX-A95X-AP6330 that run the libsub_vob VobSub decoder. CVSS scores it 6.9 (medium), and no vendor rating or fix is listed in the checked facts.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Do first: Workaround: The checked facts give no workaround. The only condition they identify is that the subtitle pipeline must be consuming data, so that is the one factor a reader can look at while waiting for a fix.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 19/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The Amlogic DroidLogic SubTitleService, specifically its VobSub subtitle decoder (libsub_vob), as shipped on certain Nexbox A95X TV boxes, can be made to hang. A remote attacker or a local user who opens a malicious subtitle file can cause the decoder to loop endlessly at full CPU usage, resulting in a denial of service.
Read the original description
The VobSub subtitle decoder libsub_vob (part of the Amlogic DroidLogic SubTitleService), as shipped on Nexbox A95X (Amlogic S905X) TV boxes, contains an infinite loop vulnerability in get_vob_spu() that allows unauthenticated network attackers or local users loading malicious files to trigger an unreachable loop exit condition via mismatched length fields. Attackers can send crafted AMLU data blocks over the unauthenticated tcp/10100 listener or via a malicious VobSub (.sub) file to cause the subtitle decode thread to spin at 100% CPU indefinitely, resulting in denial of service.
What to do
Workaround: The checked facts give no workaround. The only condition they identify is that the subtitle pipeline must be consuming data, so that is the one factor a reader can look at while waiting for a fix.
Timeline
- CVE published
- Record last updated
- First seen by cve.now
Affected versions
- Nexbox A95X
NEXBOX-A95X-AP6330
- Amlogic Amlogic Android SDK
0
Evidence 2
- Exploit
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-119738
What does this mean?
A flaw in the VobSub subtitle code path, get_vob_spu(), can make the subtitle decode thread spin at 100% CPU indefinitely. The result is a denial of service.Source: vulncheck.com, mstreet97.github.io
Am I affected, and how do I check?
The checked facts list Nexbox A95X (Amlogic S905X) TV boxes running the libsub_vob VobSub decoder, with builds up to and including NEXBOX-A95X-AP6330. The trigger requires the subtitle pipeline to be consuming data. To check a device, compare its build identifier with NEXBOX-A95X-AP6330.Source: vulncheck.com, mstreet97.github.io
What should I do about it?
The checked facts do not name a fixed version, so no upgrade target can be given. Check the vendor for an update that moves past build NEXBOX-A95X-AP6330.Source: vulncheck.com, mstreet97.github.io
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What if there's no patch?
The checked facts give no workaround. The only condition they identify is that the subtitle pipeline must be consuming data, so that is the one factor a reader can look at while waiting for a fix.Source: vulncheck.com, mstreet97.github.io