CVE-2026-89879 — media: s2255: bound JPEG frame size before copying into the buffer
In the Linux kernel, the following vulnerability has been resolved: media: s2255: bound JPEG frame size before copying into the buffer s2255_fillbuff() memcpy()s vc->jpg_size bytes of a captured JPEG/MJPEG frame into the vb2 plane. vc->jpg_size is taken verbatim from the S2255_MARKER_FRAME header the device sends (pdword[4] in save_frame()) and, unlike the frame payload length just above it, is never bounded: payload = le32_to_cpu(pdword[3]); if (payload > vc->req_image_size) /* payload is checked ... */ return -EINVAL; vc->pkt_size = payload; vc->jpg_size = le32_to_cpu(pdword[4]); /* ... jpg_size is not */ A malicious or malfunctioning device can therefore report a jpg_size larger than the destination vb2 plane, and the memcpy() writes past it. jpg_size is a signed int, so a value with the top bit set also turns into a huge length. Reject a frame whose jpg_size is negative or exceeds the plane size before copying it.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 38f993ad8b1fe4caf9e989caf6e2a25aff3bbaf7 and < 32a595dd3e8634544e5cfbc47f906dff3d3c1ef8≥ 38f993ad8b1fe4caf9e989caf6e2a25aff3bbaf7 and < 4b6f7bccc6559ae5c54573c284fe76eafc9989b2≥ 38f993ad8b1fe4caf9e989caf6e2a25aff3bbaf7 and < 2542516a147bfad740e7e411c251b639fad260ff≥ 38f993ad8b1fe4caf9e989caf6e2a25aff3bbaf7 and < 79f58f900dd221ab04ea74bf4eaf79fa3b0fcc77≥ 38f993ad8b1fe4caf9e989caf6e2a25aff3bbaf7 and < d2ecaaab6a4f165abb54cdf61be60030b5782bf8≥ 38f993ad8b1fe4caf9e989caf6e2a25aff3bbaf7 and < 68d664f1b4efe525e99154b7058fcb0378bdaff7≥ 38f993ad8b1fe4caf9e989caf6e2a25aff3bbaf7 and < dd739517560c8d0ec4463a53e717bf40b988d7da≥ 38f993ad8b1fe4caf9e989caf6e2a25aff3bbaf7 and < e504cc888f42999dd76b6a43788c422610f2aad2 and 1 moreversion 2.6.27 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 20, 2026 · 5 reading(s) · max 0.21%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× References added · Oct 19, 2026 – Oct 19, 2026
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
10 on the record
- git.kernel.org/stable/c/4b6f7bccc6559ae5c54573c284fe76eafc9989b2
- git.kernel.org/stable/c/79f58f900dd221ab04ea74bf4eaf79fa3b0fcc77
- git.kernel.org/stable/c/2542516a147bfad740e7e411c251b639fad260ff
- git.kernel.org/stable/c/dd739517560c8d0ec4463a53e717bf40b988d7da
- git.kernel.org/stable/c/d2ecaaab6a4f165abb54cdf61be60030b5782bf8
- github.com/advisories/GHSA-w8vh-2wxg-frpg
- nvd.nist.gov/vuln/detail/CVE-2026-89879
- git.kernel.org/stable/c/68d664f1b4efe525e99154b7058fcb0378bdaff7
- git.kernel.org/stable/c/e504cc888f42999dd76b6a43788c422610f2aad2
- git.kernel.org/stable/c/32a595dd3e8634544e5cfbc47f906dff3d3c1ef8
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-98866 sched/cache: Introduce task_struct->sched_cache_grp to fix UAF 2d
- Unknown CVE-2026-98867 dm-pcache: bound the logical key offset from persistent memory 2d
- Unknown CVE-2026-98868 dm-pcache: reject a kset that overruns its segment 2d
- Unknown CVE-2026-98856 kprobes: Skip disarmed probes when checking optkprobe overlap 2d
- Unknown CVE-2026-98857 ipvs: bound LBLCR and LBLC cache growth 2d
- Unknown CVE-2026-98858 io_uring: fix task_work add use-after-free with SQPOLL 2d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-89879 is "media: s2255: bound JPEG frame size before copying into the buffer", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.21% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.