LiveActive security incident?Get immediate response
CVE Record

CVE-2024-42265: protect the fetch of ->fd[fd] in do_dup2() from mispredictions

In the Linux kernel, the following vulnerability has been resolved: protect the fetch of ->fd[fd] in do_dup2() from mispredictions both callers have verified that fd is not greater than ->max_fds; however, misprediction might end up with tofree = fdt->fd[fd]; being speculatively executed. That's wrong for the same reasons why it's wrong in close_fd()/file_close_fd_locked(); the same solution applies - array_index_nospec(fd, fdt->max_fds) could differ from fd only in case of speculative execution on mispredicted path.

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

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel hardening issue around speculative CPU execution. The kernel already checks file descriptor bounds, but a mispredicted path could speculatively fetch an fd-table entry in do_dup2(). Business risk depends on whether systems run affected Linux kernels and whether vendor kernel updates have been applied.

Executive priority

Treat this as routine but time-bound kernel patch management. It is not flagged as actively exploited, but speculative-execution kernel issues matter most on shared, exposed, or regulated infrastructure.

Technical view

The fix applies array_index_nospec() to the do_dup2() fd-table access so speculative execution cannot use an out-of-bounds index after a mispredicted bounds check. The CVE record lists Linux kernel branches as affected and points to stable kernel fixes plus Debian and Siemens advisories.

Likely exposure

Exposure is likely on servers, appliances, containers hosts, and embedded products running affected Linux kernel builds. The bundle does not identify a vulnerable application layer or remotely reachable service.

Exploitation context

The source bundle does not report active exploitation, and KEV is false. The available evidence describes a speculative-execution safety fix, not a public exploit path or remote attack chain.

Researcher notes

Evidence is limited to the CVE description, upstream stable commits, and downstream advisories. No CVSS, CWE, exploit status, or detailed impact rating is provided in the bundle.

Mitigation direction

  • Apply Linux kernel updates from the operating system or device vendor.
  • Prioritize internet-facing hosts, multi-tenant systems, and security appliances using Linux.
  • Track Debian LTS advisories if using Debian-based systems.
  • Check Siemens ProductCERT guidance for affected Siemens products.
  • Avoid custom kernel backports unless they include the referenced stable fixes.

Validation and detection

  • Inventory kernel versions across servers, endpoints, appliances, and container hosts.
  • Confirm installed vendor kernel packages include the CVE-2024-42265 fix.
  • Review Debian or vendor advisories for package-specific fixed versions.
  • Verify reboot completion after kernel updates.
  • Check unsupported or custom kernels for the referenced upstream commits.
Prepared
Confidence
medium
Sources
12

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-42265 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
3ADP providers
12Source 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

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container
siemens-SADPADP container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux8280d16172243702ed43432f826ca6130edb4086, 8280d16172243702ed43432f826ca6130edb4086, 8280d16172243702ed43432f826ca6130edb4086, 8280d16172243702ed43432f826ca6130edb4086, 8280d16172243702ed43432f826ca6130edb4086, 8280d16172243702ed43432f826ca6130edb4086, 8280d16172243702ed43432f826ca6130edb4086, 8280d16172243702ed43432f826ca6130edb4086unaffected
LinuxLinux3.7, 0, 4.19.320, 5.4.282, 5.10.224, 5.15.165, 6.1.104, 6.6.45, 6.10.4, 6.11affected
Weakness

CWE details

No CWE listed

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