BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2024
CVE-2024-42136High confidence

cdrom: rearrange last_media_change check to avoid unintentional overflow

Linux · Linux

7.8HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 212 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Medium, lowered one band.downgradedsince 11 May 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.23% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 212 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

18 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 14 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.9.9-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.98-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.9.9-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.9.9-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.8Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2024-42136 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: cdrom: rearrange last_media_change check to avoid unintentional overflow
198 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • kernel as a component of Red Hat Enterprise Linux 6
  • kernel-abi-whitelists as a component of Red Hat Enterprise Linux 6
  • kernel-bootwrapper as a component of Red Hat Enterprise Linux 6
  • kernel-debug as a component of Red Hat Enterprise Linux 6
  • kernel-debug-devel as a component of Red Hat Enterprise Linux 6
  • kernel-devel as a component of Red Hat Enterprise Linux 6
  • kernel-doc as a component of Red Hat Enterprise Linux 6
  • kernel-firmware as a component of Red Hat Enterprise Linux 6
  • kernel-headers as a component of Red Hat Enterprise Linux 6
  • kernel-kdump as a component of Red Hat Enterprise Linux 6
  • kernel-kdump-devel as a component of Red Hat Enterprise Linux 6
  • kernel.src as a component of Red Hat Enterprise Linux 6
Summary
A potential overflow in the Linux kernel in last_media_change check. This may lead to a crash.
Remediation
Fix deferred
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2024-39968

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 212 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

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.

What

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.

Why

The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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.

Why

The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → Integer Overflow or Wraparound → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-190 ↗

CWE-190: Integer Overflow or Wraparound. The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
CWE-190
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2024-1722Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20240731Security Bulletin 31 Jul 2024

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 31 Jul 2024, published on 31 July 2024. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0002Multiples vulnérabilités dans le noyau Linux de Debian LTS

