In the Linux kernel, the following vulnerability has been resolved:
ice: Fix improper extts handling
Extts events are disabled and enabled by the application ts2phc.
However, in case where the driver is removed when the application is
running, a specific extts event remains enabled and can cause a kernel
crash.
As a side effect, when the driver is reloaded and application is started
again, remaining extts event for the channel from a previous run will
keep firing and the message "extts on unexpected channel" might be
printed to the user.
To avoid that, extts events shall be disabled when PTP is released.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue can crash a system when the Intel ice network driver is removed while PTP timestamping software is still using external timestamp events. The source describes an availability risk, not data theft or remote takeover. Exposure depends on affected kernels, the ice driver, and PTP/ts2phc usage.
Executive priority
Treat as a targeted availability risk for time-sensitive network infrastructure rather than a broad enterprise emergency. Patch during the next appropriate maintenance window, sooner for production systems relying on PTP or ice-based network adapters.
Technical view
The ice driver did not disable extts events when PTP was released. If ts2phc was running during driver removal, an extts event could remain enabled, later causing a kernel crash or repeated “extts on unexpected channel” messages after reload. Stable kernel commits disable extts events on PTP release.
Likely exposure
Most likely on Linux systems using the ice driver with PTP external timestamp handling, especially where ts2phc runs and drivers may be removed or reloaded. The bundle lists Linux kernel affected versions/markers but does not provide distribution-specific package names.
Exploitation context
The source bundle does not cite active exploitation, and KEV is false. The described trigger requires a specific operational sequence involving ts2phc and ice driver removal while the application is running. Public evidence here supports a crash condition, not weaponized exploitation.
Researcher notes
Evidence is limited to the CVE record and kernel stable commits. No CVSS, CWE, exploit status, or distro package mapping is provided. Validate exposure by driver, PTP usage, and kernel backport status rather than upstream version strings alone.
Mitigation direction
Apply Linux vendor kernel updates containing the referenced stable fixes.
Avoid removing or reloading the ice driver while ts2phc is running.
Review vendor advisories for distribution-specific fixed kernel packages.
Prioritize systems that use PTP, ts2phc, and Intel ice networking.
Validation and detection
Inventory Linux hosts using the ice driver and PTP services.
Check whether ts2phc or equivalent PTP timestamping applications run on those hosts.
Verify installed kernels include the referenced stable commits or vendor backports.
Review kernel logs for “extts on unexpected channel” messages.
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-42139 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.