CVE-2026-89879

media: s2255: bound JPEG frame size before copying into the buffer

N/A
Published: September 16, 2026 at 10:31 AM UTC
Updated: October 19, 2026 at 09:18 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.6.2738f993ad8b1fe4caf9e989caf6e2a25aff3bbaf7
Vendor states this is fixed in 2542516a147bfad740e7e411c251b639fad260ff (fixed)
Vendor states this is fixed in 32a595dd3e8634544e5cfbc47f906dff3d3c1ef8 (fixed)
Vendor states this is fixed in 4b6f7bccc6559ae5c54573c284fe76eafc9989b2 (fixed)
Vendor states this is fixed in 68d664f1b4efe525e99154b7058fcb0378bdaff7 (fixed)
Vendor states this is fixed in 79f58f900dd221ab04ea74bf4eaf79fa3b0fcc77 (fixed)
Vendor states this is fixed in d2ecaaab6a4f165abb54cdf61be60030b5782bf8 (fixed)
Vendor states this is fixed in dd739517560c8d0ec4463a53e717bf40b988d7da (fixed)
Vendor states this is fixed in e504cc888f42999dd76b6a43788c422610f2aad2 (fixed)
Vendor states this is fixed in 2.6.27 (unaffected)
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.18.51 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.5 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card