CVE-2026-89879: media: s2255: bound JPEG frame size before copying into the buffer
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.21% (FIRST EPSS).
- Fixed version: Linux Linux 2542516a147bfad740e7e411c251b639fad260ff, 32a595dd3e8634544e5cfbc47f906dff3d3c1ef8, 4b6f7bccc6559ae5c54573c284fe76eafc9989b2; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 2542516a147bfad740e7e411c251b639fad260ff, 32a595dd3e8634544e5cfbc47f906dff3d3c1ef8, 4b6f7bccc6559ae5c54573c284fe76eafc9989b2; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1 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: 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.
- Published
- Sep 16, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.2% · 12th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
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.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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.27affected
- 38f993ad8b1fe4caf9e989caf6e2a25aff3bbaf7 and later · before 32a595dd3e8634544e5cfbc47f906dff3d3c1ef8affected · git
- 38f993ad8b1fe4caf9e989caf6e2a25aff3bbaf7 and later · before 4b6f7bccc6559ae5c54573c284fe76eafc9989b2affected · git
- 38f993ad8b1fe4caf9e989caf6e2a25aff3bbaf7 and later · before 2542516a147bfad740e7e411c251b639fad260ffaffected · git
- 38f993ad8b1fe4caf9e989caf6e2a25aff3bbaf7 and later · before 79f58f900dd221ab04ea74bf4eaf79fa3b0fcc77affected · git
- 38f993ad8b1fe4caf9e989caf6e2a25aff3bbaf7 and later · before d2ecaaab6a4f165abb54cdf61be60030b5782bf8affected · git
- 38f993ad8b1fe4caf9e989caf6e2a25aff3bbaf7 and later · before 68d664f1b4efe525e99154b7058fcb0378bdaff7affected · git
- 38f993ad8b1fe4caf9e989caf6e2a25aff3bbaf7 and later · before dd739517560c8d0ec4463a53e717bf40b988d7daaffected · git
- 38f993ad8b1fe4caf9e989caf6e2a25aff3bbaf7 and later · before e504cc888f42999dd76b6a43788c422610f2aad2affected · git
- before 2.6.27not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-89877Sep 16, 2026 · media: saa7164: fix cleanup on resource allocation failure33Monitor
- ← EarlierCVE-2026-89878Sep 16, 2026 · media: s2255: check firmware size before reading trailing marker0Monitor
- Later →CVE-2026-89880Sep 16, 2026 · media: rtl2832_sdr: release URBs and stream buffers on start_streaming() failure31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 2542516a147bfad740e7e411c251b639fad260ff | Vendor (CNA) |
| Linux Linux | 32a595dd3e8634544e5cfbc47f906dff3d3c1ef8 | Vendor (CNA) |
| Linux Linux | 4b6f7bccc6559ae5c54573c284fe76eafc9989b2 | Vendor (CNA) |
| Linux Linux | 68d664f1b4efe525e99154b7058fcb0378bdaff7 | Vendor (CNA) |
| Linux Linux | 79f58f900dd221ab04ea74bf4eaf79fa3b0fcc77 | Vendor (CNA) |
| Linux Linux | d2ecaaab6a4f165abb54cdf61be60030b5782bf8 | Vendor (CNA) |
| Linux Linux | dd739517560c8d0ec4463a53e717bf40b988d7da | Vendor (CNA) |
| Linux Linux | e504cc888f42999dd76b6a43788c422610f2aad2 | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | — | Microsoft (MSRC) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | 6.6.157.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
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 researchersFinders, 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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1114 · Sep 17, 2026(Linux Kernel Güvenlik Bildirimi)
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/32a595dd3e8634544e5cfbc47f906dff3d3c1ef8
- git.kernel.org/stable/c/4b6f7bccc6559ae5c54573c284fe76eafc9989b2
- git.kernel.org/stable/c/68d664f1b4efe525e99154b7058fcb0378bdaff7
- git.kernel.org/stable/c/79f58f900dd221ab04ea74bf4eaf79fa3b0fcc77
- git.kernel.org/stable/c/d2ecaaab6a4f165abb54cdf61be60030b5782bf8
- git.kernel.org/stable/c/dd739517560c8d0ec4463a53e717bf40b988d7da
- git.kernel.org/stable/c/e504cc888f42999dd76b6a43788c422610f2aad2
Vendor advisories and official records. Exploit/PoC links are deliberately left out.