CVE-2024-42136
cdrom: rearrange last_media_change check to avoid unintentional overflow
Reported by linux · Published July 30, 2024
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.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| kernel-headers | Amazon Linux | 6.1.102-108.177.amzn2023 |
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 67f1e027c27054e641584655020a417eaac9cb3a, 67f1e027c27054e641584655020a417eaac9cb3a, 67f1e027c27054e641584655020a417eaac9cb3a |
| Linux | Linux | 5.16, 0, 6.1.98 |
| amazon:2023 | kernel-headers | 0 |
| linux | linux_kernel | 5.16, 5.16, 5.16 |
| Linux | Linux | 6.10, 67f1e027c27054e641584655020a417eaac9cb3a, 67f1e027c27054e641584655020a417eaac9cb3a |
| amazon:2023 | kernel-tools | 0 |
| amazon:2023 | python3-perf | 0 |
| amazon:2023 | kernel-libbpf-static | 0 |
| amazon:2023 | kernel-livepatch-6.1.102-108.177 | 0 |
| amazon:2023 | kernel-tools-devel | 0 |
| amazon:2023 | kernel-modules-extra-common | 0 |
| amazon:2023 | bpftool | 0 |
| amazon:2023 | kernel-devel | 0 |
| amazon:2023 | kernel-libbpf-devel | 0 |
| amazon:2023 | perf | 0 |
| amazon:2023 | kernel | 0 |
| amazon:2023 | kernel-libbpf | 0 |
| amazon:2023 | kernel-modules-extra | 0 |
Timeline
- Jul 29, 2024 CVE Published
- Jul 30, 2024 EPSS Score (30 in total, the first dated here)
- Oct 4, 2024 Coalition ESS Score (10 in total, the first dated here)
- Jan 6, 2026 Security Advisory (355 in total, the first dated here)
- Mar 30, 2026 Distribution Patch (237 in total, the first dated here)
- Nov 19, 2026 CVE Updated
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2024-42136
vulnetix vdb fixes CVE-2024-42136
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2024-42136/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart