LiveActive security incident?Get immediate response
CVE Record

CVE-2024-42136: cdrom: rearrange last_media_change check to avoid unintentional overflow

In the Linux kernel, the following vulnerability has been resolved: cdrom: rearrange last_media_change check to avoid unintentional overflow When running syzkaller with the newly reintroduced signed integer wrap sanitizer we encounter this splat: [ 366.015950] UBSAN: signed-integer-overflow in ../drivers/cdrom/cdrom.c:2361:33 [ 366.021089] -9223372036854775808 - 346321 cannot be represented in type '__s64' (aka 'long long') [ 366.025894] program syz-executor.4 is using a deprecated SCSI ioctl, please convert it to SG_IO [ 366.027502] CPU: 5 PID: 28472 Comm: syz-executor.7 Not tainted 6.8.0-rc2-00035-gb3ef86b5a957 #1 [ 366.027512] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 [ 366.027518] Call Trace: [ 366.027523] <TASK> [ 366.027533] dump_stack_lvl+0x93/0xd0 [ 366.027899] handle_overflow+0x171/0x1b0 [ 366.038787] ata1.00: invalid multi_count 32 ignored [ 366.043924] cdrom_ioctl+0x2c3f/0x2d10 [ 366.063932] ? __pm_runtime_resume+0xe6/0x130 [ 366.071923] sr_block_ioctl+0x15d/0x1d0 [ 366.074624] ? __pfx_sr_block_ioctl+0x10/0x10 [ 366.077642] blkdev_ioctl+0x419/0x500 [ 366.080231] ? __pfx_blkdev_ioctl+0x10/0x10 ... Historically, the signed integer overflow sanitizer did not work in the kernel due to its interaction with `-fwrapv` but this has since been changed [1] in the newest version of Clang. It was re-enabled in the kernel with Commit 557f8c582a9ba8ab ("ubsan: Reintroduce signed overflow sanitizer"). Let's rearrange the check to not perform any arithmetic, thus not tripping the sanitizer.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2024-42136 is a Linux kernel cdrom driver bug where a media-change time check could cause signed integer overflow. The public record describes a sanitizer-detected kernel issue, not a confirmed remote compromise path. Business urgency depends on whether affected Linux kernels and optical-media device paths exist in the fleet.

Executive priority

Treat this as a routine kernel patch-management item unless your environment exposes cdrom device paths on affected kernels. There is no source-backed evidence of active exploitation, but kernel issues still deserve timely remediation through standard maintenance windows.

Technical view

The bug is in drivers/cdrom/cdrom.c within cdrom_ioctl handling. Syzkaller with the reintroduced signed integer overflow sanitizer triggered an overflow during last_media_change arithmetic. The upstream fix rearranges the check to avoid arithmetic that can overflow. Sources do not provide CVSS, CWE, or a detailed security impact.

Likely exposure

Exposure is most plausible on Linux systems running affected kernel builds with cdrom or SCSI optical-device code reachable. Cloud servers and containers may have little practical exposure unless host kernels expose such devices. The bundle lists upstream stable fixes and a Debian LTS advisory, so distribution patch status should be verified.

Exploitation context

The source evidence shows syzkaller discovery and KEV is false. No cited source claims active exploitation, public weaponization, or remote exploitation. The described trigger involves kernel cdrom ioctl handling and a deprecated SCSI ioctl path, but the bundle does not establish a practical attacker impact.

Researcher notes

The evidence is narrow: sanitizer overflow in cdrom_ioctl, found by syzkaller, fixed by avoiding arithmetic in the last_media_change check. The public bundle does not document privilege requirements, exploitability, CVSS, CWE, or impact beyond the overflow finding.

Mitigation direction

  • Update affected systems to vendor kernels containing the upstream stable fixes.
  • Check Debian LTS and other distribution advisories for package-specific fixed versions.
  • Prioritize hosts that expose optical-media or SCSI cdrom device paths.
  • Where patching is delayed, follow vendor guidance for device-access restrictions.
  • Track kernel inventory against the listed fixed stable references.

Validation and detection

  • Identify Linux kernel versions across servers, workstations, and appliances.
  • Check whether cdrom or SCSI optical device support is present or exposed.
  • Confirm the installed kernel includes one of the cited stable fixes.
  • Review distribution security advisories for backported fixes.
  • Validate remediation through normal kernel package and reboot verification.
Prepared
Confidence
medium
Sources
7

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-42136 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
2ADP providers
6Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux67f1e027c27054e641584655020a417eaac9cb3a, 67f1e027c27054e641584655020a417eaac9cb3a, 67f1e027c27054e641584655020a417eaac9cb3a, 67f1e027c27054e641584655020a417eaac9cb3aunaffected
LinuxLinux5.16, 0, 6.1.98, 6.6.39, 6.9.9, 6.10affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.