d?id=CVE-2024-42115 Référence CVE CVE-2024-42119 https://www.cve.org/CVERecord?id=CVE-2024-42119 Référence CVE CVE-2024-42120 https://www.cve.org/CVERecord?id=CVE-2024-42120 Référence CVE CVE-2024-42121 https://www.cve.org/CVERecord?id=CVE-2024-42121 Référence CVE CVE-2024-42124 https://www.cve.org/CVERecord?id=CVE-2024-42124 Référence CVE CVE-2024-42126 https://www.cve.org/CVERecord?id=CVE-2024-42126 Référence CVE CVE-2024-42127 https://www.cve.org/CVERecord?id=CVE-2024-42127 Référence CVE CVE-2024-42130 https://www.cve.org/CVERecord?id=CVE-2024-42130 Référence CVE CVE-2024-42131 https://www.cve.org/CVERecord?id=CVE-2024-42131 Référence CVE CVE-2024-42136 https://www.cve.org/CVERecord?id=CVE-2024-42136 Référence CVE CVE-2024-42137 https://www.cve.org/CVERecord?id=CVE-2024-42137 Référence CVE CVE-2024-42138 https://www.cve.org/CVERecord?id=CVE-2024-42138 Référence CVE CVE-2024-42140 https://www.cve.org/CVERecord?id=CVE-2024-42140 Référence CVE CVE-2024-42142 https://www.cve.org/CVERecord?id=CVE-2024-42142 Référence CVE CVE-2024-42145 https://www.cve.org/CVERecord?id=CVE-2024-42145 Référence CVE CVE-2024-42147 https://www.cve.org/CVERecord?id=CVE-2024-42147 Référence CVE CVE-2024-42148 https://www.cve.org/CVERecord?id=CVE-2024-42148 Référence CVE CVE-2024-42152 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-1080Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2024-42126 Référence CVE CVE-2024-42127 https://www.cve.org/CVERecord?id=CVE-2024-42127 Référence CVE CVE-2024-42128 https://www.cve.org/CVERecord?id=CVE-2024-42128 Référence CVE CVE-2024-42129 https://www.cve.org/CVERecord?id=CVE-2024-42129 Référence CVE CVE-2024-42130 https://www.cve.org/CVERecord?id=CVE-2024-42130 Référence CVE CVE-2024-42131 https://www.cve.org/CVERecord?id=CVE-2024-42131 Référence CVE CVE-2024-42132 https://www.cve.org/CVERecord?id=CVE-2024-42132 Référence CVE CVE-2024-42133 https://www.cve.org/CVERecord?id=CVE-2024-42133 Référence CVE CVE-2024-42135 https://www.cve.org/CVERecord?id=CVE-2024-42135 Référence CVE CVE-2024-42136 https://www.cve.org/CVERecord?id=CVE-2024-42136 Référence CVE CVE-2024-42137 https://www.cve.org/CVERecord?id=CVE-2024-42137 Référence CVE CVE-2024-42138 https://www.cve.org/CVERecord?id=CVE-2024-42138 Référence CVE CVE-2024-42140 https://www.cve.org/CVERecord?id=CVE-2024-42140 Référence CVE CVE-2024-42141 https://www.cve.org/CVERecord?id=CVE-2024-42141 Référence CVE CVE-2024-42142 https://www.cve.org/CVERecord?id=CVE-2024-42142 Référence CVE CVE-2024-42144 https://www.cve.org/CVERecord?id=CVE-2024-42144 Référence CVE CVE-2024-42145 https://www.cve.org/CVERecord?id=CVE-2024-42145 Référence CVE CVE-2024-42146 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-1013Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2024-42126 Référence CVE CVE-2024-42127 https://www.cve.org/CVERecord?id=CVE-2024-42127 Référence CVE CVE-2024-42128 https://www.cve.org/CVERecord?id=CVE-2024-42128 Référence CVE CVE-2024-42129 https://www.cve.org/CVERecord?id=CVE-2024-42129 Référence CVE CVE-2024-42130 https://www.cve.org/CVERecord?id=CVE-2024-42130 Référence CVE CVE-2024-42131 https://www.cve.org/CVERecord?id=CVE-2024-42131 Référence CVE CVE-2024-42132 https://www.cve.org/CVERecord?id=CVE-2024-42132 Référence CVE CVE-2024-42133 https://www.cve.org/CVERecord?id=CVE-2024-42133 Référence CVE CVE-2024-42135 https://www.cve.org/CVERecord?id=CVE-2024-42135 Référence CVE CVE-2024-42136 https://www.cve.org/CVERecord?id=CVE-2024-42136 Référence CVE CVE-2024-42137 https://www.cve.org/CVERecord?id=CVE-2024-42137 Référence CVE CVE-2024-42138 https://www.cve.org/CVERecord?id=CVE-2024-42138 Référence CVE CVE-2024-42140 https://www.cve.org/CVERecord?id=CVE-2024-42140 Référence CVE CVE-2024-42141 https://www.cve.org/CVERecord?id=CVE-2024-42141 Référence CVE CVE-2024-42142 https://www.cve.org/CVERecord?id=CVE-2024-42142 Référence CVE CVE-2024-42144 https://www.cve.org/CVERecord?id=CVE-2024-42144 Référence CVE CVE-2024-42145 https://www.cve.org/CVERecord?id=CVE-2024-42145 Référence CVE CVE-2024-42146 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0997Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2024-42126 Référence CVE CVE-2024-42127 https://www.cve.org/CVERecord?id=CVE-2024-42127 Référence CVE CVE-2024-42128 https://www.cve.org/CVERecord?id=CVE-2024-42128 Référence CVE CVE-2024-42129 https://www.cve.org/CVERecord?id=CVE-2024-42129 Référence CVE CVE-2024-42130 https://www.cve.org/CVERecord?id=CVE-2024-42130 Référence CVE CVE-2024-42131 https://www.cve.org/CVERecord?id=CVE-2024-42131 Référence CVE CVE-2024-42132 https://www.cve.org/CVERecord?id=CVE-2024-42132 Référence CVE CVE-2024-42133 https://www.cve.org/CVERecord?id=CVE-2024-42133 Référence CVE CVE-2024-42135 https://www.cve.org/CVERecord?id=CVE-2024-42135 Référence CVE CVE-2024-42136 https://www.cve.org/CVERecord?id=CVE-2024-42136 Référence CVE CVE-2024-42137 https://www.cve.org/CVERecord?id=CVE-2024-42137 Référence CVE CVE-2024-42138 https://www.cve.org/CVERecord?id=CVE-2024-42138 Référence CVE CVE-2024-42140 https://www.cve.org/CVERecord?id=CVE-2024-42140 Référence CVE CVE-2024-42141 https://www.cve.org/CVERecord?id=CVE-2024-42141 Référence CVE CVE-2024-42142 https://www.cve.org/CVERecord?id=CVE-2024-42142 Référence CVE CVE-2024-42144 https://www.cve.org/CVERecord?id=CVE-2024-42144 Référence CVE CVE-2024-42145 https://www.cve.org/CVERecord?id=CVE-2024-42145 Référence CVE CVE-2024-42146 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0957Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2024-42126 Référence CVE CVE-2024-42127 https://www.cve.org/CVERecord?id=CVE-2024-42127 Référence CVE CVE-2024-42128 https://www.cve.org/CVERecord?id=CVE-2024-42128 Référence CVE CVE-2024-42129 https://www.cve.org/CVERecord?id=CVE-2024-42129 Référence CVE CVE-2024-42130 https://www.cve.org/CVERecord?id=CVE-2024-42130 Référence CVE CVE-2024-42131 https://www.cve.org/CVERecord?id=CVE-2024-42131 Référence CVE CVE-2024-42132 https://www.cve.org/CVERecord?id=CVE-2024-42132 Référence CVE CVE-2024-42133 https://www.cve.org/CVERecord?id=CVE-2024-42133 Référence CVE CVE-2024-42135 https://www.cve.org/CVERecord?id=CVE-2024-42135 Référence CVE CVE-2024-42136 https://www.cve.org/CVERecord?id=CVE-2024-42136 Référence CVE CVE-2024-42137 https://www.cve.org/CVERecord?id=CVE-2024-42137 Référence CVE CVE-2024-42138 https://www.cve.org/CVERecord?id=CVE-2024-42138 Référence CVE CVE-2024-42140 https://www.cve.org/CVERecord?id=CVE-2024-42140 Référence CVE CVE-2024-42141 https://www.cve.org/CVERecord?id=CVE-2024-42141 Référence CVE CVE-2024-42142 https://www.cve.org/CVERecord?id=CVE-2024-42142 Référence CVE CVE-2024-42144 https://www.cve.org/CVERecord?id=CVE-2024-42144 Référence CVE CVE-2024-42145 https://www.cve.org/CVERecord?id=CVE-2024-42145 Référence CVE CVE-2024-42146 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0822Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2024-42122 Référence CVE CVE-2024-42124 https://www.cve.org/CVERecord?id=CVE-2024-42124 Référence CVE CVE-2024-42125 https://www.cve.org/CVERecord?id=CVE-2024-42125 Référence CVE CVE-2024-42126 https://www.cve.org/CVERecord?id=CVE-2024-42126 Référence CVE CVE-2024-42127 https://www.cve.org/CVERecord?id=CVE-2024-42127 Référence CVE CVE-2024-42130 https://www.cve.org/CVERecord?id=CVE-2024-42130 Référence CVE CVE-2024-42131 https://www.cve.org/CVERecord?id=CVE-2024-42131 Référence CVE CVE-2024-42132 https://www.cve.org/CVERecord?id=CVE-2024-42132 Référence CVE CVE-2024-42133 https://www.cve.org/CVERecord?id=CVE-2024-42133 Référence CVE CVE-2024-42136 https://www.cve.org/CVERecord?id=CVE-2024-42136 Référence CVE CVE-2024-42137 https://www.cve.org/CVERecord?id=CVE-2024-42137 Référence CVE CVE-2024-42138 https://www.cve.org/CVERecord?id=CVE-2024-42138 Référence CVE CVE-2024-42139 https://www.cve.org/CVERecord?id=CVE-2024-42139 Référence CVE CVE-2024-42141 https://www.cve.org/CVERecord?id=CVE-2024-42141 Référence CVE CVE-2024-42142 https://www.cve.org/CVERecord?id=CVE-2024-42142 Référence CVE CVE-2024-42143 https://www.cve.org/CVERecord?id=CVE-2024-42143 Référence CVE CVE-2024-42144 https://www.cve.org/CVERecord?id=CVE-2024-42144 Référence CVE CVE-2024-42145 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0779Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2024-42122 Référence CVE CVE-2024-42124 https://www.cve.org/CVERecord?id=CVE-2024-42124 Référence CVE CVE-2024-42125 https://www.cve.org/CVERecord?id=CVE-2024-42125 Référence CVE CVE-2024-42126 https://www.cve.org/CVERecord?id=CVE-2024-42126 Référence CVE CVE-2024-42127 https://www.cve.org/CVERecord?id=CVE-2024-42127 Référence CVE CVE-2024-42130 https://www.cve.org/CVERecord?id=CVE-2024-42130 Référence CVE CVE-2024-42131 https://www.cve.org/CVERecord?id=CVE-2024-42131 Référence CVE CVE-2024-42132 https://www.cve.org/CVERecord?id=CVE-2024-42132 Référence CVE CVE-2024-42133 https://www.cve.org/CVERecord?id=CVE-2024-42133 Référence CVE CVE-2024-42136 https://www.cve.org/CVERecord?id=CVE-2024-42136 Référence CVE CVE-2024-42137 https://www.cve.org/CVERecord?id=CVE-2024-42137 Référence CVE CVE-2024-42138 https://www.cve.org/CVERecord?id=CVE-2024-42138 Référence CVE CVE-2024-42139 https://www.cve.org/CVERecord?id=CVE-2024-42139 Référence CVE CVE-2024-42141 https://www.cve.org/CVERecord?id=CVE-2024-42141 Référence CVE CVE-2024-42142 https://www.cve.org/CVERecord?id=CVE-2024-42142 Référence CVE CVE-2024-42143 https://www.cve.org/CVERecord?id=CVE-2024-42143 Référence CVE CVE-2024-42144 https://www.cve.org/CVERecord?id=CVE-2024-42144 Référence CVE CVE-2024-42145 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-008312Linux の Linux Kernel における整数オーバーフローの脆弱性

Linux の Linux Kernel には、整数オーバーフローの脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Linux: < 5.16, 6.1.98 ≤ 6.1.*, 6.6.39 ≤ 6.6.*, 6.9.9 ≤ 6.9.*, 6.10 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 30 Jul 2024 · Last source change 11 May 2026, 20:27 UTC · CWE-190 · Integer Overflow or Wraparound

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2024-39968
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceNIST NVD
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2024-39968↗Vendor CSAF · Red Hat Product Security↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2024-42136 · cve.blacktree.nl