CVE-2024-42107: ice: Don't process extts if PTP is disabled
Noroxi assessment
Priority: Monitor (action score 18/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: Linux Linux 1c4e524811918600683b1ea87a5e0fc2db64fa9b, 2ab26aeec3de0a677e02d6bc4dc85d49cd1ec4ac, 996422e3230e41468f652d754fefd1bdbcd4604e.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 1c4e524811918600683b1ea87a5e0fc2db64fa9b, 2ab26aeec3de0a677e02d6bc4dc85d49cd1ec4ac, 996422e3230e41468f652d754fefd1bdbcd4604e or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: ice: Don't process extts if PTP is disabled The ice_ptp_extts_event() function can race with ice_ptp_release() and result in a NULL pointer dereference which leads to a kernel panic. Panic occurs because the ice_ptp_extts_event() function calls ptp_clock_event() with a NULL pointer. The ice driver has already released the PTP clock by the time the interrupt for the next external timestamp event occurs. To fix this, modify the ice_ptp_extts_event() function to check the PTP state and bail early if PTP is not ready.
- Published
- Jul 30, 2024
- Updated
- Oct 30, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- CWE-367
Report tools
Action score
18
Low priority for now.
- CVSS
- 18 / 40 · 4.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.14affected
- 172db5f91d5f7b91670c68a7547798b0b5374158 and later · before 2ab26aeec3de0a677e02d6bc4dc85d49cd1ec4acaffected · git
- 172db5f91d5f7b91670c68a7547798b0b5374158 and later · before 9aa83a5eb013f8aff20e701aa25ba6b0eaad0b65affected · git
- 172db5f91d5f7b91670c68a7547798b0b5374158 and later · before 1c4e524811918600683b1ea87a5e0fc2db64fa9baffected · git
- 172db5f91d5f7b91670c68a7547798b0b5374158 and later · before 996422e3230e41468f652d754fefd1bdbcd4604eaffected · git
- before 5.14not affected · semver
- 6.1.191 and later · up to and including 6.1.*not affected · semver
- 6.6.160 and later · up to and including 6.6.*not affected · semver
- 6.9.9 and later · up to and including 6.9.*not affected · semver
- 6.10 and laternot affected · original_commit_for_fix
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.14 and later · before 6.9.9
- linux linux kernel6.10
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.192-1 | 6.1.192-1 |
| Debian:13 | linux | before 6.9.9-1 | 6.9.9-1 |
| Red Hat:rhel_eus:9.2::appstream | bpftool-debuginfo | before 0:7.0.0-284.80.1.el9_2 | 0:7.0.0-284.80.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-64k-debug-debuginfo | before 0:5.14.0-284.80.1.el9_2 | 0:5.14.0-284.80.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-64k-debug-devel | before 0:5.14.0-284.80.1.el9_2 | 0:5.14.0-284.80.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-64k-debug-devel-matched | before 0:5.14.0-284.80.1.el9_2 | 0:5.14.0-284.80.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-64k-debuginfo | before 0:5.14.0-284.80.1.el9_2 | 0:5.14.0-284.80.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-64k-devel | before 0:5.14.0-284.80.1.el9_2 | 0:5.14.0-284.80.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-64k-devel-matched | before 0:5.14.0-284.80.1.el9_2 | 0:5.14.0-284.80.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-debug-debuginfo | before 0:5.14.0-284.80.1.el9_2 | 0:5.14.0-284.80.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-debug-devel | before 0:5.14.0-284.80.1.el9_2 | 0:5.14.0-284.80.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-debug-devel-matched | before 0:5.14.0-284.80.1.el9_2 | 0:5.14.0-284.80.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-debuginfo | before 0:5.14.0-284.80.1.el9_2 | 0:5.14.0-284.80.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-debuginfo-common-aarch64 | before 0:5.14.0-284.80.1.el9_2 | 0:5.14.0-284.80.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-debuginfo-common-ppc64le | before 0:5.14.0-284.80.1.el9_2 | 0:5.14.0-284.80.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-debuginfo-common-s390x | before 0:5.14.0-284.80.1.el9_2 | 0:5.14.0-284.80.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-debuginfo-common-x86_64 | before 0:5.14.0-284.80.1.el9_2 | 0:5.14.0-284.80.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-devel | before 0:5.14.0-284.80.1.el9_2 | 0:5.14.0-284.80.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-devel-matched | before 0:5.14.0-284.80.1.el9_2 | 0:5.14.0-284.80.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-tools-debuginfo | before 0:5.14.0-284.80.1.el9_2 | 0:5.14.0-284.80.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-zfcpdump-debuginfo | before 0:5.14.0-284.80.1.el9_2 | 0:5.14.0-284.80.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-zfcpdump-devel | before 0:5.14.0-284.80.1.el9_2 | 0:5.14.0-284.80.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-zfcpdump-devel-matched | before 0:5.14.0-284.80.1.el9_2 | 0:5.14.0-284.80.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | perf | before 0:5.14.0-284.80.1.el9_2 | 0:5.14.0-284.80.1.el9_2 |
+53
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2023-52888Jul 30, 2024 · media: mediatek: vcodec: Only free buffer VA that is not NULL22Monitor
- ← EarlierCVE-2024-42106Jul 30, 2024 · inet_diag: Initialize pad field in struct inet_diag_req_v222Monitor
- Later →CVE-2024-42114Jul 30, 2024 · wifi: cfg80211: restrict NL80211_ATTR_TXQ_QUANTUM values17Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1c4e524811918600683b1ea87a5e0fc2db64fa9b | Vendor (CNA) |
| Linux Linux | 2ab26aeec3de0a677e02d6bc4dc85d49cd1ec4ac | Vendor (CNA) |
| Linux Linux | 996422e3230e41468f652d754fefd1bdbcd4604e | Vendor (CNA) |
| Linux Linux | 9aa83a5eb013f8aff20e701aa25ba6b0eaad0b65 | Vendor (CNA) |
| debian:linux | 6.1.192-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.9.9-1 · Debian:13 | Package registry (OSV) |
| red hat:bpftool-debuginfo | 0:7.0.0-284.80.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:5.14.0-284.80.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:5.14.0-284.80.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:5.14.0-284.80.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:5.14.0-284.80.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:5.14.0-284.80.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:5.14.0-284.80.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:5.14.0-284.80.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:5.14.0-284.80.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:5.14.0-284.80.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:5.14.0-284.80.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-aarch64 | 0:5.14.0-284.80.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2025-38352357 days apartposix-cpu-timers: fix race between handle_posix_cpu_timers() and posix_cpu_timer_del()KEV61This week
- CVE-2023-2007463 days apartThe specific flaw exists within the DPT I2O Controller driver.31Monitor
- CVE-2024-4388222 days apartexec: Fix ToCToU between perm check and set-uid/gid usage28Monitor
- CVE-2021-4728070 days apartdrm: Fix use-after-free read in drm_getunique()28Monitor
- CVE-2024-2697490 days apartcrypto: qat - resolve race condition during AER recovery28Monitor
- CVE-2024-50234102 days apartwifi: iwlegacy: Clear stale interrupts before resuming device28Monitor
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-1106 · Jul 31, 2024(Linux Kernel Güncellemesi)
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-367 · Time-of-check Time-of-use (TOCTOU) Race ConditionCVSS vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.