Bug 2548399 (CVE-2026-107655) - CVE-2026-107655 cups: NULL pointer dereference via embedded job ticket comments allows remote denial of service
Summary: CVE-2026-107655 cups: NULL pointer dereference via embedded job ticket commen...
Keywords:
Status: NEW
Alias: CVE-2026-107655
Deadline: 2026-10-09
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2548470
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-10-09 08:16 UTC by OSIDB Bzimport
Modified: 2026-10-09 10:48 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-10-09 08:16:18 UTC
A flaw was found in CUPS when processing embedded job ticket comments in PostScript or PDF documents. The read_job_ticket() function in scheduler/ipp.c allows a job-ticket option named attributes-natural-language to replace the valid IPP operation attribute with a keyword attribute, because the replacement lookup does not restrict the attribute group. When the job starts, cupsdContinueJob() in scheduler/job.c looks up the attribute as IPP_TAG_LANGUAGE and dereferences the NULL result without checking it. An unauthenticated client permitted to submit jobs to an accepting shared printer queue can send a single crafted IPP Print-Job request to crash cupsd before any document filter or backend starts, temporarily interrupting printing for all users. The upstream report reproduced the crash on CUPS 2.4.19, 2.4.20, and the 2.4.x development branch. Loopback-only deployments are not remotely reachable through this path. The ticket states that the service automatically restarts after failure; no confidentiality or integrity impact is demonstrated. Validation associated with CVE-2026-61702 does not prevent this issue because job-ticket processing modifies the attribute after that validation. Upstream fixes restrict job-ticket attributes and disable job-ticket comment processing by default in the 2.4.x branch, and remove this functionality in the branch for 2.5 and later.


Note You need to log in before you can comment on or make changes to this bug.