LiveActive security incident?Get immediate response
CVE Record

CVE-2024-36887: e1000e: change usleep_range to udelay in PHY mdic access

In the Linux kernel, the following vulnerability has been resolved: e1000e: change usleep_range to udelay in PHY mdic access This is a partial revert of commit 6dbdd4de0362 ("e1000e: Workaround for sporadic MDI error on Meteor Lake systems"). The referenced commit used usleep_range inside the PHY access routines, which are sometimes called from an atomic context. This can lead to a kernel panic in some scenarios, such as cable disconnection and reconnection on vPro systems. Solve this by changing the usleep_range calls back to udelay.

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can cause a system crash when the Intel e1000e network driver accesses PHY management logic from an atomic context. The described trigger involves cable disconnect and reconnect scenarios on vPro systems. The business impact is availability loss, not disclosed data theft or remote takeover in the provided sources.

Executive priority

Handle as a reliability and uptime risk for affected Linux fleets, not as confirmed active exploitation. Prioritize environments where unexpected host crashes are business-critical or where vPro-class hardware with e1000e is common.

Technical view

The vulnerable change used usleep_range inside e1000e PHY MDIC access routines. Those routines may run in atomic context, where sleeping is unsafe and can panic the kernel. The fix changes those waits back to udelay. The CVE record lists Linux kernel stable commits as references, with no CVSS, CWE, or detailed affected product matrix.

Likely exposure

Exposure appears limited to Linux systems using affected e1000e kernel driver code paths, especially systems matching the described Meteor Lake or vPro scenario. The source bundle does not provide a complete distro-by-distro affected version list.

Exploitation context

The source bundle does not report active exploitation, and KEV status is false. The described failure scenario is operational: network cable disconnection and reconnection can lead to kernel panic on some systems. No remote exploit path is established in the provided evidence.

Researcher notes

Evidence is narrow but coherent: the vulnerability is a sleep-in-atomic-context bug introduced by a prior e1000e workaround and fixed by reverting to busy-wait delays. Public metadata lacks CVSS, CWE, exploit status, and a complete affected-version matrix, so validation should focus on kernel commit lineage and distro backports.

Mitigation direction

  • Apply vendor or distribution kernel updates containing the referenced stable fixes.
  • Prioritize Linux endpoints or servers using the e1000e driver.
  • Check vendor advisories if your distribution backports kernel fixes without changing major versions.
  • Avoid treating version strings alone as definitive without distro advisory confirmation.

Validation and detection

  • Inventory Linux systems using the Intel e1000e driver.
  • Confirm whether installed kernel packages include the referenced stable commits or equivalent backports.
  • Review kernel logs for e1000e PHY or MDIC errors followed by panic events.
  • Test remediation in a maintenance window before broad deployment.
Prepared
Confidence
medium
Sources
5

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-36887 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
4Source 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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux1d16cd91cd319d5bf6230c8493feb56a61e486a1, 0a4e3c2d976aa4dd38951afd6267f74ef3fade0e, 6dbdd4de0362c37e54e8b049781402e5a409e7d0unaffected
LinuxLinux6.6.26, 6.8.5unaffected
Weakness

CWE details

No CWE listed

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